1. OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, 2013 11:00 am (EST) Seal of the U.S. Department of Veterans Affairs Office of Information and Technology

2. OFFICE OF INFORMATION AND TECHNOLOGY Scrum Team A TEAM Developing Product, not People Doing Work 2 Scrum Team – Self-Organized & Cross-functional “The team figures out how to do its work using the framework” – Scrum Team does not equal Development Team The Team Consists of the following: – Team Members Not just developers, includes all of the following: – Developers, Analyst & SQA Goal: Develop a Quality Product – Product Owner Goal: Team’s POC (liaison) to the outside world (Stakeholders). Makes sure the product being developed is the “right” one. – Scrum Master Goal: Makes sure the team is using scrum correctly, in a positive way and constantly improving in its use of scrum

3. OFFICE OF INFORMATION AND TECHNOLOGY Our Practices 3 Sprint Review – Held the day after* the last day of the sprint – Present the stories that are going to be reviewed – Review the product – Collect Feedback Attendees: Scrum Team, PO, Scrum Master & Stakeholders Sprint Retrospective – Held the day of* the review – Identify & Solve Issues Attendees: Scrum Team, PO & Scrum Master Sprint Planning – Held the day after* the review meeting The first day of the next sprint – PO has prioritized the list of stories – Review stories one by one – Identify and capture the “Acceptance Criteria” – Assign Story Points (Fibonacci Sequence) 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144 Attendees : Scrum Team, PO & Scrum Master Grooming Sessions – Getting the stories ready for prioritization – Make sure the stories are clear, correct and have simple goals Attendees : Analyst, PO & Scrum Master (Developers on an Ad Hoc basis) * These are the target days. If necessary, these activities will be performed on different days. Planning Poker Website

4. OFFICE OF INFORMATION AND TECHNOLOGY Our Practices 4 The Daily Scrum – Allows for a daily INSPECT and ADAPT cycle Inspect: Collect Information Adapt: Do something with that information NOT a Simple Status Update – Story Focused 1.What happened to your set of stories since the last Scrum? 2.What will happen to your set of stories since the last Scrum? 3.What is impeding the Story’s Progress? – 30 Minutes 10 min Standard Round Table – Planning Board Displayed & Updated 5 min Open Forum 15 min User Story Demos Attendees: Scrum Team, PO & Scrum Master

5. OFFICE OF INFORMATION AND TECHNOLOGY The Sprint 5 – Fixed period of time in which Backlog Items are converted into reviewable products the Stakeholders can provide feedback on. – 3 Weeks Long 2 weeks for development of Functionality 1 weeks for SQA Sprint Process 1.Work on user stories simultaneously (Developers & SQA) While the developers are coding, SQA would create manual/automated test cases 2.Deliver the code to SQA (Developers) 3.Execute the unit test (SQA) After the code for last stories in the sprint are delivered 4.Performs integrated test (SQA) 5.Start analysis for the next set of user stories (Developers, Analyst & PO) Analyst may be writing additional stories Goal: A team member completes their highest priority story, have reviewed by the team & them move on to their next story

6. OFFICE OF INFORMATION AND TECHNOLOGY 6 Comments/Feedback/Questions