Published on

Agile presented by Jeff Bollinger & Cliff Robbins at SCSU on 2/15/2012.

Published in: Technology, Business
1 Like
  • Be the first to comment

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

No notes for slide


  1. 1. Agile
  2. 2. About usJeff• www.jeffbollinger.netCliff RobbinsSoftware Development
  3. 3. Agenda• Waterfall• Agile• Scrum @ W3i
  4. 4. What’s a DevelopmentMethodology? Idea  Software
  5. 5. Methodologies• Waterfall• Agile – Scrum W3i’s Flavor – XP – Kanban
  6. 6. WaterfallRequirements Design Implementation Testing Deployment Maintenance
  7. 7. Waterfall The Real WorldRequirements Change Design Implementation Takes too long Gets skipped Testing Deployment Maintenance
  8. 8. Waterfall Works Well When… • Requirements are stable • Technology is well known and mature • Everything happens as one would expect • We are not taking on anything new or unknown • We have done this many times before
  9. 9. What is Agile?• Iterative Development• Requirements and solutions evolve• Collaboration between self- organizing cross-functional teams
  10. 10. Agile Manifesto Individuals & over Processes & Tools Interactions Comprehensive Working Software over Documentation Customer Contracts and over Collaboration Negotiation Responding to over Following a Plan Change
  11. 11. Agile Principles
  12. 12. Embrace Change Welcome changing requirements, even late in development. Agile processes harness change for the customers competitive advantage.
  13. 13. Frequent Delivery Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  14. 14. Early Delivery Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  15. 15. Collaboration Business people and developers must work together daily throughout the project.
  16. 16. Motivated Individuals Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  17. 17. Conversation The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  18. 18. Working Software Working software is the primary measure of progress.
  19. 19. Sustainable Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  20. 20. Simplicity Simplicity--the art of maximizing the amount of work not done is essential.
  21. 21. Technical Excellence Continuous attention to technical excellence and good design enhances agility.
  22. 22. Self Organizing Teams The best architectures, requirements, and designs emerge from self-organizing teams.
  23. 23. Tune and Adjust At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  24. 24. Why Agile?
  25. 25. The Agile Paradigm Shift Waterfall AgileFixed Requirements Resources Time Vision VALUE Driven PLAN DrivenEstimated Resources Time Features
  26. 26. What is Scrum?• Scrum is popular flavor of agile• Used @ W3i for past 6 years
  27. 27. Scrum Illustration
  28. 28. Scrum User Story Planning Meeting Burndown Chart Epics Retrospective Review Meeting Story Points Estimating Backlog Tasks Velocity
  29. 29. User Stories Example: As a mobile advertiser I would like to be able to export reports via a web service in order to import data into my own system.
  30. 30. Estimating 0,1,2,3,5,8,13
  31. 31. Velocity How fast are you going?
  32. 32. Planning Meeting • Specific amount of time with specific resources.
  33. 33. Daily Scrum – What did you work on yesterday? – What are you going to work on today? – What are your roadblocks, if any?
  34. 34. Burndown
  35. 35. Sprint ReviewsTime to show off
  36. 36. Retrospectives
  37. 37. Questions? We’re Hiring! - Summer Interns - .NET DevelopersJeff Bollinger Cliff RobbinsCTO Software Development