Entire generation of IT managers set to lose jobs as frugal companies embrace automation?

-
Recently read an article in Economic Times Entire generation of IT managers set to lose jobs as frugal companies embrace automation . I started analyzing which areas of project management are lost to agile and which to tools (automation).

Integration Management: This is redundant to some extent because of agile adoption in projects. Also depends on the kind of projects. But in most projects which are agile we do not need a manager for this.

Scope management: When you take things in small sips, no need to worry about breaking your belly. Your system can handle the small sips easily. Scope is not an issue if you are agile.

Time management: When you are agile you build what gives more bang for the buck. There are also many tools which track remaining effort, velocity of the team which again do not need a full time manager.

Quality management: Team defining definition of done and follow do not need a person to manage quality. Team will do it.

Communication management: Agile prescribes communicate well. If team can communicate well with the product owner no need of management here. If team cannot then  solve the issue. Having a person to manage communication will be like applying a deo to stop the decay.

Cost management: This is a key area for all projects. Control the cost. This cannot be achieved with a tool. But telling the budget to the team and what is expected gives better result. Is a manager needed to manage the cost? Depends on how much is being spent. Manager also add to the cost head. Product owner is the best person to handle this.


Risk management, Human resource management, Procurement management, Stakeholder management : These need a person to manage things. Tools can help here. But a person is needed to move things. That is why SCRUM defines product owner.

My take is most projects which follow agile do not need a project manager full time. There are some areas like cost, risk and procurement which will be taken care by the product owner. 

Comments

Post a Comment

Popular posts from this blog

Greedy computing with API

-
Image
 We all know computing resources have a cost. Memory, long term storage, transportation and computing all have their own costs. There are lot of scenarios where your API end point won't be able to respond in time. These are scenarios where you need to use more resources to provide a response. Let us be greedy with our resources and explore different patterns which can solve this. Polling  This is a commonly used pattern where the caller initiates a process. Then keeps on checking if the process is complete. If the process is complete then the caller reads the data needed.  This is a good pattern when both systems are part of the same organization. At least developers of caller and callee should be able to discuss this implementation.  Call back This is an improvement over polling pattern. Here the caller supplies a call back URL to the long running process. Once the process is complete it calls the callback URL and informs the caller that process results are availabl...
Read more

ChatGPT for cavemen

-
Image
I heard a lot about ChatGPT and thought to come out of my cave to find out what the hype is about. Is it going to eat all my lunch or eat me for lunch?  Like any product I gave it all my details and signed up. I asked it about quantum computing an it gave some answer. So far so good. Next day I wanted to check its blogging skills. So I opened chatGPT and I got this . I checked throughout the day and it is still down. So it won’t eat me till it is fed few more servers.  Continuing after it was up.  I asked it to write a blog about itself. Here is what was generated by chatGPT.
Read more

Event driven architecture for micro services

-
This is a work in progress. I am designing an event driven architecture to be used in systems using micro services. Micro service architecture is popular because it solves few problems in development process. While it solves some problems it also brings in new problems to the table. Bad designs impact micro services harder than monoliths. But this is thought is for another time.  How micro services talk to each other. In a monolith you have one gigantic database, or you can easily call another component to process the information. In a microservice you can use a Que (or event bus) to pass the information. This is the problem I want to discuss. Main issue with que is it is not designed for this scenario. There are few products which give a good solution by providing a subscription-based approach. But these are large implementations. Using these is similar to bringing an excavator to plant a sapling in your garden. Yes, many people go with using these large implementations to resolve...
Read more