User stories are supposed to reflect the 'human' side of the IT. The should be easy to understand and not too technical. Ok, but what should happen when you're asked to prepare user stories for strictly technical projects/products?

Agenda:
1. Understanding target audiences
2. Understanding scope
3. Use or not to use user stories -> scope management
4. Fitting the requirements to 'user stories' oriented tools

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Agenda:
1. Understanding target audiences
2. Understanding scope
3. Use or not to use user stories -> scope management
4. Fitting the requirements to 'user stories' oriented tools

Learning Outcome

How to deal with technical User Stories in Scrum? Is it possible to write good technical User Story? Find out during my talk!

Target Audience

IT crowd :)

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal