Using Process Models to Track Agile Sprints

Transcription

1 Using Process Models to Track Agile Sprints Sprint Implementation Requirements Tracker (SIRT) MITRE Susan Main Hall The MITRE Corporation. All rights reserved.

2 Overview 2 Developed new process & tool to track Agile development in support of Department of Veterans Affairs Leverages available business artifacts currently created by the Veterans Health Administration (VHA) Business Architecture Team Provides easy-to-understand graphic to communicate progress/gaps Initial concept proven leveraging real-time VHA effort Tailorable, layered & expandable

3 3 MITRE Role for Project Requirements Elaboration & Development Support Participated in business requirements discussions Wrote enhanced requirement descriptions ( user stories ) for originally planned development Identified additional requirement details and testing objectives Initiated use of automated tracking suite through guidance and support THEN second system added to effort Running as two projects completely parallel Both projects pulled from same business expertise Additional requirements from two other efforts changed priorities for project

4 The Challenge and Goal 4 VA changing development approach from waterfall to Agile Steep learning curve for business and technology teams Agile/new VA process allows for flexible development activities and greater potential for confusion between business and development groups Limited access to automated technology for most business participants on project GOAL Help project implement successfully Support learning agile Not delay development Increase understanding of implementation Create easy to use and understand communication tools to show project development status

5 5 Business Products Created Full User Stories based on Business Requirements Document Large teleconferences (75 participants) with business representatives held twice a week for months To review business models created by VHA Business Architecture Team To review User Stories Business Architecture Team created: Business Process Modeling Notation diagrams for sub-sections of BRD requirements 16 pages of models developed to describe AS-IS and TO-BE processes Another set created for second modernization effort Not every requirement modeled Business logical information model updated to include new data objects

6 Business Products Created (cont d) 6 Requirements Elaboration Documentation Epics & Sub-Epics General User roles & high-level actions User Stories User Story Cards As a <role>, I need to <action> so that <benefit> Acceptance Criteria (SHALL requirements) Requirements Traceability Matrix (RTM) Included previous-non-agile style items Added epic user cards Not all fields completed

7 Development Contractor Products 7 Development details unevenly available to full project team Some lower level User Cards available, but not linked to business user stories/cards Sprint Work Items visible as phrases of functionality linked to Business Requirements Elaboration Document Sub-Epics

8 Unclear Links Between Products 8 Business RQMTs Document (BRD) Business Architecture Team Process Models Requirements Elaboration Documentation RQMTs Traceability Matrix VIP/Agile Sprint Build Release Work Item

9 MITRE Approach to Improving Communication & Tracking Development 9 Link business and development information to get complete flow from original requirement to actual implementation Create textual version and visual version to support both types of understanding Questions current process model answers: What function(s) are scheduled to be implemented in what sprint? What functions are not assigned to a development sprint? What functions are missing business details? What functions are developed, but not released? What functions have been released? Provide reassurance to business folks new to Agile that requirements are being met

10 Process Models to Track Agile Sprints 10 Key Scheduled Coded Exists/Done GAP All tasks defined in the business architecture models and user stories With first sprint: Task 1 has been identified as existing functionality Tasks 3 and 4 are coded, ready for testing and release, but could be held until future releases Task 5 is functionality revealed as missing from original business specification. It needs definition from business and detailed design from development Note, Agile development and/or change requests may cause tasks to divide across sprints (i.e. 3A and 3B)

11 Spreadsheet to Capture Details (matches sample Sprint Implementation Requirements Tracker model) 11 Priority Business User Story Card Status Development Task (SIRT model) Scheduled Sprint Scheduled Release Date As a <user story card A > Existing Task 1 NA As a <user story card B > Scheduled Task 2 Sprint 2 3/17/2017 As a <user story card C > Scheduled Task 2 Sprint 2 3/17/2017 As a <user story card D > Scheduled Task 3A Sprint 3 6/14/2017 As a <user story card E > Coded Task 3B 6/14/ As a <user story card F > Coded Task 4 1/20/2017 As a <user story 6 card G > Scheduled Task 6 Sprint 3 6/14/2017 As a <user story 7 card H > Scheduled Task 7 Sprint 2 3/17/ <NEW> Task 5 Change Request(s) CR1155 New Veteran status added to enrollment options CR1155 New Veteran status added to enrollment options Issue(s) Cannot be released until Task 3B is ready for release Cannot be released until Project X finishes Issue Point of Contact Justine time Toby Dunn

12 Steps for Initial Tracker Recreated the individual business process models, merging them into a single view 2. Linked the business requirements, user story cards, and sprint work item phrases 3. Captured progress based on Scrum of Scrum status reporting

13 Large Example SIRT Model 13

14 14 Metrics Available Velocity Speed with which the requirements are being implemented in comparison to how much time has elapsed Completion Scheduled Answers Is enough getting done fast enough to finish on schedule? Change rate Amount of requirements changed from original business specifications Percentage of whole Type Timing Answers How are Change Requests impacting progress? Status Phase of development in which each requirement exists Type Duration in type Answers Which requirements are stalled/might need clarification?

15 15 Potential Future Metrics Data Business Architecture Team updating their information model Entities Attributes Meta data Multiple data stores Expandability to multiple projects

16 SIRT Summary 16 Newly developed process & tool for Agile Development tracking: Can be upgraded and extended Can be tailored to use many other types of available business artifacts Increases communication and provides visual graphic progress tracking Requires minimal training Takes advantage of A picture is worth 1000 words