More About Scrum

Scrum

Scrum excels on urgent projects that are critical to the organization. Scrum excels when requirements are unknown or changing. Scrum helps by helping teams excel

Scrum has been used for…

• FDA-approved, life-critical software for x-rays and MRIs
• Enterprise workflow systems
• Financial payment applications
• Biotech
• Call center systems
• Tunable laser subsystems for fiber optic networks
• Application development environments
• 24x7 with 99.99999% uptime requirements
• Multi-terabyte database applications
• Media-neutral magazine products

Scrum Characteristics

•          One of the agile methodologies
•          Self-organizing teams
•          Product progresses in a series of month-long “sprints”
•          Requirements are captured as items in a list of “product backlog”
•          No specific engineering practices prescribed
•          Wraps existing engineering practices, including Extreme Programming
•          Delivers business functionality in 30 days

Scrum’s Roles

•          The Product Owner
•          The Scrum Master
•          The Team
•          Everyone else is not part of Scrum

The Product Owner

•          Creates initial product vision - overall requirements
•          Manage and prioritize the Product Backlog
•          Decide on release dates and its contents
•          Responsible for the ROI, audience, etc.
•          Interact with stakeholders and customers to define the Product backlog
•          Adjust features and prioritize every sprint, as needed!
•          Accept or reject work results during the Sprint Review

The Scrum Master

•          Protect values and principles
•          Removes impediments
•          Keep the team fully functional and productive
•          Enable cooperation
•          Shield the team from “dark forces”
•          Facilitates integration
•          Does NOT allocate tasks

The Team

•          Typically 7 plus or minus 2
•          Self organizing
•          Self managing
•          Full time allocated
•          Cross functional (Developers , QA ,Doc ,UED, PM etc…)
•          Figure out how to turn Scrum backlog into an increment of functionality.
•          Responsible for the quality
•          Estimates the complexity
•          Committed to developing functionality

Chickens

•          No formal responsibilities
•          No accountabilities
•          Not a team member
•          Someone who is interested in the project

Facilities Strategy

•           Open space.
•           Tables in the middle of the space.
•          Cubbies (Private) around the outside of the space

Scrum Practices

•          The Sprint Planning Meeting
•          The Sprint
•          The Daily Scrum
•          The Sprint Review Meeting
•          The Sprint Retrospective
•          All other practices are not part of Scrum

Scrum’s Artifacts

•          The Product Backlog
•          The Product Burndown Chart
•          The Sprint Goal
•          The Sprint Backlog
•          The Sprint Burndown Chart
•          The Potentially Shippable Product Increment