Last week, when I was at the Much Ado about Agile 2 conference in Vancouver, I had a conversation with Dan Rawsthorne. He said he wants to make sure his teams have demo-able software, not necessarily release-able.
Interesting. So what would have to be true for an agile team to have “just” demo-able software, not release-able?
- If the entire team is large (think Scrum of Scrums) and the product has big features. Each smaller team can do their user stories, but they may not be able to totally integrate each user story with each other until enough user stories are done.
- If there's a hardware component and it's not done yet.
- I keep trying to think of a third reason, and I'm stuck 🙁 I bet you can help.
Even if at the end of an iteration, the product is “only” demo-able, that still means the team has integrated among themselves.
Thanks, Dan, for the jiggle.