When we say a Fixed Bid project, what comes to our mind? Are we talking about fixed Scope, Budget and Time? Assuming we are a service provider and all the parameters are fixed for the project, is it possible to do a Release Plan with out losing the spirit of agile?
Suggested Solution:
There are various ways we could approach this situation without losing the spirit of Agile.
Usually, when we hear the word ‘Fixed Bid’ we assume that all the three parameters (Scope, Time and Cost) are fixed. But, that may not be the case in the real world. As a service provider, if we ask our client, which one of the three parameters is critical, or non-negotiable, we may identify the levers. In some cases, the cost may be a constraint. Then there could be some flexibility in scope and time. If the time is critical, say some compliance or security-related issue, the cost and to an extent the scope, might have some room for adjustments.
Once we understand, through meaningful collaboration with the client, the critical parameter(s) and our levers, doing a release plan is easier. The objective of the release plan is to bring in reasonable predictability and adaptability. If the cost is fixed, we could work on a range in the timeline. Similarly, if the timeline is fixed, then the scope could have a range.
I’ll be elaborating on this topic with more examples in my subsequent blogs.
2 Responses
Velocity of each individual iteration will be a different figure. There are many ways velocity gets impacted. Apart from planned absence (planned leave, training etc.) and holidays, there could be unplanned absences caused by illness, personal emergency etc. which impact velocity. User stories that do not get completed in an iteration get moved to next iteration. This brings down the velocity of the iteration where the story was started and bumps up the velocity of the iteration where it got completed. This being the situation, good practice is to take an average of last five or six iterations as the velocity of the team. Team stability is another factor that impacts velocity. Teams that have higher churn will see higher volatility in velocity. Other factors such as change in technology, adoption of new tools, increase in automation, will also impact velocity either positively or negatively! However, if team is stable and has reached “performing stage” steady rise in average velocity will be seen over a period of time till any of the factors mentioned above comes into play and impacts it.
Thanks Milind, fully agree with your comment.
Finally, irrespective of the increasing trend in velocity, there is improvement for sure. This cannot be missed, if observed. One of the intent of my blog is to encourage this observation, by taking a mildly provocative stand.