Every project manager would do anything to get an extra week when the project is in trouble but time is a variable you may not be able to adjust.
I'm 99% sure that you won't be able to buy time unless you are able to drive the DeLorean to hire an extra dev in the past and go back to the future to use it. Actually, if going back to the past to fix wrong decisions was possible, we would be all awesome managers :)
So for regular managers, as we are, we need to plan in advance and get ready for that extra help when the project needs it.
A developer got sick, new mandatory requirements are coming, we need to fix defects asap or an unforeseen risk is now an issue are some of the items in a very long list. After all, the only thing we know about a plan is that things won't go according to it. [If you want to read about strategy check this].
Here is a list of do's and don'ts about bench and reserves.
Dont's:
- Include reserves as part of the sprint plan. The most common mistake is to use the reserves in the game, this turns them into regular players and leaves you with an empty bench. There is no extra help to add if you need it.
- Leave the reserves out of the team. Opposed to the previous item, reserves tend to be left apart from the team. Nobody knows who they are or what they are doing. The problem with this approach is that the reserve won't be ready to move rapidly into a team role and help. Most probably, they won't know anything about the project and you will have to train them before they can start.
Do's:
- Assign them to explore the upcoming sprints. They are not considered part of the team capacity, so you still have those people in bench and they are also trained and up to speed with the project to be ready to jump on it. In addition, you can get some extra risk mitigation by exploring upcoming sprints.
- Change the person who is in bench each sprint. Similar to games, players need some time to sit back and see the game from outside.
No comments:
Post a Comment