How can you keep the customer inputs flowing, the teams running and still know where you stand?
By Naama Gafni Lifshitz @ AgileIL12
http://agilesparks.com/CustomerFlowing-NaamaGafniLifshitz
Is long and hard to manageDoes not show “big picture”Is not scenario orientedHard to define minimal scopeCannot be used as a communication tool with customer and teams
2 dimensions: User: typical users = personasUsage: what the users do with the software = usage sequenceInner structure reflects a “day in a life of a persona” = backboneBased on the backbone, you derive the user stories for the backlog
2 dimensions: User: typical users = personasUsage: what the users do with the software = usage sequenceInner structure reflects a “day in a life of a persona” = backboneBased on the backbone, you derive the user stories for the backlog