V1 Review Step-by-Step
At the end of a sprint, all open work should either be closed or moved to
another sprint. All items in the sprint should be closed before closing the
Select Review in the main menu.
Close items to reflect delivery of and acceptance. Zeroing out work
can be easily accomplished by selecting all rows in the sprint and using the
Close multi-select action. Closing a workitem automatically zeroes out any
remaining To Do on that item. Closing a backlog item or defect will also
automatically close any tasks and tests that belong to it.
Transitions are shortcuts that allow you to impact multiple
values with a single action. The transitions show up as
options in the action menus on grids and the Taskboard /
Testboard pages. Use Quick Close to close items and
optionally update status. A default set of status updates
are applied when Transitions are enabled. System
Administrators have the ability to modify the status values
for each type of update, including the ability to make no
change at all. Transitions are automatically enabled when
systems are upgraded, so be sure to review the configured
Status values to ensure they are appropriate for your
Items that were not completed during this sprint can be moved forward
to the next sprint. If the next sprint has not yet been defined, use the Add
Sprint function to create it. Drag an open item up to the next sprint to
move the item, or use the multi-select checkbox and the Move option to move
multiple items at once.
Move the story to the backlog by selecting edit and updating the
sprint to blank.
Some teams may choose to split a partially completed backlog item.
Select Split for any partially completed backlog item to remove remaining
work effort from the current sprint and move it to the following sprint.
Splitting the item will create two separate backlog items. Be sure to
allocate the estimate for the backlog item appropriately.
When all items have been closed, split or moved forward so there are
no Open items remaining in the sprint, an option to Close the current sprint
will appear for those with proper access rights (i.e. Project Leads and
Administrators). If the next sprint already exists when the current one is
closed, the next sprint will automatically be activated. If the next sprint
has not yet been created, an option to create it will be displayed for those
with access rights. If this is the last sprint in the release or project,
simply close the sprint to complete it.
A retrospective is a meeting held by a project team at the end of sprint,
release, or project to inspect and adapt their processes and teamwork. Within
VersionOne, retrospectives can be used to capture the important details of a
retrospective meeting. They can also be related to backlog items or issues that
are identified or discussed in the meeting.
Select the Retrospectives tab under Review.
Create new retrospectives by clicking on the Add link above the grid
at the top of the page. All that is required to create a retrospective is a
title. Additional attributes can be defined as necessary.
Edit retrospectives by clicking on the Edit link or through an
editable column in the grid. Additionally, the Conduct link opens a focused
page that allows a user to quickly capture the details of the meeting,
including any to backlog items or issues that are identified.
View full details of any retrospective by clicking on the
retrospective title to bring up its Details page. The Details page can also
be used to make edits, add discussion notes and links, and to establish and
edit relationships between the retrospective and other assets in the system.