Scrum, but? Scrum, and! Using Scrum and Requirements Engineering Successfully. Susanne Muehlbauer 02 September 2011

Transcription

1 Scrum, but? Scrum, and! Using Scrum and Requirements Engineering Successfully Susanne Muehlbauer 02 September 2011

2 Content Aims & Basics Why Agile SW-Development? Some Basics for Scrum Is RE necessary in an agile Environment? Scrum & RE Where can we find RE in Scrum? Which RE-Methods can we use in Scrum? Questions & Answers the prior permission of

3 Aims & Basics Why Agile SW-Development? Some Basics for Scrum Is RE necessary in an agile Environment? the prior permission of

4 The Software Factory Good idea, but the wrong Analogy! the prior permission of

5 Software-Development is complex Source: Ken Schwaber: Agiles Projektmanagement mit Scrum. Microsoft Press 2007 (ISBN ) the prior permission of

6 Heavyweight goes agile Float like a butterfly, Source: the prior permission of. and sting like a bee

7 Agile Manifesto Source: nach the prior permission of. -7-

8 Agile Values Courage, Communication, Simplicity, Feedback, Transparency, Openess, Trust, Respect Source: the prior permission of

9 And now...? The Agile Manifesto does not tell us about Methods and Processes Source: the prior permission of

10 UC6 Buch hinzufügen 7 UC7 In den Einkaufswagen 8 UR1 möchte ich UR5 Als Standardbenutzer 1 ich Authormöchte Als UR4 UC2 Buch finden 2 UC3 Author hinzufügen 4 möchte ich Standardbenutzer Als kriterien Akzeptanz- Anforderung ID 5 3 Prio Sprint Backlog Sprint Auslieferbares Produktinkrement CI Aufsetzen Versionskontrolle The Agile Manifesto Implementations Known agile Methods: Pair Programming Refactoring Personas Continuous Integration... Scrum Maximal 30 Tage Known agile Frameworks: XP FDD Crystal Scrum... Product Backlog anlegen DB-Struktur aufsetzen Daily Scrum 24 stunden Source: nach the prior permission of. -10-

11 The idea of Scrum * Agile Software Development with scrum, Ken Schwaber, Microsoft Press, 2004 ** Scrum guide, Scrum Alliance, the prior permission of. -11-

12 3 Roles Product Owner Development Team Scrum Master Product Backlog Value/ ROI Order/ Prioritisation Implementation Cross functional Self organizing Servant-Leader Techniques, Practices, Rules Impediments the prior permission of. -12-

13 3 Artifacts Product Backlog Sprint Backlog Burndown Chart Backlog Items Ordered/Prioritized Estimated Selected Backlog Items unchangeable Commited Progress Source: the prior permission of. -13-

14 3 Meetings/ Events Sprint Planning Daily Scrum Review Retro Why What How Inspect & Adapt Communication Focus Results Development Process Inspect & Adapt the prior permission of. -14-

15 Scrum & RE Scrum Documentation [SUT10]: Where can we find RE in Scrum? Which RE-Methods can we use in Scrum? [ ] refining (or grooming ) the Product Backlog: This includes detailed requirements analysis, [ ] Scrum is silent on how this work is done [ ] the prior permission of. -15-

16 The Product Owner in the project organisation Requirements Engineering Product Owner Requirements Engineering Scrum Master Development Team Stakeholders Scrum Team the prior permission of. -16-

17 Soruce: Source: Responsibilities of the Product Owner Product Backlog Clarification of Backlog Items Value of the work (ROI) Prioritization and Order of Backlog Items Inspection of product increments Release Planning Being a Product Owner is a full-time job

18 Soruce: Soruce: Source: Capabilities of the Product Owner Project Management Communication skills Know How within the Business Domain Requirements Engineering Being a Product Owner is a challenging job

19 Some Principles for Requirements Engineering in Scrum 1: Time boxing Reducing the scope of the work to a sprint of between two to four weeks 2: Face-to-face Communicating the requirements through face-to-face conversation of the Scrum team with the product owner, who is available at all times 3: Deferred Decisions Evolutionarily developing the requirements as late as possible ( deferred decisions applied) 4: Embrace Change Product Backlog does change, Selected Backlog does not change during the sprint the prior permission of. -19-

20 Where can we find RE in Scrum? Product Vision the prior permission of. -20-

21 Product Vision - Example All my music is in my pocket Apple the prior permission of. -21-

22 Agile Methods for the Product Vision Elevator Statement Press Release Product Feature Feature Feature Vision Box [COH06] the prior permission of. -22-

23 Requirements Engineering: Define Scope System Context and Interfaces Stakeholder Analysis the prior permission of. -23-

24 Where can we find RE in Scrum? Requirements Acceptance Business and System Requirements the prior permission of. -24-

25 Magic Backlog READY Available Ordered/ Prioritized Estimated INVEST Understood Source:

26 From Vision to Product Backlog Vision Business Plan Business Drivers Release Product Backlog Minimum Marketable Product Planning Release 1 Release 2 Release 3 Feature Feature Feature User Story User Story User Story User Story User Story User Story User Story the prior permission of. -26-

27 From Vision to Product Backlog Vision Fahrgast Wartungspersonal Operator Business Processes Aufzugsystem Energieversorgung Business Plan Business Drivers Organization Minimum Marketable Product Constraints Feature Feature Feature User Story User Story User Story User Story User Story User Story User Story the prior permission of. -27-

