requirement slicing

32
Requirement slicing Exilesoft Johannes Brodwall, Chief scientist Exilesoft

Upload: xandy

Post on 23-Feb-2016

49 views

Category:

Documents


1 download

DESCRIPTION

Requirement slicing. Exilesoft Johannes 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. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Requirement slicing

Requirement slicing

ExilesoftJohannes Brodwall, Chief scientist

Exilesoft

Page 2: Requirement slicing

Part I:

Page 3: Requirement slicing

Giving good demos

Page 4: Requirement slicing

Problem: Showing database in demo

Page 5: Requirement slicing

Problem: Showing code in demo

Page 6: Requirement slicing

Problem: Showing low-value features

in demo

Page 7: Requirement slicing

Part 1c statement

Page 8: Requirement slicing

Part II:

Page 9: Requirement slicing

Slicing requirements

Page 10: Requirement slicing

Rainbow plan

Page 11: Requirement slicing

What is nice, what is required?

Page 12: Requirement slicing

What can we show?

Page 13: Requirement slicing

Part III:

Page 14: Requirement slicing

What did you learn

Page 15: Requirement slicing

«Customers»

Page 16: Requirement slicing

What did the teams show at demos?

Page 17: Requirement slicing

Teams

Page 18: Requirement slicing

Sprint overhead

Page 19: Requirement slicing

Demo readiness

Page 20: Requirement slicing

Sprint planning meeting

Page 21: Requirement slicing

Who is your…• Customer?

• Product owner?• User?

Page 22: Requirement slicing

«Business analyst» (and «developers»)

Page 23: Requirement slicing

What was your product backlog

ordering?

Page 24: Requirement slicing

«Developers»(and «analysts»)

Page 25: Requirement slicing

Technical platforms

Page 26: Requirement slicing

Technical debt?

Page 27: Requirement slicing

«Everyone»

Page 28: Requirement slicing

Can we demonstrate value every 15 minutes?

Page 29: Requirement slicing

Can we demonstrate value

every 2 weeks?

Page 30: Requirement slicing

Conclusion:

Page 31: Requirement slicing

Delivering value is a matter of practice and

reflection

Page 32: Requirement slicing

Thank [email protected]

http://johannesbrodwall.comhttp://exilesoft.com

http://twitter.com/jhannes

Demonstrate value every sprint