Lesson 1: Create the product backlog
In this lesson, you log in as the product owner to create a product backlog plan. A product backlog plan contains all of the ideas and work items that might or might not make it into the product over time.
- In the web client, log in to the Change and Configuration Management application. For example, go to https://host-name:9443/ccm/web.
- When the Login window opens, log in as the product owner by typing ursula in both the User ID and Password fields.
- From the My Projects page, under the project name that you created as part of the prerequisites, click Manage Project. In this tutorial, the project name is JKE Banking.
- Plan the start and end dates for the release:
- On the Project Areas page, click Timelines.
.One main development timeline exists in each project, and each timeline can contain only one active iteration, which is indicated by the Active Iteration icon . When you create a project, a default set of plans is also created. For the Scrum process template, the following plans are created: a product backlog, a release backlog, and two sprint backlogs. The product and release backlogs are high-level plans that outline the general features to target in a release. The sprint backlogs are lower-level plans that elaborate on the actual work that needs to be done.Note: The product backlog, which is labeled as Backlog, does not have a schedule. A timeline is not needed for that plan because the purpose of a product backlog is to contain the ideas and work items that might become a part of the product over time.
- To adjust the timeline, click Release 1.0, and then click Edit Properties.
- Select the dates for the release, click OK, and then click Save.
- Open the project dashboard by clicking the Explore Project icon
. Tip: Alternatively, you can open the project dashboard by clicking the down arrow next to the Home icon , and then clicking your project name under the Change and Configuration Management section.
The project dashboard opens:
Take a few minutes to get familiar with the project dashboard. The project dashboard provides an overview of your project status. You can customize the dashboard by adding widgets that query project information, such as defect reports. For more information about customizing the dashboard, see Adding and organizing content on a dashboard.
- Open the product backlog for the project. Tip: As a product owner, you define the features and release schedule for a product and then determine which features provide the most value to customers. A product backlog can help to track all of these ideas and work items.To open the product backlog:
- From the menu, click to see the plans for the project.
- In the Backlog section, in the Name column, click Product Backlog. The plan opens in the plan editor.
- Click the down arrow that is next to the Plan Details
heading to see plan-specific information.
Every project includes a set of plan types, each of which provide a plan editor with specific plan views that support task-oriented work. The plan editor contains five default pages: Planned Items, Links, Snapshots, Dashboard, and Notes. The Planned Items page of the product backlog shows all of the work items that belong to a plan. In this plan type, you can view the work items in the Ranked List or Work Breakdown views.Learn more about how work items are included in a plan:
What makes a work item be displayed in a plan?
A work item belongs to a plan based on two categories: the Planned For field, which represents the iteration, and the Filed Against field, which represents the team that the work item is assigned to.
A plan is a sophisticated query that pulls in work items based on these categories. In each work item, select a category for the Filed Against field and an iteration for the Planned For field to ensure that work items are displayed in the correct plan.
- Add a story to the plan. As a product owner, you add backlog items, which are called stories, directly on the Planned Items tab. A story is a high-level work item in which you can record general details about a product idea or feature. To add a story:
- Click the down arrow that is next to the Add Work Item icon , and then click Story.
- Type a summary for the story.
- Add at least five stories, and then click Save.
- Estimate the stories. After the product owner determines the features to target in a release, the team meets to estimate the amount of work that is needed for each story. Later, stories are broken into smaller tasks, where estimates can be gauged in hours. However, you estimate the complexity of a story in points. To estimate the stories:
- Hover the mouse pointer over the Story Points column
for each work item, click the down arrow, and select a point value.
Note: Your team can decide the meaning of the point values.
- Click Save.
- Hover the mouse pointer over the Story Points column for each work item, click the down arrow, and select a point value.
- Assign the priority and rank to a story:
- Hover the mouse pointer over the Priority column for each work item, click the down arrow, and then select a priority. The work items are automatically sorted by the priority.
- If possible, rank items within a priority group. For
instance, if you have three high-priority work items, you might provide
a rank to give more information about the individual importance of
each item. To change the rank of story, hover the mouse pointer over
the leftmost section in the Actions column of the work item, and then
drag the work item to a new location. The rank changes automatically,
as the next image shows. Note: Changing the ranking of a work item within a plan does not affect its priority.
- Provide more details for each work item:
- Click Summary to open a work item in the Work Item editor.
- To the right of the Description section, click Edit, and then type a description.
- Click Save.
- Add descriptions for all of the work items.