Project Management

The Italian Dinner - How work flows from Release to Story to Task w/ Judy Neher, CST

From the The Reluctant Agilist Blog
Adam Weisbart | Agile | Agile 2013 | agile 2014 | agile 2015 | Agile 2017 | Agile 2018 | Agile Alliance | agile coaching | Agile Metrics | Agile Practice | Agile Teams | agile transformation | Agile Transition | agile2014 | agile2015 | agile42 | Agilistocrats | Alistair Cockburn | Atlassian | autism | Bas Vodde | BigVIsible | Bob Tarne | book review | Brian Bozzuto | business agility | carson pierce | Center for Non-Violent Communication | Certification | Certified Scrum Master | Certified Scrum Product Owner | Chet Hendrickson | Chris Li | Coaching | commitment | Communication | conteneo | Craig Larman | cross functional teams | CSM | CSPO | DAD | Daniel Gullo | Dave Prior | David Anderson | David Bernstein | David Bland | David J Anderson | Dhaval Panchal | diana larsen | Digital Agency | Digital PM | digitalpm | Disciplined Agile | Disciplined Agile Delivery | Distributed Teams | Don Kim | dpm | dpm2013 | drunken pm radio | drunkenpm | drunkenpm radio | eduscrum | emotional intelligence | empathy | Enterprise Agile | Essential Scrum | esther derby | Excella | Gangplank | Gil Broza | Howard Sublett | Individuals and Interactions | Jean Tabaka | Jeff Sutherland | Jesse Fewell | Jessie Shternshus | jim benson | johanna rothman | john miller | Jukka Lindstrom | Jutta Eckstein | kanban | Kanban Pad | kanbanfor1 | Ken Rubin | Kenny Rubin | Kim Brainard | lacey | Language | Large Scale Scrum | Larry Maccherone | LeadingAgile | lean | Lean Kanban North America | LeanKit | LESS | lkna | luke hohmann | lyssa adkins | Maria Matarelli | Mark Kilby | Marshall Rosenberg | Michael Sahota | Mike Vizdos | Modern Management Methods | modus cooperandi | Natalie Warnert | Nic Sementa | Non-violent communication | North American Global Scrum Gathering | NVC | Olaf Lewitz | Øredev | Øredev 2013 | organizational agility | Organizational Change | overcommitment | Patrice Colancecco Embry | Paul Hammond | personal kanban | personal productivity | personal project management | Peter Saddington | PMBOK | PMI | PMP | podcast | portfolio management | Product Development | Product Owner | Product Ownership | productivity | project management | Project Management Institute | Rally | Release Planning | reluctant agilist | Renata Lerch | retrospective | Richard Cheng | Roman Pichler | Ron Jeffries | SAFE | Safety | Sallyann Freudenberg | scaling agile | Scaling Scrum | Scott Ambler | Scrum | Scrum Alliance | Scrum Gathering | Scrum Master | ScrumMaster | self organizing teams | SGPHX | SGPHX 2015 | Shane Hastie | social engineering | SolutionsIQ | SoundNotes | sprint planning | Team | teams | Temenos | The Improv Effect | Things | Tom Perry | troy magennis | User Stories | value | Vivek Angiras | waste | Waterfall | What We Say Matters | why limit wip | women in agile | Woody Zuill | show all posts

About this Blog


Recent Posts

When Sprint Planning Is Like Hunger Games with Meghan McInerny

Practicing Agile at Home with Yvonne Marcus

Using Outcome Based Planning at Home to Effect Social Change

Product Ownership and Online Education with Braden Cundiff

The Business Agility Canvas with Karim Harbott

When I am teaching CSM and CSPO classes I frequently get questions from students who have trouble understanding how work flows from the release level down through product backlog items like User Stories on down to the task level. I do cover this in class but for some, it is not so easy to see. 

In hopes of resolving this, I asked Judy Neher, a fellow Certified Scrum Trainer, to help me work through a metaphor that I hope will provide clarity on how we take work from Releases to User Stories to Tasks, how they tie back to strategy and vision and how Epics and Themes fit in as well. 

If you'd like to reach out to Judy with follow up questions, here is her contact info:

Judy Neher

Posted on: December 27, 2019 01:42 PM | Permalink

Comments (4)

Please login or join to subscribe to this item
Dear Dave
Interesting this interview with Judy Neher
Thanks for sharing

I liked the metaphor of the Italian dinner

This is a great metaphor. I would suggest that the problem however is not so much that some people don't get how to go from the big picture to the tasks, but that the common Agile model of requirements decomposition is missing a key component and that it forces people to bridge the gap. Unfortunately, even when people do bridge the gap, many do it differently and this causes another problem.

What's missing? A 16 year old concept put forth in Software by Numbers: Low-Risk, High-Return Development. They called the term Minimum Marketable Feature (MMF). It's the smallest releasable item for which value can be realized from a business perspective. It's not an epic (epics are larger than this) and it's not usually a feature (features often can't be released on their own) and it's not even the smallest releable thing because sometimes that doesn't make sense. For example, coffee is releasable on its own, but "releasing" it with dessert made more sense.

Note that SAFe redefined the MMF - and what they call the MMF has virtually nothing to do with what the intent of the MMF is.

When I was with Net Objectives, we started using the MMF concept in 2005 and I would attribute a good 50% of our success to it. In fact, i know some companies who transformed their company on their own just with this concept.

After a few months of using this, however, we found a challenge with the name of the MMF was that IT companies said they didn't have products and therefore didn't market. We eventually renamed the term to be Minimum Business Increment as that was more intention revealing and works everywhere.
Here's an article on the MBI

Note how the concept of the MBI ties the big picture (meal / initiative) to the small task (putting cream in coffee). The meal is the initiative. The courses are the MBIs. An MBI may be composed of one or more items (e.g., coffee and dessert), each of these may have tasks (e.g., coffee= coffee itself, cream, sugar).

When I look back on my 20 years experience with Agile and see what cauess a lot of confusion and makes alignment more difficult than it needs to be I attribute the lack of the MBI to be the main cause. Note that an MBI (which is about building something we know to be of value, just need to figure out the details), is quite different from an MVP. That is, with the Italian dinner we have the whole in mind and decompose it. If we were trying to create a new kind of dinner we might start with an appetiser and see how to go from there.

I think i'm going to use this metaphor :) will give attribution. It's a nice concept.

Dear Dave
Although I find the metaphor of the Italian dinner very interesting, I was thinking from a perspective of managing this project

It can be a predictive approach with perfectly defined phases (and phase deliverables):
- Appetizers
- Appetizer
- Meal
- Dessert
- Coffee and digestives

Of course you should not forget to make pre-order purchases depending on the scope :-)

Having reflected on my experience as an amateur cook and watching the Burnt movie, I am convinced that there may be a hybrid approach, being quick to employ

Please Login/Register to leave a comment.


"Never eat more than you can lift."

- Miss Piggy