Skip to main content
System StatusContact Support
VersionOne Community

Getting Started for Lifecycle Administrators


To get your out-of-the-box Lifecycle instance up-and-going fast, only a few things are needed to start planning and tracking your agile project.  This guide gives you the essentials.

It's generally a good idea to focus on minimalism first to help teams get up and going on what's most important. At first, consider disabling features and limiting the number of fields being used. As the teams mature and discover they need more, you can add in more features and/or complexity as the needs arise.

Step 1. Create a Project in the Project Tree

In Lifecycle, the terms "Project" and "Release" are used interchangeably.

The first thing you need to do, is create a new project in the Project Tree. A project is an asset that allows you to capture a backlog of stories, defects, and other workitems and can represent a product or release.

Step 2. Create and Assign a Sprint/Iteration Schedule

Next, you need to create and assign a Sprint/Iteration Schedule to the project. A Sprint Schedule is basically a sprint calendar that aligns a collection of sprints/iterations following the same duration (e.g., two weeks).

Step 3. Add a Team Member to the Project

Now, you can begin adding members to the project. This grants them access to the project and its backlog.

Assigning a member to a project grants them access to the project and allows them to see all of their project data in the Project Navigator and in the Project Tree. 

  1. Go to the Admin menu, select (1) Members, and then click on the (2) Project Assignment tab. 

  2. Expand the project tree at to top of the page, and then (3) drag the member from the bottom grid to the project you want them to access. 

At this point, the member's Admin Privileges role is automatically assigned as the member's project role (drag-and-drop method only), but they do not have explicit access to perform any actions in the project. To grant them access to the project, you need to also assign a Project Role (Step 2 below).

See Member Administration to learn more about managing member accounts.

Step 4. Assign a Project Role to the Member

  1. From the Admin menu, select Projects, and then click on the Member Roles tab (1). 

  2. Expand the project tree, select a project, and then click Manage (2) next to the project name. 

  3. For each member, select a role from the New Project Role/Owner List (3) drop-down list and then select the checkbox if you want the member's name to display in the Owners list.

  4. Click Save.

Step 5. Create or Import Stories for the Project (Optional)

There are several ways to add workitems (stories, defects, etc.) to your project backlog. The most common ways are listed below. For additional options, see Building the Backlog.

  • Import from an Excel Spreadsheet
    If you are managing your workitems in an Excel spreadsheet or have exported them from another system, you can quickly import them into Lifecycle in bulk using the Import Template. We recommend downloading and using this template because it guidance on how to properly format the data to reduce import errors. See Importing Data from Excel.

  • Create Stories on the Backlog Page
    You can also add new stories to the project backlog on the project backlog page. See to Stories/Backlog Items for instructions.

Step 6. Create a Sprint/Iteration (Optional)

  1. In the main menu, select Iteration Planning > Iteration Scheduling.

  2. Select a project in the Project Navigator.

  3. Click on the Iteration Scheduling tab, and then click Add Sprint (or Add Iteration).

  4. Enter the information in the required fields.

    • (Optional) To set the expected amount of estimate to plan for future sprints, set a target velocity for the sprint.

  5. Click Save.

Step 7. Assign Stories to the Sprint  (Optional)

  • With the Project Backlog selected, drag-and-drop Stories from the Backlog into desired Sprint.

  • Stories can be broken down into Tasks and Tests and estimated in desired unit of detail estimation – e.g., Hours; this Detail Estimate provides a To Do value to each Task/Test; reducing the To Do value by a Team Member during the Sprint drives the Sprint Burndown chart to show progress being made against the Sprint Backlog.

Step 8. Track Work and Progress During the Sprint (Optional)

There are several ways to track work in progress:

  • Storyboards, Taskboards, or Testboards
    They are particularly valuable if used in the manner of a physical whiteboard – project onto a wall or display in a large monitor for the Team to use. See Storyboard, Taskboard, or Testboard for more details.

  • TeamRoom
    Drag-and-drop stories, tasks and tests to a status column to show progress; reduce number of To Do values to show progress. See TeamRooms for details.

  • From My Home
    Alternatively, use the My Home > My Work view independently to manage the work to you. See My Work for more information.

  • Was this article helpful?