Scrum | Refcardz. By Michael James About Scrum Scrum is a simple management framework for incremental product development using one or more cross-functional, selforganizing teams of about seven people each. Scrum teams use fixed length iterations, called Sprints, typically two weeks or 30 days long. They attempt to build a potentially shippable (properly tested) product increment every iteration. An Alternative to Waterfall Scrum’s incremental, iterative approach trades the traditional phases of “waterfall” development for the ability to develop a subset of high-business value features first, incorporating user feedback sooner. Figure 1: Traditional “waterfall” development assumes perfect understanding of requirements at outset. Figure 2: Scrum blends all development activities into every iteration, adapting to discovered realities at fixed intervals. Scrum has been used for a variety of products, but has initially been most popular for software products using object-oriented technologies.
Scrum Roles Scaling. Scrum Resources | Gaming Horror - it's a Game Dev's Li. Glossary of Scrum Terms. The Sprint planning meeting is a negotiation between the team and the product owner about what the team will do during the next sprint. The product owner and all team members agree on a set of sprint goals, which is used to determine which product backlog items to commit from the uncommitted backlog to the sprint.
Often new backlog items are defined during the meeting. This portion of the sprint planning meeting is time-boxed to four hours. Typically the team will then excuse the product owner from the room and break the backlog Items down into tasks. Sprint Retrospective Meeting The sprint retrospective meeting is held at the end of every sprint after the sprint review meeting. The sprint retrospective should be time-boxed to three hours. Kelley Louie (Certified Scrum Practitioner) writes: "The sprint retrospective meeting is an integral part of the inspect and adapt process. Sprint Task In Scrum, a sprint task (or task) is a unit of work generally between four and sixteen hours.
Team. Scrum Resources. Since we’ve jumped on the Scrum bandwagon, I’ve been capturing Scrum related resources as I came across them and sharing them with my management peers and team. Well today I felt it was time I also share them with you… (Paying it forward and all that) As I come across more I’ll try to update this post (as well as link to it off my main page so it’s easy to find in the future ;) I hope these resources help you as much as they have helped me and my team… Books Magazine Articles Other Documents Blog Posts Podcasts Devcasting #14 - How to Make Scrum Really Work. Videos Presentation Materials Scrum in 90 Minutes – The Presentation Software Scrum for Team System Scrum For Team System Quickboard (A personal project) First/Alpha release of my Scrum for Team System Quickboard Project (Think “10 foot SfTS Dashboard”) Light Weight Scrum (Team System) eScrum for Team System My Scrum Stories & Posts (that are not already in the above lists) Humor PS.
Update 8/11/2008: Added: eScrum TFS Template v1.1 Released. Schwapub.pdf (application/pdf Object) Introduction to Scrum and Agile Development - Billy McCafferty. Recently I gave two days worth of talks introducing an organization to agile management and development with Scrum and XP practices. I've made available the presentations and exercises for the betterment of mankind...or at least to get a few more people familiar with agile development. Going Agile - Management.mht: This IE-readable presentation walks through the basics and history of agile development, a close look at Scrum, its usage in actual project work, and selling agile development to clients along with an overview of various contract types.
As you may have guessed, this presentation is management oriented and was effective in convincing the "suits" that agile is a good idea.Management Exercises.doc: This contains a few exercises focusing on organization improvement and reducing waste. Billy McCa.