Agile and Scrum: Executive Summary June 2, 2011 Bob Schommer, CSP, PMP, MCTS Senior Project Manager Skyline Technologies, Inc.

What does it mean to be agile? Iterative and incremental development (IID) –Working software in each iteration Evolutionary and adaptive –Inspect and adapt –Visibility Iterative and adaptive planning –Risk driven –Value driven Self managed and self organized teams Time boxed

Agile Methods Scrum Extreme Programming (XP) Crystal Methods Unified Process (UP) Dynamic Systems Development Method (DSDM) Feature Driven Development (FDD) Lean Development Adaptive Software Development Evolutionary Project Management (Evo)

Scrum Terms ScrumNot an acronym. Sometimes used to refer to the daily stand up meeting SprintAn iteration – typically 2-4 weeks in duration Product Backlog A prioritized list of product features with estimated effort Sprint BacklogDetailed list of tasks that the Scrum Team has committed to deliver during a sprint Scrum BoardUsed by Scrum Teams to track sprint progress – typically a white board with post-it notes Burn DownPublicly displayed chart showing work remaining – either for the sprint or a release

Scrum Roles Product Owner Product vision Prioritizes work to maximize ROI Determines when to deploy Keeps team “fed” with high value work Scrum Team Self organizing Cross functional skills Creates and enforces own ground rules Responsible for commitments ScrumMaster Works for the team Coach, Leader, Facilitator, Change Agent Removes impediments Has no authority

The Scrum Framework Potential Deployment Sprint Review Product Backlog & Team Formation Sprint Planning 2 Parts: Selection and Decomp Daily Scrum Sprint 2-4 Weeks Team Retrospective

The Agile Business Case High Value Features –Faster to market –Adaptable to changes – even late in development –IKIWISI –“Deliver what is needed, not necessarily what is requested” Higher Quality –Test early and often –Improvements to testing as you iterate On Time, On Budget, On Target –Power of time boxing –People remember slipped dates, not slipped features –Schedule and Cost are constants – Scope is the variable

The Agile Business Case Risk Mitigation –Agile is lower risk than waterfall development –Early risk mitigation and discovery Improved Visibility into Projects –Predictability –Meaningful metrics – working software Team Morale –Confidence and satisfaction from early and repeated success –Self organized, self managed and empowered –Face-to-face communications –No “death marches” Continuous Process Improvement –Within the project, team, IT and the company –“Sushi” delivery

Questions?