ITSS 4370 Lecture Notes - Lecture 34: Scrum (Software Development), Timeboxing, Continuous Delivery
30 Jan 2017
School
Department
Course
Professor
Scrum Practices
• Roles
• Product owner
• Scrum Master
• Development Team
• Activities
• Sprint
• Sprint planning
• Daily scrum
• Sprint execution
• Sprint review
• Sprint retrospective
• Product backlog grooming
• Artifacts
• Product backlogs – requirements prioritizes
• Sprint backlog – what people need
• Potentially shippable product increment
• ...
Sprints
• After first sprint, do a next one
• Each sprint, you can ask for new changes and put it in backlog for next sprint
Benefits of Timeboxing
• Timebox – putting each sprint a certain time
• Establishes a Work in Process (WIP) limit
• Forces Priotization
• Demonstrates progress
• Avoids Unnecessary Perfectionism
• Fixed end date prevents potentially unbounded work to “polish” the
product
• Motivates closure
• Improved Predictability
Sprint planning
• What’s the purpose of this sprint
• Mutual commitment - Don’t change goal when sprint starts
• Product owner commits to not changing the sprint goal or adding features
• Team commits to meeting the spring goal by the end of the sprint
Executing the Sprint
• 24 hours
• Daily scrum at the end of the sprint execution
• Here’s what I did today
Sprint review
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Sprints: after first sprint, do a next one, each sprint, you can ask for new changes and put it in backlog for next sprint. Benefits of timeboxing: timebox putting each sprint a certain time, establishes a work in process (wip) limit, forces priotization, demonstrates progress, avoids unnecessary perfectionism, fixed end date prevents potentially unbounded work to polish the product, motivates closure. Executing the sprint: 24 hours, daily scrum at the end of the sprint execution, here"s what i did today. Sprint review: what could we change, what should we change, show off what you"ve done, new requests for next sprint. Sprint retrospective: what worked and what didn"t, learned. Are scrum and kanban the same: large and complex tasks to be broke down, high value on continuous improvement, optimization, scrum board, visualization. Doing so compromises learning around estimation: kanban, continuous flow, continuous delivery or at the team"s discretion, no existing roles.
