Your SlideShare is downloading. ×
Agile101
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile101

228
views

Published on

High-level Agile overview, intended for in-person presentation

High-level Agile overview, intended for in-person presentation

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
228
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Agenda Copyright © 2013 -2- • Why do we need a methodology? • Agile overview & principles • How it compares to other methods • Agile in action • Resources, tools & techniques
  • 2. Why Do We Need A Methodology? Copyright © 2013 -3- ????? Agile Spiral Extreme Programming (XP) Waterfall Iterative and Incremental Model Driven Development Six Sigma RAD Chaos Model RUP
  • 3. Traditional Project Management aka “Waterfall” Copyright © 2013 -4- Maintenance Many different variations and names for this model; e.g. SDLC Tollgates at each stage Requirements Initiation Analysis Design Implementation Testing
  • 4. What is “Agile”? Copyright © 2013 -5- Key Principles: • Focus on delivering value as quickly as possible • Iterative and incremental delivery • Business-driven prioritization of features • Emphasizes learning and adaptation • Co-located, dedicated teams See Also: Kanban, Lean, Iterative and Incremental
  • 5. Traditional vs. Agile Copyright © 2013 -6- Risk: “Get it Right the First Time” Requirements Defined/Agreed To Up Front Make the Right Design Decision Avoids the Need for Expensive Changes Later Command and control leadership Formalized change control Progress Measured by Artifacts & Milestones (Charter, Requirements Document, etc.) Risk: Get it Done As Quickly As Possible Requirements Never Complete, Always Change Make Design Decisions as Late as Possible Deliver Value as Quickly as Possible Leadership by influence Assumes changes Progress Measured by Total Amount of Working Product Traditional Approach Agile Approach
  • 6. The Triple Constraint Copyright © 2013 -7- Risk/ Quality Scope - Determine Risk/Quality Tolerance - Will Vary By Project
  • 7. Agile in Action Copyright © 2013 -8-
  • 8. Key Terms Copyright © 2013 -9- • Product Owner • Product Backlog • Sprint • Scrum • Scrum-Master • Stand-up • Burn-Down Chart • User Stories • Epic • Velocity
  • 9. More than a Project Methodology Copyright © 2013 - 10- Personal Productivity Business Strategy Agile is a state of mind
  • 10. Tools to Get Started Copyright © 2013 - 11- Post-Its!! Trello Remember the Milk The Agile Manifesto http://agilemanifesto.org Getting Things Done David Allen Read Try Learn Adapt Repeat Remember Agile Coach Toolkit http://agilecoach.net Do
  • 11. Questions? Copyright © 2013 - 12-