< Previous | Next >

Lesson 1.3: Plan the development effort

In this lesson, you complete a sprint plan that contains stories that are linked to requirements and test cases.

About this task

The team is partly through planning for sprint 2 when Bob proposes a new story from the product backlog. Some stories have been identified, scoped, and added to the iteration plan. The team assesses Bob's request to change the plan.

After completing this lesson, you will learn how to complete these tasks:

  • Track change requests that can affect the sprint plan.
  • Use traceability links to inspect a new requirement to determine the impact on a sprint.
  • Use story points on a sprint plan.
  • Share tasks with the team as child tasks for completing a story.
  • Add test cases that are linked to a story.

Reviewing requests

About this task

Review a new request:

Procedure

  1. In the web client, in the upper-left corner, click the Home menu icon. From the list, under Change and Configuration Management, click JKE Banking (Change Management).
  2. Log out as al.
  3. Log on by typing marco in User ID and marco in Password.
  4. On the project dashboard, under Recently Modified Work Items, open the Allocate Dividends To Multiple Causes story.
  5. In the story, hover over the link under the Quick Information section to view the requirements. Hovering reveals the status, approvals (if any), and links to other requirements. This quick view indicates that Bob elaborated the requirement, so that Marco and the team can proceed with this request.

    Quick information link to requirement.

  6. Optional: Follow the requirement link and explore the artifacts that Bob elaborated to fully understand the scope of the request.

Ranking stories

About this task

Assess the rank of this story compared to the others on the product backlog:

Procedure

  1. In the upper right corner, in Quick Search, click the Search All Work Items icon; then click Current Plans and specify the filter backlog as a search parameter.
  2. In the search results, click Product Backlog [Product Backlog].
  3. In the Product Backlog plan, view as Ranked List, the default view.

    Product Backlog ranked list

Results

The Allocate Dividends To Multiple Causes story is at the top of the list. The team must decide whether they can include it in sprint 2.

Adding a story to the release plan

About this task

Add the story to the release plan:

Procedure

  1. Click the Actions menu to the left of the Allocate Dividends To Multiple Causes story; then click Plan For > Release 1.0.
  2. Click the Actions menu and set Assign To Owner to Deb.
  3. Use the inline editor to set Story Points to 8 points.

    Set story points for Allocate Dividends To Multiple Causes story.

  4. Save the plan, which also saves the story.

Assessing story points

About this task

Assess story points for Sprint 2 in the Release 1.0 Backlog plan:

Procedure

  1. In the Product Backlog plan, click the Links tab.
  2. Under Related Plans, open Release 1.0 Backlog.
  3. On the Planned Items page, ensure that the View As field is set to Iterations, and note the state of the progress bars to the right.
  4. In the Release 1.0 Backlog plan, in the Sprint 2 section, hover over the progress bar and read the Progress report.

    Sprint 2 progress bar

    Note: If the report displays hours, click the progress bar, and hover again to view the report as story points.

Results

The report shows items such as story points on the iteration and project velocity.
Tip: To determine the project velocity, on the dashboard under the Trends tab, use the Story Points by Iteration widget.

Assessing requests

About this task

Assess the new request to determine whether it can be contained in the current sprint:

Procedure

  1. In the Release 1.0 Backlog plan, under Release 1.0, drag Allocate Dividends To Multiple Causes to Sprint 2.
  2. Click the progress bar to view the points. There are 57 story points. The sprint contains too many points.
  3. Drag the Organizations can Apply story and the corresponding task, Implement - Organizations can Apply from Sprint 2 to Release 1.0.
  4. Save the plan.

Creating a test case

About this task

Create a test case for a story:

Procedure

  1. Click the Filters icon and select Execution Items to exclude non-plan work item types, such as tasks and defects.
  2. In the Release 1.0 Backlog plan, click the Actions menu to the left of the Allocate Dividends To Multiple Causes story, and click Add Link > Tested By Test Case.
  3. In the Add Link window, click JKE Banking (Quality Management).
  4. Select Create new to create a test case and click OK.
  5. In the New Test Case window, in the Name field, type Allocate Dividends To Multiple Causes.
  6. From the Owner list, select Tanuj.
  7. From the Test Phase list, select Development Test.
  8. Click OK to create the test case.
  9. Save the plan.
  10. Hover over the Allocate Dividends To Multiple Causes story and verify that Tested By Test Case links to the newly created test case.

    Tested by test case link

Creating a child task

About this task

Create a child development task for a story:

Procedure

  1. In the Release 1.0 Backlog plan, from the View As list, select Work Breakdown.
  2. To the left of the Allocate Dividends To Multiple Causes story, click the Actions icon; then click Create Child Work Item > Task.
  3. Expand the parent task. In the inline editor, type Implement - Allocate Dividends To Multiple Causes, and press Enter.
  4. Click Save.
  5. To the left of Implement - Allocate Dividends To Multiple Causes, click the Actions icon; then click Plan For > Sprint 2.
  6. Click the Actions icon; then click Assign To Owner > Deb.
  7. Save the plan.

    Implement - Allocate Dividends To Multiple Causes work item

Creating child tasks for testers

About this task

Create a child task for a tester to implement the test case:

Procedure

  1. In the Release 1.0 Backlog plan, to the left of the Allocate Dividends To Multiple Causes story, click the Actions icon; then click Create Child Work Item > Task.
  2. Expand the parent task. Using the inline editor, type Detail the test case for Allocate Dividends To Multiple Causes, and press Enter.
  3. Click Save.
  4. To the left of the new task, click the Actions icon; then click Plan For > Sprint 2.
  5. Click the Actions icon; then click Assign To Owner > Tanuj.
  6. Click Save.

Lesson checkpoint

In this lesson, you learned how to complete these tasks:
  • Track change requests that can affect the sprint plan.
  • Use traceability links to inspect a new requirement to determine the impact on a sprint.
  • Use story points on a sprint plan.
  • Share tasks with the team, as child tasks for completing a story.
  • Add test cases that are linked to a story.
< Previous | Next >

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki