In this blog post, Matt Archer shares his definition of the Agile Test Lead role and what he thinks they should contribute to Scrum teams. He says that behind the practical aspects of the Agile Test Lead role, there are also subtle connotations of coaching in this position. In his opinion, it is this coaching element that makes many Agile Test Leads valuable for the Scrum team they belong to.
Thom Roach shares with us in this blog post the metrics that he includes in iteration summary reports. The three main statistics he uses are Iteration Statistics summary, Iteration Cumulative Flow and Team Velocity Chart.
This video contains an interview about lean procrastination, which is the postponement of decisions to the latest responsible moment. Olaf Lewitz explains the idea and how it might help larger companies becoming more agile.
This podcast interviews Rini van Solingen about scrum and agile software development in distributed settings where the team is spread across different locations, different buildings or even different countries and continents.
Epics are used to get a bigger picture of user stories, but we need another level of abstraction. We need to bring together the various Epics that describe how our solution will evolve to its final endpoint, and how different functional teams and specialists will interact.
This short presentation explains why software metrics are not the panacea that we thought they might be 20 years ago. This is why moving from a predictive model to a reactive approach is the only rational course.
Mike Cohn wrote an interesting post where he discusses he allows or even encourages to estimate with story points as large as 20, 40, and 100. He explains that they are useful when you need first and not necessarily precise estimate of the general size of a new project being considered.
Scrum Expert Copyright © 2009-2024 Martinig & Associates