The document provides an overview of how the Scrum process will be used within a software development lifecycle and project. Scrum is an agile methodology that uses iterative increments to optimize predictability and control risk. It has three pillars: transparency, inspection, and adaptation. The key Scrum roles are the Scrum Master, Product Owner, and Development Team. Sprints include planning meetings, daily stand-ups, reviews, and retrospectives. Scrum integrates into the project lifecycle at various stages from requirements to testing. Work items and traceability between artifacts will be managed in Visual Studio Team Services.

1. An overview of the SCRUM process and how it will be
used within the SDLC and the Project Lifecycle
Charlene Woolley

2. What is SCRUM?
Scrum is a form of Agile Methodology which employs an
iterative, incremental approach to optimize
predictability and control risk.
 Three Pillars hold each Scrum process together
 Transparency - Visibility
 Inspection
 Adaptation
Continuous Improvement

3. PIGS
“A chicken and a pig are together
when the chicken says, "Let's
start a restaurant!"
The pig thinks it over and says,
"What would we call this
restaurant?"
The chicken says, "Ham n'
Eggs!"
The pig says, "No thanks, I'd be
committed, but you'd only be
involved!"CHICKENS

4. SCRUM ROLES
 Scrum Master – Ensures process is followed
 Project Manager
 Development Manager /Tech Lead
 Product Owner –Maximizes value of work and manages Product
Backlog in VS (only 1 person)
 Development Manager
 Scrum Team – Completes the work
 Developers
 DBA, Build Lead
 SME’s
 QA Analysts
 User Acceptance Testers – Business Unit

5.  Scrum Master
 Manages the Scrum Process
 Product Owner
 Manages the
Product Backlog
 Sprint Team
 Completes Sprint Work
SCRUM ROLES - PIGS

6. *Everyone Else*
 Project Sponsors
 SME’s
 User Acceptance Testers
 Operations**
SCRUM ROLES - Chickens

7. Scrum within the Project Lifecycle
Concept
• Should we pursue this idea?
• Release Planning
Requirements
& Analysis
• What exactly do you want and what will it take?
• Sprint Planning
Development
• How does it translate to the me?
• The Sprint and Daily Scrum
Testing
• Does it work and meet all the requirements?
• The Sprint and Daily Scrum
Implementation
• Are you ready for it? Let’s start it up!
• Sprint Review and Sprint Retrospective
7

8. SRUM Content
 SCRUM Teams
 Scrum Master, Product Owner, and Scrum Team
 Time Boxes
 Release Planning Meeting
 Sprint Planning Meeting
 Sprint
 Daily Scrum
 Sprint Review
 Sprint Retrospective
 Artifacts – Test Plan, Test Cases, WIT, and Reports in TFS
 Rules – Bind together Time-boxes, Roles, and Artifacts

9. SRUM Content - Timeboxes
• Estimate and Prioritize the Release
• Product Backlog
Release Planning
Meeting
• Estimate and Prioritize the Sprint
• Sprint Backlog
Sprint Planning
Meeting
• The Sprint – “The Heart”
• Work Item Status
The Sprint and the
Daily Scrum
• Estimate and Prioritize the Sprint
• Identify what was “Done”
Sprint Review
• Lessons Learned
• Apply Improvements
Sprint Retrospective

10. Scrum – What is the Sprint?
 An iteration of work from the Product Backlog
scheduled within a certain Time Box (2-4 weeks)
 Sprint Planning Meeting
 Define the What? and the How?
 Sprint Goal
 What + How = Sprint Goal
 Sprint Review
 Define what was Done and what hasn’t been Done
 Review last Sprint’s opportunities for improvement
 Daily Scrum Meeting
 3 Questions – Yesterday, Today, and Roadblocks

11. SCRUM – Sprint Overview

12. SCRUM – Project Lifecycle
• Project Charter
• Project Plan > New Visual Studio Project
Concept
• Requirements Document > User Stories
• QA Test Strategy
Requirements and
Analysis
• Unit Test
• Build Process
Development
• Test Plan / Test Case / Test Results
• Bugs – Rework and Retest
Quality Testing
• Go Live
• Lessons Learned
Implementation

13. SCRUM WIT (Work Item Types)
User Story
Test Cases
Bugs
Tasks
Issues

14. SCRUM – Traceability
User
Story
Test
Plan
Test
Case
Bugs /
Tasks
Requirements

15. SCRUM – QA Tool Demo
Demo
Demo
Demo

16. Questions?