Scrum流程(二)

Scrum流程(二)

Note of <Scrum(development) - Wikipedia.pdf>

Artifacts

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. For example, if the "add spellcheck" and "add table support" features have the same business value, the one with the smallest
development effort will probably have higher priority, because the ROI(Return On Investment) is higher.

The product backlog is the property of the Product Owner. Business value is set by the Product Owner. Development effort is set by the Team.

Sprint backlog
Features are broken down into tasks;as a best practice,tasks are normally estimated between four and sixteen hours of work.

The sprint backlog is the property of the Team. Estimations are set by the Team. Often an accompanying Task Board is used to see and change the state of
the tasks of the current sprint, like "to do","in progress" and "done".

Burn down
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. It also provides quick visualizations for reference. There are also other types of burndown, for example the Release Burndown Chart that shows the amount of work left to complete the target commitment for a Product Release(normally spanning through multiple iterations) and the Alternative Release Burndown Chart, which basically does the same, but clearly shows scope changes to Release Content, by resetting the baseline.

Adaptive project management
The following are some general practices of Scrum:
* "Working more hours" does not necessarily mean "producing more output"
* "A happy team makes a tough task look simple"

Terminology

The following terminology is used in Scrum:
Roles
Product Owner
ScrumMaster
Team
Scrum Team
Product Owner, ScrumMaster and Team

Artifacts
Spring burn down chart
Product backlog
Sprint backlog

Others
Impediment
Anything that prevents a team member from performing work as efficiently as possible.
Sprint
Sashimi
A report that something is "done". The definition of "done" may vary from one Scrum Team to another, but must be consistent within one team.
Abnormal Termination
The Product Owner can cancel a Sprint if necessary. The Product Owner may do so with input from the Team,Scrum Master or Management. For instance,management may wish to cancel a Sprint if external circumstances negate the value of the Sprint Goal. If a Sprint is abnormally terminated, the next step is to conduct a new Sprint planning meeting, where the reason for the termination is reviewed.

Scrum modifications
Scrum-ban
snip...

Product development

Others

See also

References