Requirements flexibel und agil managen am Beispiel Jama Contour
4 likes•2,333 views
The document discusses flexible and agile requirements management (RM) practices in software development, emphasizing the importance of communication and adaptation throughout the development lifecycle. It outlines essential RM structures, methods for managing requirements change, and the integration of agile methodologies such as Scrum. The authors provide insights into user stories, sprint planning, and the systematic approach to RM that supports both flexibility and structure.
Requirements flexibel und agil managen am Beispiel Jama Contour
- 1. Requirements flexibel und agil managen Requirements-Praktiken am Beispiel Contour Handout-Version Dr. Andreas Birk und Gerald Heller, Software.Process.Management 11. April 2013, Webinar der QA Systems Akademie
- 2. Gestatten ... 2 Dr. Andreas Birk Software.Process.Management [email protected] http://www.swpm.de Blog & Resources http://MakingOfSoftware.com Gerald Heller 11. April 2013 Copyright © 2013, Software.Process.Management
- 3. Requirements Management (RM) in the Development Lifecycle 11. April 2013 Copyright © 2013, Software.Process.Management 3 Define Business Goals and Context Develop Requirements Specification Develop Architectural Design Coding and Developer Testing Integration and Testing Requirements Engineering Requirements Management Central Requirements Repository Manage Change Requests and Defect Reports Note: This is a view of software engineering activities in a logical sequence. During the development lifecycle, these activities are performed repeatedly and often concurrently.
- 4. Step One: Develop & Define Requirements 11. April 2013 Copyright © 2013, Software.Process.Management 4 Define Business Goals and Context Develop Requirements Specification Develop Architectural Design Coding and Developer Testing Integration and Testing Develop & Define Requirements For details on essential RM structures and practices, refer to the webinar „Requirements strukturieren und nutzen“ Presentation slides on Slideshare: http://bit.ly/ZoBFA2 Request access to recorded version: seminare(at)qa-systems.de
- 5. Requirements Emerge 11. April 2013 Copyright © 2013, Software.Process.Management 5 Customer Requirements Engineer Software Architect Requirement Communication is key Requirements definition often is „just“ a supportive measure
- 6. Balance Flexibility & Structure in RM Flexibility Communicate about Requirements Evolve & Adapt Requirements Evolve & Adapt Requirements Structures Evolve & Adapt Requirements Practices Structure Information Structures Roles & Responsibilities Agreed-Upon Activities & Steps Requirements States Process Stage Gates 11. April 2013 Copyright © 2013, Software.Process.Management 6
- 7. Requirements State & Stage Gates 11. April 2013 Copyright © 2013, Software.Process.Management 7 Rejected Ready for ReviewDraft create Approved Implemented Validated Suspended Define Business Goals and Context Develop Requirements Specification Develop Architectural Design Coding and Developer Testing Integration and Testing Requirement Approved Requirement Implemented Requirement Validated Requirements-Related Stage Gates: Requirements States & Transitions:
- 8. Flexible RM in Jama Contour Communicate about requirements Review requirements Manage requirements change Agile RM 11. April 2013 Copyright © 2013, Software.Process.Management 8
- 9. Communicate about Requirements 11. April 2013 Copyright © 2013, Software.Process.Management 9
- 10. Review Requirements 11. April 2013 Copyright © 2013, Software.Process.Management 10 Author Reviewer Prepare Review Object Organize Review Invite for Review Read Review Object Write Review Feedback Collect Review Feedback Conduct Review Meeting Update Review Object
- 11. Review Requirements 11. April 2013 Copyright © 2013, Software.Process.Management 11
- 12. Review Requirements 11. April 2013 Copyright © 2013, Software.Process.Management 12
- 13. Review Requirements 11. April 2013 Copyright © 2013, Software.Process.Management 13
- 14. Manage Requirements Change 11. April 2013 Copyright © 2013, Software.Process.Management 14 Requested Closed Approved Ready for Validation Work in Progress Validated Reopened Rejected An Essential Change Process for Requirements
- 15. Manage Requirements Change 11. April 2013 Copyright © 2013, Software.Process.Management 15
- 16. Manage Requirements Change 11. April 2013 Copyright © 2013, Software.Process.Management 16
- 17. Agile RM: The Scrum Process 17 Sprint Planning Meeting Collect Input & Requirements Potentially Shipable Product Increment Sprint 1-4 Weeks Agile Iteration Cycle (Sprint) Acceptance & Delivery Daily Scrum Meeting Sprint Backlog Product Backlog 11. April 2013 Copyright © 2013, Software.Process.Management
- 18. Scaling Agile: Different Requirements Levels 11. April 2013 Copyright © 2013, Software.Process.Management 18 D.Leffingwell:ScaledAgileFramework, http://ScaledAgileFramework.com Portfolio Level Program Level Team Level Epics Features User Stories Tasks
- 19. Cascades of Agile Requirements Backlogs 11. April 2013 Copyright © 2013, Software.Process.Management 19 Incoming Sprint Backlog (User Stories) Portfolio Backlog Release Backlog Product Backlog Sprint Backlog (Tasks) Let‘s illustrate this in Contour ...
- 20. User Story A User Story is a software system requirement formulated as one or two sentences in the everyday or business language of the user A User Story must be small enough to be completed in one cycle A User Story is an informal statement of the requirement as long as the correspondence of acceptance testing procedures is lacking Copyright © 2013, Software.Process.Management 20 Wikipedia July, 2009 cancel reservation As a traveler I want to cancel my reservation cancel reservation (back) □ a premium member can cancel the same day without a fee □ a non-premium member is charged 10% for a cancellation □ an email confirmation is sent out □ the hotel is notified of any cancellation 11. April 2013
- 21. Agile RM - User Story 11. April 2013 Copyright © 2013, Software.Process.Management 21
- 22. Agile RM - Sprints 11. April 2013 Copyright © 2013, Software.Process.Management 22
- 23. Agile RM - Features and User Stories 11. April 2013 Copyright © 2013, Software.Process.Management 23
- 24. Summary: Support for Agile RM 24 Sprint Planning Meeting Collect Input & Requirements Potentially Shipable Product Increment Sprint 1-4 Weeks Agile Iteration Cycle (Sprint) Acceptance & Delivery Daily Scrum Meeting Sprint Backlog Product Backlog 11. April 2013 Copyright © 2013, Software.Process.Management Manage Agile Backlogs Gather Requirements Track Requirements & Document Requirements Fulfilment Process Requirements
- 25. Summary: Flexible Support for RM Work Practices 11. April 2013 Copyright © 2013, Software.Process.Management 25 Define Business Goals and Context Develop Requirements Specification Develop Architectural Design Coding and Developer Testing Integration and Testing Requirement Implemented Requirement Validated Develop & Define Requirements Requirement Approved Communicate about Requirements & Informal Requirements Reviews Direct Requirements Change Explicit Change Management of Requirements Systematic Formal Requirements Reviews
- 26. Important Questions on RM Process Design How can we know what RM approach fits for us? How can we disseminate systematic RM in our organization? How can we move from plan-oriented to agile RM? 11. April 2013 Copyright © 2013, Software.Process.Management 26
- 27. Vielen Dank 27 Dr. Andreas Birk Software.Process.Management [email protected] http://www.swpm.de Blog & Resources http://MakingOfSoftware.com Gerald Heller 11. April 2013 Copyright © 2013, Software.Process.Management