Karl Scotland – Using Agile to Deliver Value
In order to achieve some value…
Liz Keogh says “RIP As a… I want… So that…” (via David Anderson). This also ties in with what Chris Matts has being describing as Feature Injection. What I like about this idea is that it provides the link between the MMF and the User Story.
Liz proposes a new format:
- In order to <achieve some value>
- As a <role>
- I want <some feature>
The <some value> is a MMF – Minimal Marketable Feature. However, where minimal is still quite big, then MMFs can be broken down into <features>, which are more traditional User Stories. Thus the format gives a simple way of managing the relationship between the small incremental functionality pieces, and the larger value pieces.
Thanks Liz and Chris!
No related posts.
| Print article | This entry was posted by Karl Scotland on June 16, 2008 at 5:07 pm, and is filed under Agile. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |
No trackbacks yet.
The Economics of Raking Leaves
about 2 months ago - 3 comments
I was out in the garden this weekend raking up leaves. Having read Geoff Watts recent post about using Scrum to clear his leaves – and as someone who can’t do anything without thinking about work (see Kanban and Quad Biking!) – my mind turned to how I would use Kanban Thinking to approach the More >
Starting An Agile Transition With Why
about 9 months ago - 1 comment
In March this year I gave this keynote at the Rally Agile Success Tour in London. This is a video of the talk, followed by a write-up. The slides can be downloaded from here. People don’t buy WHAT you do, they buy WHY you do it. Simon Sinek says that this is the fundamental More >
People and Process: Two Sides of the Same Coin
about 1 year ago - 1 comment
I wrote this short article for JAX Magazine, but it seems JAX doesn’t want to make it easy for people to access the content (you have to register to get a download link which only works once). So I’ve decided to post the article here as well. Its an evolution of some of my thinking More >
A Model for Creating a Kanban System
about 1 year ago - 4 comments
This post is a high level overview of the model I use when I think about Kanban Systems. As the saying goes, “all models are wrong, some are useful”. This is what I currently find useful based on working with teams and organisations in recent years. At the heart of the model is Systems Thinking. More >
From KFC Development to PVC Systems
about 1 year ago - 2 comments
I’ve been revisiting my earlier KFC Development work in light of my more recent focus on five primary practices. This is an brief overview of what’s changed, and what my mental model looks like now. Firstly, I’ve stopped referring to the practices as such, in favour of calling them aspects. Practices always felt slightly wrong, More >
Isn't Kanban Just a Task-board?
about 2 years ago - 12 comments
While the word Kanban comes from the Japanese for “visual card”, the term Kanban as used by the Kanban Software Development community, represents much more than a standard task-board, or team-board. Additionally, the Kanban Software Development community have not tried to replicate the mechanism of the Toyota Production System kanban tool exactly, but have taken More >
Kanban and the New New Product Development Game
about 3 years ago - 3 comments
One of the primary origins of Scrum is “The New New Product Development Game” by Hirotaka Takeuchi and Ikujiro Nonaka, published in the Harvard Business Review in 1986. This is the article in which the contrast is made between a traditional sequential or “relay race” approach and a holistic or “rugby” approach. Hence the name More >
Kanban, Flow and Cadence
about 3 years ago - 58 comments
Intro There has been some noticeable increase in interest in Kanban recently, with a number of people asking for more basic info, and more people writing new blogs and articles. This is my attempt to describe in more detail my take on it all, which I refer to as Kanban, Flow and Cadence. Kanban – More >
The Anatomy of an MMF
about 3 years ago - 3 comments
I’ve been involved in a number of discussions about how User Experience work fits into an Agile process. As a result a trying to articulate my position, I’ve come up with the following explanation of the anatomy of an MMF. The following diagrams assume the following key: Lets start by looking at a typical waterfall More >






about 6 months ago
This makes a lot of sense. Just to clarify, so what you are suggesting is (changes in capital):
•In order to
•As a
•I want
about 6 months ago
Yes. That’s an alternative suggested format.