The topic of hardening sprints is much-discussed among Agile practitioners – sometimes in purist indignation but more in expressing helplessness, I feel! Let’s first understand what a hardening sprint is – it is an additional sprint that some Scrum teams run at the completion of all the earlier “regular” sprints. Over time, the hardening sprint becomes accepted as inevitable by organizations and a dragon impossible to slay. Here is our take on an approach that can help such organizations to muster the courage and will to at least cut the dragon to size if not eliminate it. Step #1:...Read More
Author: Shiv Sivakumar
Some time back, I had the opportunity to read about the growth paths available to a Scrum Master (SM). The thinking behind this was that the SM role for a given Scrum team is not forever. There comes a point in time when the team is able sustain Scrum adoption by itself and the need for Scrum Master assistance reduces significantly. In that case, what does the Scrum Master do keep herself gainfully occupied and grow career-wise? Mike Cohn in his blog talks about the following options: Take on the SM role for additional teams and in more complex product environments...Read More
Barbara Jones had been a Scrum Master for a year with a team and had done a good job getting the team to a good level maturity in Agile adoption. The need for her support had reduced over time. It occupied Barbara just for a few hours per week on an average. Barbara approached her manager Jeff Sanders for additional responsibility to be SM for a few more teams. Jeff listed projects which were possible candidates for Barbara. Some of these were just starting up and had no designated Scrum Master as yet. Other projects in the list were...Read More
Allrounders is a team of 9 persons supporting some of the important applications in the organization. They were using Kanban so far and are doing well as a team. Anil, their Scrum Master is efficient and is helping the team focus on improving cycle time etc. Last month one of the applications they were supporting was phased out and the team was asked to work on couple of important initiatives that the organization is focusing on for the current year. Team members are not very experienced in handling development work and are looking forward to Anil for help. Anil himself has not handled a team doing this kind of work and is discussing with the team how to proceed etc. Can you help Anil with some possible approaches? Suggested Solution Anil will have to first find out what how much of teams’ capacity is available after the phasing out of one of the applications. Based on that he can plan how much work can be taken for the new initiatives. Possible steps which Anil can take are: 1. Observe the cycle time and throughput and determine roughly how much capacity team has to work on initiatives. 2. Understand the stories defined for the new initiatives and plan the release. 3. If the support work has significantly reduced, team can probably adopt the Scrum model and accommodate support work...Read More
It is well known that Scrum is very popular with Development teams while Operations teams prefer Kanban as it suits their nature of work best. That is because development teams deliver an incremental product over iterations and they have to plan and deliver a product as a team. Normally the scope does not change within an iteration for the committed work. For all this Scrum is ideal as it has planning, daily stand-up, review and retrospectives. Support work on the other hand is unpredictable even on a daily basis. So support teams pick the next priority item in the...Read More
- Sprint Planning in distributed teams… Patterns… SAFe
- What’s Important – Breaking Silos or Uniting the Purpose?
- Should Story Points (as a size measure) be comparable across teams?
- 3 Simple Tips for Building Distributed Teams
- CHOW #120 – Workacholic Manager
- CHOW #119- Avoiding ‘Watermelon Metrics’
- CHOW #118- Product Visioning – Mapping Features with Advantages and Benefits
- CHOW #117- Project Health and Project Status