If you’ve heard the term “dual-track development” before, this article explains where it comes from, and what it means. Here are the key points:
- Development work focuses on predictability and quality
- Discovery work focuses on fast learning and validation
- Discovery and development are visualized in two tracks because it’s two kinds of work, and two kinds of thinking
- Discovery is a necessary part of product development. Practice it with the same
I wrote this article, a rant really, in April 2014. It was lost in a website shuffle a couple years ago, and someone recently asked if I could put it back. So here it is. But, it’s been slightly renovated from the original version to bring it up to 2017 code.
Backlog grooming meetings are often the most unproductive and painful meetings in Scrum. If yours are great,
An Opportunity Canvas is a simple one-pager I like to use to facilitate a discussion about a new feature or capability. It’s put together in the spirit of the Business Model Canvas or Lean Canvas which are fabulous tools for discussing new products. But, unlike those canvases, the Opp Canvas assumes you’ve got a product already out there so you won’t need to reconsider the operational or revenue model – which is what
HOW TO DO USER STORY MAPPING
In this podcast with Talking Code, released 7/14/2015, Jeff teaches us how to map user stories by focusing on the user’s journey to an outcome. He shares his opinion on the notorious “MVP” and how he helped Gary Levitt build his MVP with Mad Mimi.
People have gotten fixated on the story template. But that’s not the important part. — Jeff Patton
More of what’s in this podcast:
I have a fundamental problem when teaching Story Mapping in a class or workshop. That is, participants never have enough time to build a complete enough backlog to explore all the different release and development strategies that having a full backlog gives you. That sucks. But, I have a simple solution. 1476