Introduction To Agile And Scrum

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

5 comments

Comments 1 - 5 of 5 previous next Post a comment

  • robertdempsey Robert Dempsey 2 months ago
    ashutoshmjain: I've taken my Intro to Agile and Scrum talk and begun recording it. You can find the first video here: http://www.youtube.com/watch?v=SjTeNBlb_5Q

    More to come!
  • ashutoshmjain Ashutosh Jain 2 months ago
    Hi Rob - I am doing project management from last 10 yrs for large scale SAP implementations .. when I look back , I tried using the traditional approach so many times and it never worked . users just dont know what they need to begin with.

    I think ... all along I was following Agile to ensure my (and projects') success and never had a name for it .. until few years back when I learned about AGILE at IBM .

    There are still many people /clients who can't unlearn the traditional approach and make the life just too difficult

    Keep up the good work

    Thanks
  • robertdempsey Robert Dempsey 2 months ago
    Thank you both for the feedback.
  • ashutoshmjain Ashutosh Jain 2 months ago
    Great work
  • guest24a348 guest24a348 3 months ago
    very much useful one.thanks
Post a comment
Embed Video
Edit your comment Cancel

12 Favorites & 1 Group

Introduction To Agile And Scrum - Presentation Transcript

  1. Introduction to Agile and Scrum Robert Dempsey Atlantic Dominion Solutions
    • CEO, Atlantic Dominion Solutions
    • Founder, Rails For All
    • Chair, acts_as_conference
    • Co-chair, doterati Membership
    • BA, Computer Science, Rollins
    • MBA Candidate 2009
    • CSM in-training
    Robert Dempsey
  2. FAIL Late / Over Budget
  3. The Old Way
  4. Pros
    • Find bugs early in the process
    • Correct requirements now, less problems later
    • Emphasis on documentation
    • Simple and disciplined
    • Good for stable projects
  5. Cons
    • Stages are not mutually exclusive
    • Developers are (usually) not clairvoyant
    • Documentation overhead
    • Rigid and inflexible
    • Stable project?!
  6. Reality
    • Development phases overlap
    • Software is emergent
    • Ultimate “done” is a moving target
    • Flexibility is required
    • Collaboration is essential
  7. Agile Manifesto
    • Individuals and interactions over processes and tools
    • Working software over comprehensive documentation
    • Customer collaboration over contract negotiation
    • Responding to change over following a plan
  8. Myths
    • Lack of discipline
    • Lack of visibility
    • “That won’t work here.”
  9. Agile Development
    • Changing requirements
    • Incremental development
    • Collaboration between business and developer
    • Self-organizing and self-managing teams
    • Continual adaptation
    • Leadership over management
  10. Agile Methods
    • Extreme Programming (XP)
    • Test Driven Development (TDD)
    • Feature Driven Development (FDD)
    • Behavior Driven Development (BDD)
    • Crystal
    • Dynamic Systems Development Method
    • Scrum
  11. SCRUM
    • An Agile software development framework
    • Iterative development – sprint
    • Requirements – user stories
    • Highest value first
    • Potentially shippable product - increment
    Scrum
  12. User Stories
    • As a (role) I want (something) so that (benefit).
    As a (User) I want (to log in) so that (I can use the site).
  13. Scrum Process Increment 24 hours Product Backlog Sprint Planning 10 days Sprint
  14. Scrum Process Increment Sprint Retrospective Sprint Review
  15. Scrum Roles
    • Pigs
      • Product Owner
      • ScrumMaster
      • Team
        • Developers
        • Designers
        • Testing / QA
  16. Scrum Roles
    • Chickens
      • Users
      • Stakeholders
        • Customers
        • Vendors
      • Managers
      • Other business units
  17. Scrum Artifacts
    • Product backlog
    • Release backlog
    • Sprint backlog
    • Scrum Burndown chart
    Scrum burndown chart
  18. Success Criteria
    • Return on investment (ROI)
    • Productivity
  19. Measuring Success (Metrics)
    • Progress
      • Sprint
      • Release
      • Product
  20. Measuring Success (Metrics)
    • Backlogs
      • Sprint
      • Release
      • Product
    • Customer happiness
    • Done
  21. Results of Agile Adoption
    • Forrester Total Economic Impact Studies
      • 5 companies piloting Agile methods
      • 3 yr, risk-adjusted ROI of 23%-66%
    • Agile Survey, 2/08, 642 respondents
      • 82% increase in productivity
      • 77% increase in quality
      • 78% increase in stakeholder satisfaction
      • 37% decrease in costs
  22. Adopting Scrum
    • Not an overnight process
    • Pilot project
    • Scrum simulation
    • Formal training
  23. Additional Information
    • Scrum Lunch and Learn
    • AgileDevelopmentWithScrum.com
  24. Thank you!
    • Questions?

Robert DempseyRobert Dempsey, 11 months ago

custom

2301 views, 12 favs, 4 embeds more stats

Introduction to Agile development with Scrum

More Info

© All Rights Reserved

Go to text version
  • Total Views 2301
    • 2091 on SlideShare
    • 210 from embeds
  • Comments 5
  • Favorites 12
  • Downloads 0
Most viewed embeds
  • 195 views on http://www.agiledevelopmentwithscrum.com
  • 13 views on http://www.agiledevelopmentwithrob.com
  • 1 views on http://agiledevelopmentwithscrum.com
  • 1 views on http://209.20.73.252

more

All embeds
  • 195 views on http://www.agiledevelopmentwithscrum.com
  • 13 views on http://www.agiledevelopmentwithrob.com
  • 1 views on http://agiledevelopmentwithscrum.com
  • 1 views on http://209.20.73.252

less

Flagged as inappropriate Flag as inappropriate
Flag as innappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel

Categories

Groups / Events