Cost of change

-


Traditional project's cost of change.


What is the cost of change? Above diagram will tell you it increases as project progresses.This diagram is from PMBOK which tells cost will grow exponentially and stakeholder influence will reduce as time progresses. Probably this is not a good thing as stakeholder should have influence throughout the project. In any dynamic business changes are inevitable. Business is dynamic and will require change in the project when the project is progressing. This model puts a high price for the change which cannot be avoided.

Now let us see why the cost increases in the traditional projects.

  • Traditional projects are executed by a plan. Plan is used to reduce the cost of the project.
  • There are no reusable (automated) tests.
  • Team need to work as a plan. If plan is not followed there will be wastage of effort. This is blasphemy for a traditional project.
  • Since there is a separate testing phase whatever is developed is not tested or not ready for delivery. This causes changes to have more regression and more expensive.
Let us see the cost of change curve for a SCRUM project.

Cost of change for agile SCRUM


As you observe cost of change increases with time. But this is not exponential increase. Now let us analyze why cost is in just going marginally up and not reaching the orbit?

  • Work worth a month or 15 days is taken at one shot. Whatever is implemented is tested and ready for production.
  • All possible test cases are automated. This avoids wastage of time in testing.
  • Since work is taken in smaller bites it is easy to take changes.
  • There is no mind block for changes.
  • Changes look simple as they come in after a sprint and you will know the reason for them.
  • Focus on completing the tasks and make them production ready rather than follow a plan.
All these are the reasons for reducing the cost of changes, Customer should not pay a arm for getting changes implemented :-)


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