SCRUM butt and local optimum

-
Many projects do not become completely agile. They start by telling we will use SCRUM for this project. A small training is provided and team goes agile. There will be some benefits in the beginning and some short comings. But definitely project is not a huge success? What is going wrong? Trigger happy top management will pull the plug telling we tried agile and it is not working for us.
When following SCRUM for the first time it is better to check whether SCRUM is followed to the full extent. As the old say it is the traditions which allowed humans to survive and evolve. It requires wise and old to tell what the tradition is. You can decide how to follow agile once you become expert on agile. How do you decide whether you are following agile to the full extent? Jeff Sutherland has developed a scoring system. This is called Nokia Test (or SRUMButt test). You can read more about this in Jeff Sutherland’s blog http://jeffsutherland.com/scrum/nokiatest.pdf.
Most of the teams claiming to follow SCRUM are only following half of the SCRUM framework. This qualifies to be called SCRUMButt. What is the problem of SCRUMButt? Each team which starts with SCRUMButt sees the benefit in the beginning. But these benefits evaporate over time? This is explained in Theory of Constraints as local optimum. You will be reaching optimum velocity for certain tasks by following SCRUMButt. This does not mean overall project has benefitted.
Let us see a scenario which is typical in SCRUMButt. There is no one dedicated as Product Owner or customer does not have time to see the demo and plan the next sprint based on it. Your team will be developing at a velocity which 3 or 4 times the traditional method. If the demo is postponed then the features get piled up. When the demo happens customer does not have enough time to dedicate to all features and ignores key changes required. This results in a bad product being developed.



SCRUMButt always results in Local optimum which results in fatigue. Compare to the analogy of a Traffic bottleneck. You have a 6 lane highway leading to a city with only two lanes. When all the travelers are going to the city there is a big bottle neck at the entrance of the city. Compare this to testing of or customer acceptance of your project. You develop at a speed possible in a 6 lane and deliver. Then there is a big wait for the next phase. When you follow SCRUM delivery is complete at every sprint. But SCRUMButt delivery waits and team waits. This causes frustration and fatigue. Local optimum does not help anybody. It might be good to have it in traditional waterfall model. It gives a high which is short lived.

Comments

Post a Comment

Popular posts from this blog

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

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 available now. 
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 thi
Read more