Scrum
2021-03-01 11:05:07 8 举报AI智能生成
Scrum
作者其他创作
大纲/内容
The Scrum Team
The Product Owner
The Product Owner is responsible for maximizing the value of the product and the work of the
Development Team
Development Team
The Product Owner is the sole person responsible for managing the Product Backlog.
Clearly expressing Product Backlog items;
Ordering the items in the Product Backlog to best achieve goals and missions;
Optimizing the value of the work the Development Team performs;
Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what
the Scrum Team will work on next; and,
Ensuring the Development Team understands items in the Product Backlog to the level
needed.
Ordering the items in the Product Backlog to best achieve goals and missions;
Optimizing the value of the work the Development Team performs;
Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what
the Scrum Team will work on next; and,
Ensuring the Development Team understands items in the Product Backlog to the level
needed.
The Development Team
The Development Team consists of professionals who do the work of delivering a potentially
releasable Increment of “Done” product at the end of each Sprint.
releasable Increment of “Done” product at the end of each Sprint.
The Scrum Master
The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters
do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules
do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules
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
The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for
delivering the product Increment and realizing the Sprint Goal.
delivering the product Increment and realizing the Sprint Goal.
Increment
At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team’s definition of “Done.”
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 detect
undesirable variances
undesirable variances
adaptation
Scrum Events
The Sprint
The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable,
and potentially releasable product Increment is created.
and potentially releasable product Increment is created.
Cancelling a Sprint
Only the Product Owner has the
authority to cancel the Sprint
authority 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 of
Product Backlog.
Product 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 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 the
Sprint Goal?
The Scrum Master ensures that the Development Team has the meeting, but the Development
Team is responsible for conducting the Daily Scrum.
Team is responsible for conducting the Daily Scrum.
Sprint Review
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.
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.
This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.
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
Daily Scrum
Coordination
Overall PBR
Product Backlog Refinement
Sprint Review
Overall Retrospective
ICC is an intelligent customer care system , its an ultimate customer care and billing solution for pay-TV operators.
It is my pleasure to have this opportunity
Scrum:A framework within which people can address complex adaptive problems,while productively and creatively delivering products of the highest possible value.
Lightweight
Simple to understand
Difficult to master
is not a process or a technique for building products;rather, it is a framework within which you can employ various processes and techniques.
0 条评论
下一页
