Your SlideShare is downloading. ×
Kevin Graves SCQAA-SF Scrum Presentation
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

Kevin Graves SCQAA-SF Scrum Presentation


Published on

Kevin Graves gives a presentation about Scrum and Agile to the San Fernando Chapter of the Southern California Quality Assurance Association.

Kevin Graves gives a presentation about Scrum and Agile to the San Fernando Chapter of the Southern California Quality Assurance Association.

Published in: Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Agile / Scrum
    3.23.11 - SCQAA-SF – Kevin Graves
  • 2. Agenda
    Why Should You Care?
    What is Agile?
    What is Scrum?
    What Real Scrum Feels Like
    Scrum Challenges
    Scrum Benefits
  • 4. Why should you care?
    Times are Changing
    It Could Help Your Current Project
    It Could help You Land Your Next Job
    It’s Often More Rewarding Work
  • 5. What is agile?
  • 6. IT’s NOT Waterfall where…
    Long Projects have distinct and sequential Phases
    Requirements -> Design -> Programming-> Testing -> Release
    Big up-front effort to collect Requirements
    Multiple Hand-offs between Departments
    Changing Requirements are discouraged
    Working Product is available only at the end of the Project
    Projects are often cancelled with nothing to show
    Software is released and the Customer doesn’t like it
    Team members become demoralized
  • 7. Problems with the waterfall SDLC
    Assumes that creating software is like an assembly line
    Assumes the customer knows exactly what they want up front
    Doesn’t engage the customer during development
    Delivers value to the business too late
    Doesn’t allow the business to respond to changing demands
    Produces artifacts that don’t provide sufficient value
    Encourages the blame game and politics
    Doesn’t leverage the best out of team members
  • 8. What is agile?
  • 9. Agile Methodologies Promote
    Management processes that encourage frequent inspection and adaptation
    Leadership philosophy that encourages teamwork, self-organization, and accountability
    Engineering best practices that allow rapid delivery of high-quality software
  • 10. Agile Values & Principles
    Individuals and interactions are more important than processes and tools
    Working software is more important than comprehensive documentation
    Customer collaboration is better than contract negotiation
    Responding to change is better than following a plan
  • 11. How Scrum relates to Agile
    Scrum (project management)
    Most common Agile implementation
    Easiest to learn
    This is my focus tonight
    Extreme Programming (technical practices)
    Lean (business re-engineering)
  • 12. Key Scrum concepts
    • An empowered, cross-functional, and self-organizing team of 5-7 individuals are picked to design/build/test software together as one team.
    • 13. The Business nominates a single Product Owner which identifies and stack-ranks high level business requirements.
    • 14. The Team works with the Product Owner to breakdown requirements “just in time” into small client-focused “User Stories”, which could each be designed, developed, tested and potentially released within a 4 week “Sprint”.
    • 15. Aggressive collaboration between team members and the Product Owner works out details within the Sprint on the fly.
    • 16. Completed work is demonstrated after each Sprint to get feedback and allow the product to evolve to something the Customer finds highly desirable.
  • Scrum Roles
    Product Owner
    Individual empowered by the company to represent the the priorities of all stakeholders
    Identifies the “what” to be done in a Sprint
    Scrum Master
    Ensures everyone is following the process & playing by the rules
    Helps remove roadblocks that the team can’t
    5-7 empowered individuals with all the skills required to design, program, and test the product
    Determines “how” to get something done
  • 17. Scrum Meetings
    Sprint Planning
    Team plans the next 4 weeks of work together
    Sprint Review
    Team shows what they built and solicits feedback
    Sprint Retrospective
    Team identifies ways to improve at the end of each sprint.
    Daily Scrum
    Daily sync-up of the team to stay focused and productive.
  • 18. Scrum Artifacts
    • Product Backlog
    • 19. Sprint Backlog
    • 20. Burndown Chart
  • What real scrum feels like
    • Work is More Enjoyable
    • 21. You feel a greater sense of Ownership
    • 22. You feel a greater sense of Creativity
    • 23. You feel great being on a highly functional team
    • 24. You get a chance to “win” as a team each 3-4 weeks
    • 25. You Learn more about how to create software
    • 26. You are proud of what you build
  • Scrum Challenges
    Education of team and others
    Buy-in from Team and Management
    Flexible Architecture is difficult
    Long-term Estimating & Planning
    Team empowerment
    Requires strong team members
    Requires Discipline
  • 27. Scrum Benefits
    Better end product
    Earlier delivery of value to customers
    Less waste / more productivity
    Happier Employees
    Less risk of a big failure
    More flexible to changing priorities
  • 28. resources
    Scrum and XP from the Trenches (HenrikKniberg) *
    Succeeding with Agile (Mike Cohen)
    Agile Testing: A Practical Guide for Testers (Janet Gregory)
    User Stories Applied (Mike Cohen)
    Extreme Programming Explained (Kent Beck)
  • 29. Questions?