• Save
Requirements flexibel und agil managen am Beispiel Jama Contour
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Requirements flexibel und agil managen am Beispiel Jama Contour

on

  • 955 views

Requirements flexibel und agil managen am Beispiel Jama Contour ...

Requirements flexibel und agil managen am Beispiel Jama Contour

Ein Webinar von Software.Process.Management für die QA Systems Akademie

Referenten: Dr. Andreas Birk und Gerald Heller

Inhalte:
- Requirements systematisch klären und definieren
- Requirements Change Management & Reviews
- Agiles Requirements-Management

Statistics

Views

Total Views
955
Views on SlideShare
787
Embed Views
168

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 168

http://eblvmsvr 160
http://eblvmsvr.djortho.local 8

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Requirements flexibel und agil managen am Beispiel Jama Contour Presentation Transcript

  • 1. Requirements flexibel und agil managenRequirements-Praktiken am Beispiel ContourHandout-VersionDr. Andreas Birk und Gerald Heller, Software.Process.Management11. April 2013, Webinar der QA Systems Akademie
  • 2. Gestatten ...2Dr. Andreas BirkSoftware.Process.Managementinfo@swpm.dehttp://www.swpm.deBlog & Resourceshttp://MakingOfSoftware.comGerald Heller11. April 2013 Copyright © 2013, Software.Process.Management
  • 3. Requirements Management (RM) inthe Development Lifecycle11. April 2013 Copyright © 2013, Software.Process.Management 3Define BusinessGoals and ContextDevelopRequirementsSpecificationDevelopArchitecturalDesignCoding andDeveloperTestingIntegrationand TestingRequirements EngineeringRequirements ManagementCentralRequirementsRepositoryManage ChangeRequests andDefect ReportsNote: This is a view of software engineering activities in a logicalsequence. During the development lifecycle, these activities areperformed repeatedly and often concurrently.
  • 4. Step One: Develop & Define Requirements11. April 2013 Copyright © 2013, Software.Process.Management 4Define BusinessGoals and ContextDevelopRequirementsSpecificationDevelopArchitecturalDesignCoding andDeveloperTestingIntegrationand TestingDevelop & DefineRequirementsFor 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 Emerge11. April 2013 Copyright © 2013, Software.Process.Management 5Customer RequirementsEngineerSoftwareArchitectRequirementCommunication is keyRequirements definition often is „just“ a supportive measure
  • 6. Balance Flexibility & Structure in RMFlexibilityCommunicate about RequirementsEvolve & Adapt RequirementsEvolve & Adapt Requirements StructuresEvolve & Adapt Requirements PracticesStructureInformation StructuresRoles & ResponsibilitiesAgreed-Upon Activities & StepsRequirements StatesProcess Stage Gates11. April 2013 Copyright © 2013, Software.Process.Management 6
  • 7. Requirements State & Stage Gates11. April 2013 Copyright © 2013, Software.Process.Management 7RejectedReady for ReviewDraftcreateApproved Implemented ValidatedSuspendedDefine BusinessGoals and ContextDevelopRequirementsSpecificationDevelopArchitecturalDesignCoding andDeveloperTestingIntegrationand TestingRequirementApprovedRequirementImplementedRequirementValidatedRequirements-Related Stage Gates:Requirements States & Transitions:
  • 8. Flexible RM in Jama ContourCommunicate aboutrequirementsReview requirementsManage requirements changeAgile RM11. April 2013 Copyright © 2013, Software.Process.Management 8
  • 9. Communicate about Requirements11. April 2013 Copyright © 2013, Software.Process.Management 9
  • 10. Review Requirements11. April 2013 Copyright © 2013, Software.Process.Management 10Author ReviewerPrepare Review ObjectOrganize ReviewInvite for Review Read Review ObjectWrite Review FeedbackCollect Review FeedbackConduct Review MeetingUpdate Review Object
  • 11. Review Requirements11. April 2013 Copyright © 2013, Software.Process.Management 11
  • 12. Review Requirements11. April 2013 Copyright © 2013, Software.Process.Management 12
  • 13. Review Requirements11. April 2013 Copyright © 2013, Software.Process.Management 13
  • 14. Manage Requirements Change11. April 2013 Copyright © 2013, Software.Process.Management 14RequestedClosedApprovedReady for ValidationWork in ProgressValidatedReopenedRejectedAn Essential Change Process for Requirements
  • 15. Manage Requirements Change11. April 2013 Copyright © 2013, Software.Process.Management 15
  • 16. Manage Requirements Change11. April 2013 Copyright © 2013, Software.Process.Management 16
  • 17. Agile RM: The Scrum Process17SprintPlanningMeetingCollect Input &RequirementsPotentiallyShipable ProductIncrementSprint1-4 WeeksAgile IterationCycle (Sprint)Acceptance &DeliveryDaily ScrumMeetingSprintBacklogProductBacklog11. April 2013 Copyright © 2013, Software.Process.Management
  • 18. Scaling Agile: Different Requirements Levels11. April 2013 Copyright © 2013, Software.Process.Management 18D.Leffingwell:ScaledAgileFramework,http://ScaledAgileFramework.comPortfolio LevelProgram LevelTeam LevelEpicsFeaturesUser StoriesTasks
  • 19. Cascades of Agile Requirements Backlogs11. April 2013 Copyright © 2013, Software.Process.Management 19Incoming SprintBacklog(UserStories)PortfolioBacklogReleaseBacklogProductBacklogSprintBacklog(Tasks)Let‘s illustrate this in Contour ...
  • 20. User StoryA User Story is a software system requirement formulated asone or two sentences in the everyday or business language ofthe 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 thecorrespondence of acceptance testing procedures is lackingCopyright © 2013, Software.Process.Management 20Wikipedia July, 2009cancel reservationAs a travelerI want to cancel myreservationcancel reservation (back)□ a premium member can cancel thesame day without a fee□ a non-premium member is charged10% for a cancellation□ an email confirmation is sent out□ the hotel is notified of anycancellation11. April 2013
  • 21. Agile RM - User Story11. April 2013 Copyright © 2013, Software.Process.Management 21
  • 22. Agile RM - Sprints11. April 2013 Copyright © 2013, Software.Process.Management 22
  • 23. Agile RM - Features and User Stories11. April 2013 Copyright © 2013, Software.Process.Management 23
  • 24. Summary: Support for Agile RM24SprintPlanningMeetingCollect Input &RequirementsPotentiallyShipable ProductIncrementSprint1-4 WeeksAgile IterationCycle (Sprint)Acceptance &DeliveryDaily ScrumMeetingSprintBacklogProductBacklog11. April 2013 Copyright © 2013, Software.Process.ManagementManage Agile BacklogsGatherRequirementsTrack Requirements& Document Requirements FulfilmentProcessRequirements
  • 25. Summary: Flexible Support forRM Work Practices11. April 2013 Copyright © 2013, Software.Process.Management 25Define BusinessGoals and ContextDevelopRequirementsSpecificationDevelopArchitecturalDesignCoding andDeveloperTestingIntegrationand TestingRequirementImplementedRequirementValidatedDevelop & DefineRequirements RequirementApprovedCommunicate about Requirements& Informal Requirements ReviewsDirect Requirements Change Explicit Change Management of RequirementsSystematic Formal Requirements Reviews
  • 26. Important Questions on RM Process DesignHow 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 Dank27Dr. Andreas BirkSoftware.Process.Managementinfo@swpm.dehttp://www.swpm.deBlog & Resourceshttp://MakingOfSoftware.comGerald Heller11. April 2013 Copyright © 2013, Software.Process.Management