1 / 16

An Introduction to Scrum

An Introduction to Scrum. CSCI 216: Web/Database Capstone. Scrum in 100 words. Scrum is an agile process that allows us to focus on delivering the highest value in the shortest time. Scrum allows us to rapidly and repeatedly inspect actual working software. The client sets the priorities.

chase-dyer
Download Presentation

An Introduction to Scrum

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Introductionto Scrum • CSCI 216: Web/Database Capstone

  2. Scrum in 100 words • Scrum is an agile process that allows us to focus on delivering the highest value in the shortest time. • Scrum allows us to rapidly and repeatedly inspect actual working software. • The client sets the priorities. • Teams self-organize to determine the best way to deliver the highest priority features.

  3. Individuals and interactions Responding to change Working software Customer collaboration Following a plan Comprehensive documentation Contract negotiation Process and tools over over over over The Agile Manifesto Source: www.agilemanifesto.org

  4. Core Values • Commitment • Focus • Openness • Respect • Courage

  5. 24 hours Sprint goal Gift wrap Gift wrap Coupons Coupons Return Cancel Cancel Sprint backlog Sprint 2-4 weeks Return Potentially shippable product increment Scrum Product backlog

  6. The requirements A list of all desired work on the project Ideally expressed as “use cases” – the value to the users or customers of the product Prioritized by the product owner Reprioritized at the start of each sprint Product Backlog Product backlog

  7. A Sample Product Backlog See a more comprehensive example…

  8. Sprints • Scrum projects make progress in a series of “sprints” • Typical duration is 1–4 weeks • Ours will be one week • A constant duration leads to a better rhythm • Product is designed, coded, tested, debugged and documented during the sprint

  9. Product owner • Your client! • Defines the features of the product, which are recorded in the product backlog • Prioritizes features • Adjusts features and priorities every iteration, as needed  • Accepts or reject works results

  10. The ScrumMaster • Responsible for enacting Scrum values • Removes impediments • Ensures that the team is fully functional and productive • Shields the team from unnecessary interference • For our purposes, the Scrum Master will: • Rotate each week • Present the sprint review

  11. The Team • Cross-functional: • Programmers, testers, designers, etc. • Teams are self-organizing • Work is never assigned • Roles may change and overlap

  12. 1 2 3 What did you do yesterday? What will you do today? Is anything in your way? The Daily Scrum • These are not status for the ScrumMaster • They are commitments in front of peers

  13. The Sprint Review • Team presents what it accomplished during the sprint • Typically takes the form of an informal demo • Whole team participates, including the client • Elicit feedback • Welcome criticism

  14. Start / Stop / Continue • Whole team gathers and discusses what they’d like to: Start doing Stop doing Continue doing

  15. Where to go next • www.mountaingoatsoftware.com/scrum • www.scrumalliance.org • www.controlchaos.com • scrumdevelopment@yahoogroups.com

  16. A Scrum reading list • Agile and Iterative Development: A Manager’s Guide by Craig Larman • Agile Estimating and Planning by Mike Cohn • Agile Project Management with Scrum by Ken Schwaber • Agile Retrospectives by Esther Derby and Diana Larsen • Agile Software Development Ecosystems by Jim Highsmith • Agile Software Development with Scrum by Ken Schwaber& Mike Beedle • Scrum and The Enterprise by Ken Schwaber • Succeeding with Agile by Mike Cohn • User Stories Applied for Agile Software Development by Mike Cohn

More Related