Help Center/ CodeArts/ Best Practices/ Using CodeArts to Manage an e-Mall Development Project/ Implementation Procedure/ Step 1: Managing Project Plans
Updated on 2024-11-18 GMT+08:00
View PDF
Share

Step 1: Managing Project Plans

CodeArts Req provides simple and efficient team collaboration services, including multi-project management, agile iteration, and task management.

This sample project uses the Scrum mode for iterative development. Each sprint lasts for two weeks. The Phoenix Mall has been developed in the first three sprints, and sprint 4 is being planned.

According to the project plan, time-limited discount and group buying activity management functions need to be implemented in sprint 4.

Due to business and market changes, store network query is added as an urgent requirement. Therefore, this function will be developed in sprint 4.

This section describes how Sarah (product owner) and Maggie (project manager) manage requirements and sprints, and track the project progress.

Managing Requirements

Project requirements are managed using mind maps, which present work items in the hierarchical structure of "Epic > Feature > Story > Task". These work item types are described in Table 1.

Table 1 Work item types

Type

Description

Epic

An important strategic measure of a company. For example, Phoenix Mall in this sample project is a key strategic measure related to the survival of the company.

Feature

A function valuable to customers. You can use features to fulfil customer requirements. For example, the store network query function in Phoenix Mall is continuously delivered in multiple sprints.

Story

Generated by breaking down a function based on user scenarios. A story can be completed in one sprint.

Task

Generated by breaking down a user story. Preparing environments and test cases can be tasks for a story.
  1. Create a work item for the new requirement.

    The store network query function is a new requirement. Therefore, Sarah needs to add it to the requirement planning view.
    1. Go to the Phoenix Mall project and choose Work.
    2. Click the Plans tab and click Phoenix-MindMap.

      If the Plans tab page is empty, create a mind map.

      1. Click and choose Mind Maps from the drop-down list.

        In the dialog box that is displayed, enter the name Requirement_Planning, and click OK. The mind map details page is displayed.

      2. Click Add Epic. In the displayed dialog box, select Phoenix and click OK.
    1. Create a feature named Store Network.
      1. Click under Epic Phoenix.
      2. Enter the name Store Network and press Enter to save the settings.
      Figure 1 Creating a feature
    2. Use the same method to add story User can query network of all stores to feature Store Network.

  2. Edit the story.

    1. Click story User can query network of all stores and edit it by referring to the following table.
      Table 2 Story configurations

      Configuration Item

      Suggestion

      Description

      Enter As a user, I want to query all stores so that I can select a proper store to obtain the service.

      Priority

      Select High.

      Severity

      Select Critical.
    2. To facilitate understanding, prepare a local file named Store List that includes the following content.
      Table 3 Store list

      Branch Name

      Branch Address

      Branch A

      123 meters to the departure floor, Terminal 1, Airport E

      Branch B

      No. 456, Street G, Area F

      Branch C

      No. 789, Street J, Area H

      Branch D

      West side of Building K, Avenue L, Area K
    3. Return to the story editing page, find Click to select a file, or drag and drop a file, choose Upload from the drop-down list, and upload the list file to the work item as an attachment.
    4. Click Save. The story details are edited.

Managing Sprints

Before a sprint starts, the project manager Maggie organizes a plan meeting to add the new story to the sprint, break down the story into tasks, and assign the tasks to developers.

This section describes how to plan sprint 4.

  1. Create a sprint.

    1. Go to the Phoenix Mall project, choose Work from the navigation pane, and click the Sprints tab.
    2. Click next to Sprint in the upper left corner of the page. In the dialog box that is displayed, configure the sprint by following Table 4. Then click OK.
      Table 4 Sprint information configurations

      Configuration Item

      Suggestion

      Sprint Name

      Enter Sprint4.

      Planned Duration

      Set the duration to 2 weeks.

  2. Plan the sprint.

    1. From the left navigation pane, choose Unplanned Work Items.
    2. Select the following three stories in the list as planned:
      • User can query network of all stores
      • Admin adds group buying activities
      • Admin adds time-limited discounts
    3. Click Edit at the bottom of the page.
    4. Click Add Field.
    5. Choose Sprint from the Field Name drop-down list box, select Sprint4 from the Field Value drop-down list box, and click Save.
    Figure 2 Planning the sprint

  3. Assign the stories.

    1. Choose Sprint4 from the left navigation pane.
    2. Select all stories and set the Assign To field to Chris by following the instructions in Planning a Sprint.

  4. Break down the stories.

    1. Find the story User can query network of all stores. Click the story name.
    2. In the right pane of the page, click the Child Work Items tab.
    3. Click Fast Create Child. Enter the title Frontend display-add store network menu, assign it to Chris, and click OK.
    4. Use the same method to add task Background management-Add store network management and maintenance module.

Tracking Project Status

  • Tracking Task Progress via Daily Stand-ups

    After the sprint starts, the project team communicates the current progress of each work item through daily stand-up meetings and updates the status.

    You can view the status of work items in the sprint in the card mode.

    Go to the Sprints tab page and click to switch to the card mode. This page displays work item cards in each status. You can drag a work item card to update its status.

  • Accepting Iteration Results via Review Meeting

    Before the expected end time of the sprint, the project team holds a review meeting to present work achievements of the current sprint.

    The Sprints tab page provides sprint statistics and charts. The team can easily collect statistics on the progress of the current sprint, including the requirement completion status, sprint burndown chart, and workload.

    Go to the Sprints tab page and click Statistics to display the progress view.

Parent topic: Implementation Procedure