Lean Procrastination
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.
Articles by scrumexpert
Distributed Scrum
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.
Using Sagas as a Strategic View of Epics
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.
The Dark Side of Metrics
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.
Using Large Number in Planning Poker
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.
Using Agile Tools
Even if the the Agile Manifesto declares that you should value “individuals and interactions over processes and tools”, this doesn’t mean that you shouldn’t use any tool. The authors of this article shares their experience using agile tools and explains why they prefer non-software tools and why you should be carefully pick the tools that will support your practice and your company if you pick any at all.
Managing Risk in Scrum
The topic of Managing Risk in Scrum projects is addressed by Valerie Morris in these two blog posts. The first part discusses the five risk areas found on most software projects: intrinsic schedule flaw, specification breakdown, scope creep, personnel loss and productivity variance. The second part compares risk management practices between traditional project management and Scrum.