Scrum Software Development model
· Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
· It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).
· The business sets the priorities. Our teams self-manage to determine the best way to deliver the highest priority features.
· Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance for another iteration.
· Scrum projects make progress in a series of “sprints”
· Target duration is one month
· +/- a week or two
· Product is designed, coded, and tested during the sprint
· No changes during the sprint
Scrum Framework
· Roles : Product Owner, Scrum Master, Team
· Meetings: Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting
· Artifacts : Product Backlog, Sprint Backlog, and Burn down Chart
Product Owner
· Define the features of the product
· Decide on release date and content
· Be responsible for the profitability of the product (ROI)
· Prioritize features according to market value
· Adjust features and priority every iteration, as needed
· Accept or reject work results
The Scrum Master
· Represents management to the project
· Removes obstacles
· Ensure that the team is fully functional and productive
· Enable close cooperation across all roles and functions
· Shield the team from external interferences
Scrum Team
· Typically 5-10 people
· Cross-functional
1. QA, Programmers, UI Designers, etc.
· Members should be full-time
2. May be exceptions (e.g., System Admin, etc.)
· Teams are self-organizing
3. What to do if a team self-organizes someone off the team??
4. Ideally, no titles but rarely a possibility
· Membership can change only between sprints
Sprint Planning
· At the beginning of the sprint cycle (every 15–30 days), a “Sprint Planning Meeting” is held. Select what work is to be done
· Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team
· Identify and communicate how much of the work is likely to be done during the current sprint
· Eight hour limit
Daily Scrum
· Daily for 15-minutes
· Stand-up
· Not for problem solving
· Three questions:
1. What did you do yesterday
2. What will you do today?
3. What obstacles are in your way?
· All are invited but team members and scrum master will talk
Sprint Review Meeting
· Team presents what it accomplished during the sprint
· Typically takes the form of a demo of new features or underlying architecture
· 2-hour prep time rule
· Participants are Customers, Management, product Owner, Other engineers
Product Backlog
· The product backlog is a high-level document for the entire project. It contains backlog items: broad descriptions of all required features, wish-list items, etc. prioritized by business value. It is the “What” that will be built.
· Requirements for a system, expressed as a prioritized list of Backlog Items
· Is managed and owned by a Product Owner
· Spreadsheet (typically)
Sprint Backlog
· The sprint backlog is a document containing information about how the team is going to implement the features for the upcoming sprint
· A subset of Product Backlog Items, which define the work for a Sprint
Sprint Burn down Chart
· The sprint burn down chart is a publicly displayed chart showing remaining work in the sprint backlog. Updated every day, it gives a simple view of the sprint progress
· Shows the estimated amount of time to release
· Ideally should burn down to zero to the end of the Sprint