28 Requirements Engineering: Goal Modelling the prior permission of. -28-

29 RE: Activities Elicit Time boxing Specify Face-to-face User Story the prior permission of. -29-

30 Stakeholder/ User-Analysis Interest in Product/ Business Value High Influence to Product Success Low Low High Stakeholder Influence/ Power the prior permission of. -30-

31 User Story Template Story Title I as a X Want Y So that Z X is the person who will benefit from this story being delivered. Y is the content of the story. Z is the benefit the story will deliver. [NORTH] the prior permission of. -31-

32 3 C s for User Stories Card Just enough text to identify the requirement Story Titel I as a X Want Y So that Z Conversation Promise for a conversation between customer and programmer Confirmation Needs acceptance criteria Back side Acceptance Criteria the prior permission of. -32-

33 Quelle: Grooming the Backlog Detailed Requirements Analysis Splitting large items (Re-) Estimation (Re-) Prioritization -33-

34 Level of Detail and Prioritization Evolution of Requirements from Iteration to Iteration Current Iteration In Detail Analyzed Requirements Order/ Priority of Requirements Current Version Later Versions Roughly analyzed Requirements Deferred Decisions Embrace Change Source: WENN DER KUNDE NICHT WEISS, WAS ER WILL: TIPPS FÜR DEN AGILEN UMGANG MIT ANFORDERUNGEN, OBJEKTspektrum September/Oktober2009 the prior permission of. -34-

35 Prioritization By Business Value For the Customer For the company (avoid costs, reduce costs) By Stakeholders By Themes By MuSCoW By Eisenhower (urgent/ important) By risk By Kano Non-Functionl Aspects/ Architecture Dependencies Organizational requirements (e.g. Suppliers) Time Restrictions (Launch Date) the prior permission of. -35-

36 INVEST in Good Stories Bill Wake Quality Check Source:

37 INVEST (Bill Wake) I N V E S T Independent Negotiable Valuable/ Vertical Estimable Small Sized right Testable Who is responsible for the compliance to the criteria? the prior permission of. -37-

38 Story Splitting the prior permission of. -38-

39 The Example also works with Pizza

40 Where can we find RE in Scrum? Implementation Requirements the prior permission of. -40-

41 Team selects Backlog Items for Sprint Backlog Current Iteration Current Version Roughly analyzed Requirements READY State In Detail Analyzed Requirements Time boxing Selected Product Backlog Sprint Backlog: User Story - Task - Task - Task Later Versions Embrace Change Source: WENN DER KUNDE NICHT WEISS, WAS ER WILL: TIPPS FÜR DEN AGILEN UMGANG MIT ANFORDERUNGEN, OBJEKTspektrum September/Oktober2009 the prior permission of. -41-

42 Embrace Change The Content of the Sprint Backlog is stable! No Changes/ no new requirements during the current spring (Iteration) Short Iterations Changes/ new requirements become part of the product backlog and will be prioritized

43 Agile Information Model Levels Artifacts Activities Problem Why? What? Vision Product Backlog Backlog Grooming Planning I Responsible: PO Involved: Team Solution How? Sprint Backlog SW Design Tasks Planning II Responsible: Team Involved: PO the prior permission of. -43-

44 Where can we find RE in Scrum? Requirements Acceptance Release Planning the prior permission of. -44-

45 The Potentially releasable Product Increment Every sprint must deliver a potentially releasable Product Increment Every user story must be Done The product increment must be Done Definition of Done Quality of the product increment Non-functional requirements Unit Tests Refactoring Deliverables oft the product increment, e.g. Documentation Installation Routine Team-Specific the prior permission of. -45-

46 Release-Planning Vision Roadmap Minimum Marketable Product Minimum Marketable Product Release Release Potentially Releasable Product Increment Feature Feature Feature Feature Feature Sprint Sprint Sprint Sprint Sprint Story 7 Story 3 Story 9 Story 4 Story 2 Story 1... Feature Sprint t the prior permission of. -46-

47 Only Done is Done (Ralf Wirdemann) -47- Quelle:

48 Can we find Requirements Engineering in Scrum? 1: Time boxing Focus on a small amount of requirements Higher priority requirements are clearer and have more detail than lower priority requirements 2: Face-to-face Communicating the requirements through face-to-face conversation 3: Deferred Decisions 4: Embrace Change Evolutionarily developing the requirements as late as possible Differentiate between problem and solution space but before a requirement can be taken into a sprint it has to have enough detailed information and acceptance criteria (ready state) Yes, Requirements Engineering is an important part of Scrum. the prior permission of. -48-

49 Questions & Answers Are you ready for questions or are you done? the prior permission of. -49-

50 Thank You! Susanne Muehlbauer Office Munich Keltenring Oberhaching Germany Tel: Susanne.Muehlbauer@HOOD-Group.com the prior permission of. -50-

51 Literature [SUT10] J. Sutherland, K. Schwaber (2010). The Scrum Papers: Nut, Bolts, and Origins of an Agile Framework. [SCH10] K. Schwaber, TraIning Material (2010), Professional Scrum Master, Scrum.org [SUT11] J. Sutherland, K. Schwaber (2011), Scrum Guide [NORTH] Dan North, Web Log [COH06] M. Cohn (2006), Agile Product Management, [WAK03] Bill Wake (2003), Posted on August 17, 2003 [MOE11] T. Mödl, S. Muehlbauer, Eine rationale Romanze, Objektspektrum, to be published 2011] the prior permission of. -51-