Thank you Michael.

Much of the literature on Scrum and Agile is silent in regard to planning and understanding activity patterns (or use cases, etc.) Similarly, it is relatively silent about understanding and planning coherent user experience. Both of these exist “outside of” individual user stories, and consequently are often ignored by many fledgling agile teams. As a user-centered development shop doing agile, I know we struggled with this (and sometime still do).

Your blog and book have been useful to our teams in finding agile, lightweight ways to do this planning without falling back on “big up front” design. Thanks!

I view a story as valuable if it is necessary to turn the product vision into a successful product.

I find that the features on the product vision board often end up as epics on the product backlog. I would suggest to create models only for those epics whose relationship with user roles or other epics needs to be explored further.

Do you see a tie up between features on the Vision board and this epic model? Could a model be created for each feature?

Never considered the activity diagram approach but essentially are we not working with use cases, flows etc… (Nothing wrong with that btw, I’m just saying they seem to have converged – Use Cases are commonly perceived as non-agile). In the example above, you have a story “Enter user name and password”, I’ve questioned whether this in it’s own right has value (as part of INVEST) to the customer?