1 / 9

Agile and Scrum: Executive Summary

Agile and Scrum: Executive Summary. Bob Schommer, CSP, PMP, MCTS Senior Project Manager Skyline Technologies, Inc. June 2, 2011 . What does it mean to be agile?. Iterative and incremental development (IID) Working software in each iteration Evolutionary and adaptive Inspect and adapt

lovey
Download Presentation

Agile and Scrum: Executive Summary

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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 organizedteams • Time boxed

  3. 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)

  4. Scrum Terms

  5. Scrum Roles

  6. The Scrum Framework Potential Deployment ScrumPlanning Product Backlog & Team Formation Sprint2-4 Weeks Team Retrospective Sprint Planning2 Parts: Selection and Decomp Sprint Review Daily Scrum

  7. 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

  8. 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

  9. Questions?

More Related