A Brief Introduction to the SCRUM Agile Methodology


Published on

The aim of this presentation is to provide a brief overview of the SCRUM Agile Methodology, and to give organizations an idea of how SCRUM may affect the traditional development of requirements and deliverables.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

A Brief Introduction to the SCRUM Agile Methodology

  1. 1. Agile DevelopmentTaha Kass-Hout and John Page Thursday December 20, 2012
  2. 2. Agile Methodology• Agile Methodology – an industry standard – Agile is Empirical (uses real measurements of product and process to continuously reevaluate and adjust) – Waterfall is Defined (requirements & design are all fixed at the start and predict the future path and product)• Agile is not for everything, Waterfall is not for everything (process theory [Tunde])• Successful implementations have been established and are expanding in federal agencies• There are organizational maturation processes and levels achieved when an enterprise integrates Agile Methodology 2
  3. 3. FACT: It is very difficult to predict the future Waterfall asks for detailed understanding when we fundamentally 25% 40% 60% 80% know the least. + 100% 50% 20% 10% - TIME Study z/Analysis Design Coding Testing ReleaseThe top triangle: Represents the idea that our understanding of something is better the closer we are to completing it. At the beginning, we know the least about the object.The bottom triangle: Represents the variability in our estimations of the objects. Early in the project, we understand little about the objects; therefore, our estimates are +- 100%. To mitigate this, Waterfall likesto ‘gate’ the procedure and judge understanding NOT by evaluating the currently developed solution; rather, by evaluating the artifacts produced (documents). 3Agile/Scrum recognizes this reality by building the solution in incremental steps, slicing through the technical layers to provide a working sliver of functionality, and continuously elaborating on the requirements.
  4. 4. Agile Methodology Ecosystem Toolsets Agile (Scrum) Common Framework Development Environment Continuous Automated Transparency Integration Testing Agile Automated Management Deployment Agile Development and Integration 4
  5. 5. SCRUM Process Flow DAILY SCRUM MEETING Design | Code | Integrate |Test 24 HOURS Prioritized by PRODUCT Product Daily Tasks managed Owners by the 2-4 WEEKS teamRequirements Develop/Integrate Continuous Integration IA/DT&E Deploy Preproduction/ Testing Production Continuous Discovery, Reevaluation, Decisions, Status (dashboards) 5
  6. 6. Stakeholder Involvement = Customer Stakeholder / SME Design | Code | Integrate |TestWaterfall (Analysis, Design, Develop, Test)Subject Matter Expert Availability (actual users) DAILY SCRUM MEETINGLong Delivery CyclesHaving to Make ChoicesContinuous Planning/Elaboration 24 HOURSChange is Hard Prioritized by PRODUCT Daily Tasks Product Owners managed by the team 2-4 WEEKS Demonstration and Retrospective Backlog Sprint Sprint Planning Daily Stand-up Sprint Review Refinement Retrospective Meeting Meeting Meeting Meeting Meeting 6
  7. 7. Sample Individual Task Tracking 7
  8. 8. Sprint Planning• Occurs at the beginning of each Sprint.• Participants in the sprint review typically include the Product Owner, Scrum team, management, customers and other project stakeholders.• During the sprint planning meeting the product owner describes the highest priority features to the team.• Two Artifacts – – Sprint Goal – Sprint Backlog
  9. 9. Sprint Review• Occurs at the end of each Sprint.• Participants in the sprint review typically include the Product Owner, Scrum team, management, customers and other project stakeholders.• The project is assessed against the sprint goal determined during the Sprint Planning Meeting.