Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
student:vivifyscrum:practices [2019/03/05 10:51] – created bernstdh | student:vivifyscrum:practices [2019/03/05 11:42] – bernstdh |
---|
Vivify Scrum uses some non-standard terminology (e.g., it does not use the term "acceptance criteria" or "definition of done" but does have "checklists") and allows some non-standard practices (e.g., tasks can have checklists). To use standard practices and avoid any confusion, you must use the following practices and comply with the following conventions. | Vivify Scrum uses some non-standard terminology (e.g., it does not use the term "acceptance criteria" or "definition of done" but does have "checklists") and allows some non-standard practices (e.g., tasks can have checklists). To use standard practices and avoid any confusion, you must use the following practices and comply with the following conventions. |
| |
- Each sprintable backlog item must be have an "item type" of "Story" (selected from the color-coded drop-down at the top left corner of the card). | - Each sprintable backlog item must be have an "item type" of "Story". |
- Every sprintable backlog item must have a single "Checklist" containing the acceptance criteria. | - Every sprintable backlog item must have a single "Checklist" containing the acceptance criteria. |
- Most sprintable backlog items should have "SUBITEMS". | - Most sprintable backlog items should have "SUBITEMS". |
- Every "SUBITEM" must have an "item type" of "Task" (selected from the drop-down at the top of the card). | - Every "SUBITEM" must have an "item type" of "Task". |
- A "Task" must not have a checklist. (A "Task" should be small so a "Checklist" would not provide any additional useful information.) | - A "Task" must not have a checklist. (A "Task" should be small so a "Checklist" would not provide any additional useful information.) |
- The team must have an "Assignee" for every "Task" (as a "PERFORMER" in the "DETAILS" section). | - The team must have an "Assignee" for every "Task". |
- Stories must not have "Assignees" (since the individual tasks do). | - Stories must not have "Assignees" (since the individual tasks do). |
- The team member that is the "Assignee" on a "Task" must mark it as "Done" when it is completed. | - The team member that is the "Assignee" on a "Task" must mark it as "Done" when it is completed. |
- The team must have a "Reviewer" for every "Story" (as a "PERFORMER" in its "DETAILS" section). | - The team must have a "Reviewer" for every "Story". |
- Tasks must not have "Reviewers" (because they will be reviewed when the story is). | - Tasks must not have "Reviewers" (because they will be reviewed by the reviewer for the story). |
- Epics can (and should) be included in the product backlog. Since there is no specific item type for epics, they must be classified as "Story". | - Epics can (and should) be included in the product backlog. Since there is no specific item type for epics, they must be classified as "Story". |
- Since Vivify Scrum does not allow multiple levels of "drill-down", when an epic is decomposed into sprintable stories it must be removed from the product backlog. | - Since Vivify Scrum does not allow multiple levels of "drill-down", when an epic is decomposed into sprintable stories it must be removed from the product backlog. |
| |
| Help is available on the [[student:vivifyscrum:help | using VivifyScrum page ]]. |