In my last blog I had shared the first of the two common patterns that I have encountered in my Agile Coaching experience related to the cadence of the team, here I am sharing the second one. The scrum team has a well-defined backlog and good clarity on what is expected in the release. They start their iterations and make good progress, delivering chunks of potentially shipable increments every iteration. They seek and get feedback from the PO, take in their stride any new requirements that are discovered or changes that are needed. They do their retrospectives and improve...Read More
Author: S Vasudev
Prasad the Agile coach for a team, has coached the “Enchanters” scrum team for a couple months and has completed the initial Agile Maturity Assessment. The team was slow to change at the beginning, but Prasad with his interventions has been able to turn around the team to adopt Scrum in the right spirit and with enthusiasm. The assessment is not a surprise to the team and highlights the areas where they have done well and those that they could improve. Prasad has facilitated a meeting to walk thru the assessment and arrive at a set if action items...Read More
I have seen two patterns in my Agile Coaching experience, I am sharing the first one in this blog, the other will follow soon. The Scrum team has a large number of items in its Product backlog, typically they are doing enhancements, to a fairly mature product-line that is still far from its sunset. The team adopts Scrum and start tackling items from their large and active Product backlog. Iteration after iteration they keep delivering enhancements, to their product. Backlog gets populated with Release related items in sync with their ad-hoc and periodic Release, which they take it in...Read More
Wise Eagles (WE) and Bright Kites (BK) are two teams located in India and US and share just a few overlap hours. BK need to use/ work on code that was developed by the WE in the past. Team members from BK often reach out to WE team members to get specific details on the code and the WE team members help. The problem WE face is that there is repeat request for the same information, which annoys them. But what took the cake was after a Developer from BK got had a Knowledge Transfer (KT) session on a...Read More
Agile Scrum teams that I have interacted with have their team norms or working agreements in place. This is in place either at the start, or within a few sprints. Typically, it starts with an attempt to address some aspect of collaboration within the team. The team gets together and works out an approach by consensus and documents them as team norms or the working agreement. It helps for the coach to nudge them to put these up as the team norms. Many of the teams that I have coached, initiate this for the Daily Scrum or the daily stand up, when there...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 #119- Avoiding ‘Watermelon Metrics’
- CHOW #118- Product Visioning – Mapping Features with Advantages and Benefits
- CHOW #117- Project Health and Project Status
- CHOW #116- High Performing Team