Requirement slicing
description
Transcript of Requirement slicing
Requirement slicing
ExilesoftJohannes Brodwall, Chief scientist
Exilesoft
Part I:
Giving good demos
Problem: Showing database in demo
Problem: Showing code in demo
Problem: Showing low-value features
in demo
Part 1c statement
Part II:
Slicing requirements
Rainbow plan
What is nice, what is required?
What can we show?
Part III:
What did you learn
«Customers»
What did the teams show at demos?
Teams
Sprint overhead
Demo readiness
Sprint planning meeting
Who is your…• Customer?
• Product owner?• User?
«Business analyst» (and «developers»)
What was your product backlog
ordering?
«Developers»(and «analysts»)
Technical platforms
Technical debt?
«Everyone»
Can we demonstrate value every 15 minutes?
Can we demonstrate value
every 2 weeks?
Conclusion:
Delivering value is a matter of practice and
reflection
Thank [email protected]
http://johannesbrodwall.comhttp://exilesoft.com
http://twitter.com/jhannes
Demonstrate value every sprint