Ankit is a scrum master for a team. Their team is responsible for making small enhancements to their product. They also pick up some new features to be added to their product. Ankit’s team is Agile and they follow Scrum. As they have been following Scrum, they report their velocity and progress at the end of the sprint as part of their sprint review and demo to their stakeholders. Their business manager, Linda – a very senior person in product management informed them that the product will need a new feature. Their product owner walked them through the requirements,...Read More
Author: Harish Achappa Kallira
This blog is more to share an observation and get inputs from as many folks as possible on sprint planning: Often, teams do their sprint planning in the following way: 1. There are a set of stories (mostly) ready for an upcoming sprint.2. Hence, the teams estimate their stories to pick a few stories from the backlog3. The team uses story points – adopting Fibonacci series (I have not come across anything else!)4. They may play planning poker, or, someone from the team proposes a number.5. The team estimates stories and then pick stories until their velocity is reached.6....Read More
A backlog must resemble a good folktale- that people will talk about after they have listened to it, allowing freedom to interpret and be able to be told in multiple variations without changing the outcome. Product Owners play a direct role in creating backlogs that teams can own and understand the problem that they are trying to solve. Product Owners need to become story tellers than requirement specialists. My experience in working with teams has been that the backlog usually appears empty or stuffed with disparate items early in the lifecyle. Once clarity is available on what needs to...Read More
Amit is a lead for a team. His team has a clear charter to improve the quality of client engagement information available to their sales team. Towards this, the team is working with analytics and the latest in software – machine learning. The team is following Agile and does quarterly planning; and here-in lies their challenge. Earlier, quarterly planning used to be figuring out how much the team feels they can do. They knew what they were buildin in a reasonable way In this current charter, the team does not know what they are going to do – they...Read More
An advantage of considering Design Thinking as an Innovation LEVER is that it clarifies what Design Thinking actually is – and what it is not. Design Thinking provides a structure – for individuals and teams to look closely at challenges, understand the problem before moving to create a solution. Hence, practising Design Thinking will also need tools and skills required to use the structure effectively. Each step of creating a response has tools that have been used for ages. Tools for research, for generating ideas, to validate assumptions and to build solutions incrementally while getting constant feedback. Effective use of this structure requires multiple skills – a strength that only a poly-skilled team can bring in. It is critical to build facilitation skills for effective collaboration across teams and stakeholders with these skills and knowledge. Without these tools and the collaboration skills, the structure that Design Thinking provides will end up being procedural – risking Design Thinking being tagged as a fad. In subsequent posts, I plan to write about: The relevance of Design Thinking, Agile and DevOps in the lifecycle of businesses (are they the Three musketeers of innovation?) Challenges in looking for and creating innovation when teams are distributed. Introducing Design Thinking in to teams – and in existing environments. I will greatly appreciate you writing and responding on this post – to further me on the...Read More
- Making Meetings Effective and Productive
- Great Scrum Masters – Endangered Species?
- Sprint Planning in distributed teams… Patterns… SAFe
- What’s Important – Breaking Silos or Uniting the Purpose?
- CHOW #123 – Help Kamal’s mission be successful
- CHOW #122 – Help Prakash create better Epics
- CHOW #121 – Measure of Scrum Masters
- CHOW #120 – Workacholic Manager