Monday, May 17, 2010

My First Posterous Post

This post advocates putting "Theme" at the top of the project pyramid. Others put Epic at the top of a given project defining "Theme" as a collection of user stories around a functional area.

However, I think there is real value in putting something like Experience Statement at the top of a project management graphic.Doing so focuses the project not around the thing trying to be built, but rather the user's experience when using the thing. Thus, the thing is more changeable as the team delves deeper into the implications of that Experience Statement on the Epics, User Stories, and Tasks that make the experience happen.

The other thing I think it does is build a bridge between the language of value propositions and minimal viable product with the actual development of the value propositions and products. Why? Because the value of a product depends entirely on the experience it delivers. 

It's user centric. I feel that sometimes even Epics are at risk of being completely off base because there is no definitive statement above them telling the viewer of the epic why the epic exists.

The Hierarchy of Agile Requirement Formats - Themes, Epics, User Stories, Tasks
from Agile 101

Another value of placing the Experience Statement at the outset is that it forces a development team to consider different roles and the related functionality around them in and of themselves. Instead of trying to account for each role as a subset of the project, the different types of users get their own dedicated focus. 

I've embraced Agile because it provides a simple way that both developers and their clients can gather around requirements without navigating too learning-curve laden jargon. Tell good stories, make those stories come true, and you're done. However, there has still been the problem of making sure that the stories your write are what people want to experience. That's where the Experience Statement is pivotal. 

The Experience Statement is the value proposition of the product told from a user's perspective. A good Experience statement will help the team determine which Epics, Themes, and User Stories are created and how they are prioritized.

Posted via email from Interactivist

0 comments: