Scrum
2021-03-01 11:05:07 8 举报
AI智能生成
登录查看完整内容
Scrum
作者其他创作
大纲/内容
Scrum
The Scrum Team
The Product Owner
The Product Owner is responsible for maximizing the value of the product and the work of theDevelopment Team
The Product Owner is the sole person responsible for managing the Product Backlog.
The Development Team
The Development Team consists of professionals who do the work of delivering a potentiallyreleasable Increment of “Done” product at the end of each Sprint.
The Scrum Master
The Scrum Master is a servant-leader for the Scrum Team
Facilitating Scrum events as requested or needed
Removing impediments to the Development Team’s progress;
Leading and coaching the organization in its Scrum adoption;
Scrum Artifacts
Product Backlog
Sprint Backlog
Increment
Scrum Theory
transparency
Significant aspects of the process must be visible to those responsible for the outcome
inspection
Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detectundesirable variances
adaptation
Scrum Events
The Sprint
Cancelling a Sprint
Only the Product Owner has theauthority to cancel the Sprint
Sprint Planning
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.
Topic One: What can be done this Sprint?
Topic Two: How will the chosen work get done?
Sprint Goal
The Sprint Goal is an objective set for the Sprint that can be met through the implementation ofProduct Backlog.
Daily Scrum
The Daily Scrum is a 15-minute time-boxed event
The Daily Scrum is held at the same time and place each day to reduce complexity.
What did I do yesterday that helped the Development Team meet the Sprint Goal? What will I do today to help the Development Team meet the Sprint Goal? Do I see any impediment that prevents me or the Development Team from meeting theSprint Goal?
Sprint Review
This is a four-hour time-boxed meeting for one-month Sprints.
Sprint Retrospective
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
Manifesto for Agile Software Development
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
What’s Different in LeSS?
Sprint Planning Part 1
Sprint Planning Part 2
Coordination
Overall PBR
Product Backlog Refinement
Overall Retrospective
It is my pleasure to have this opportunity
Lightweight
Simple to understand
Difficult to master
0 条评论
回复 删除
下一页