Lately I’ve been trying to understand how best to represent Known Unknowns (KU) stories/tasks in the BDC. I’m talking about things like Support cases from customers – things not related to stories from the backlog essentially, that you know you will need to address. I’m wondering how the burndown chart should reflect those.
Invest in your Product Owner
Getting the user stories on the right size, in the right format, in essence getting to the sprint in a READY-READY form (READY actually means READY, not make-believe READY…) requires a lot of cooperation from the Product Owner/Manager. He should understand the value he gets if he INVESTs in stories/features, because it DOES create work …
Big is bad, small is good!
While a lot of what affects an agile team is within the team’s scope of responsibility, the key antipattern I’m talking about today sort of isn’t… A big factor on whether a team can be effective is the size of stories/features on its backlog. A lot of good things happen when stories are Small (See …
The cost of iterations applied to Kanban as well…
My latest blog post was about the costs and challenges of iterations, as well as what to do to overcome them. One of the other things I’m working on is Kanban. I believe Kanban is a great fit to many teams and situations. Specifically doing Scrumban is a great way to get the benefits of …
Iterate / Inspect and Adapt – nice in theory…
On paper, it all makes sense. You iterate in order to deliver business value as early and frequent as possible, and to learn as early as possible about mistakes or opportunities, both in what you build as well as how you build. So far so good. Now, there are several things you hear from teams …
Agile antipattern: Code freezes during each iteration
Bob Hartman, from the Agile for All blog writes about the agile antipatterns insanity – continue doing the same things that always fail, thinking they will work better the next time without changing anything. I agree with every word, especially with the pattern of testing late, and code freezes during each iteration I see this …
agileblog 06/04/2009
InfoQ: Pulling Power: A New Software Lifespan tags: lean, design, agile, agileblog how Kanban metaphor from Lean manufacturing and the Feature Injection template play into Behaviour Driven Development, working together to help us identify the most important software, reduce unnecessary artifacts at each stage of development, and produce the minimum necessary to achieve a vision …
agileblog 06/03/2009
great Kanban Parable tags: kanban, parable, agileblog Posted from Diigo. The rest of my favorite links are here.
Its hard to embrace change…
A key theme in Agile is embracing change. We hear time and again that change is good, we should “welcome change”, yada yada yada. Most teams I see are sick of change. On one hand they are not fully exposed to the business case for change, to the sense of urgency around changing fast. On …