Yearly Archives: 2013

Impact mapping

The product backlog is boring. After all, it’s just a list, albeit an ordered one. Hence we do things like user story mapping, which makes it a more presentable way at looking at requirements. Nevertheless, more and more teams (and

Posted in Agile, Lean Tagged with: , , , ,

Continuous discovery

The agile way of ensuring level flow is via slicing of the backlog. However, this is not easy to do. We do spikes to learn more and then use that information to create roughly equally sized chunks of stories. I

Posted in Agile Tagged with: , ,

Effective retrospectives

As time goes by, one key observation from team retrospectives is – the core issues do not seem to surface during retrospectives. Most of the issues are superficial or “it was all the the other teams fault”. Two key reasons

Posted in Agile Tagged with: ,

Agile fluency

Recently saw a video of a keynote speech at XP2013 by James Shore, wherein he described the Agile fluency model that Diana Larsen and he put together. One of the key things James emphasized is, this is NOT a maturity

Posted in Agile Tagged with: ,

Improvement theme

In a typical Scrum retrospective, the team identifies remedial action and then tries those in the upcoming sprint. But sometimes, the teams encounter large issues for which the solutions can span over multiple sprints. For example, the team might encounter

Posted in Agile, Lean Tagged with: , ,

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.