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

Comments

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users. This information might be useful in the future when we need to decide where we want to keep and manage our users. Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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 http://go.microsoft.com/fwlink/?LinkId=260882 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.51 EF 6.0.2 VS2013 It see

Cloud as a Story - Vunvulea Radu

Search This Blog