Skip to main content

Big team and Commitment

Managing a big team is not an easy job, especially when you have a customer that make a lot of pressure – in the end all customers make pressure, you need to deal with it.
What you should never do to a team?
Announce that all the sub-teams structure will change from today - changing the scope of each of them and also the people.
In this scenario people will be disoriented. All the tasks and plans will remain in a gray state. Even if you will continue after 2-3 months will not be the same. After you make such a change, you should allow some time to sub-teams to finished the ongoing tasks and let the sub-project in a stable phase. In this cases the team members will feel that there is not communication inside the team and the only scope of team leaders is to make promises.
When you are in the head of a team you should not accept death-lines from the customer without talking with the team. Making such commitments can generate a lot of problems:
  • You will not be able to deliver in time
  • The team will be stress
  • A lot of overtime
  • The quality of the code will decrease
  • There will be a log of bugs
  • Testing team will not have enough time to make the test
  • And many more

And again, you will not be able to deliver in time. The client will not be happy, even if he says that it is fine for him.
In such situations, the testing team will have a lot of headaches because they will don’t have enough time to make all the testing (from new features testing to regression tests). The testing team should never accept a new version of a product without having enough time for testing. They are like a defense tower that can discover issues that in production can ruin not only the development team but also the client.

All this problem can be avoided with the simplest thing: COMMUNICATION


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…