Lot of hard work, little output

-
Many times in software development, we are not able to deliver on time. Everyone in the team works hard. But the team is not able to cross the hurdle and push the product to production. Everyone is stressed and worried. At some point blame game will start. 

There is a novel written by Eliyahu M Goldratt called "The Goal". It introduces you to theory of constraints (TOC). It is a good read. 

Let us take Inventory concept and apply it to software development. What is inventory in software development. All the work in progress (WIP) is inventory. When you hold lot of inventory your delivery speed is reduced. This is a proven fact in manufacturing and same is true in software development. All the WIP needs integration before product is complete. When number of WIP items increase integration becomes complex and takes lot more time.

Another concept of interest is bottleneck. Even in software development there is bottleneck. Usually it is resource capacity. In some cases it is specific skill which acts as constraint. It is easy to find the bottleneck in software development. Look where the work is stuck most of the time and you know the bottleneck.

Now let us jump into the solving the problem as per TOC. TOC tells us to identify the constraint and align the work based on constraint. Let us consider the scenario where your work needs to pass quality control. Your app can be complex and QC might have so many scenario's to test. You need to improve the QC capacity by automation or by adding resource. If this is not possible then you need to reduce the work to match QC capacity. If your bottleneck is something else then, try increasing capacity of that. If it is not possible then align the work to bottleneck's capacity.

Why WIP is so bad that TOC recommends to reduce the work? It is counter intutive. Work done is not considered as done till it is in production. Any work which is stuck adds on to the overall complexity of the process. This always leads to confusion and delay in delivery.

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