This document describes progress tracking in classic project management.
Open Project
1. Log in to the CODING Console and click Use Now to go to CODING page.
2. Click
in the upper-right corner to open the project list page and click a project icon to open the corresponding project.
3. In the menu on the left, click Project Collaboration.
Feature Overview
When the various iteration plans are in progress or have been completed, you can go to a specific iteration in the Iterations module to view the iteration information, issue statistics, status trend, time burndown chart, and action log in Overview and Statistics, to stay on top of your team's progress for the iteration.
The iteration details on the left of Overview and Statistics shows all information of the iteration. The ** Iteration Info** includes the current iteration phase, iteration duration, progress, estimated time, and other information. In Issue Statistics, the total number of issues and number of completed issues in the iteration are shown.
The issue status trend chart in the upper-right corner of Overview and Statistics is a stacked area chart showing the change in issue status versus time, highlighting aggregate trends in issues for the development team. You can switch between issues in the dropdown menu. The different area colors indicate different issue statuses, helping teams manage issue progress and make the necessary adjustments to lagging issues.
If the estimated time and time spent are logged for issues, the Time Burndown Chart in Overview and Statistics will show the remaining workload versus time. See Workload Statistics for details on how to use workload statistics.
The time burndown chart starts a day before the iteration start time and shows the total estimated time of all issues. The horizontal axis indicates time and the vertical axis indicates the remaining time. The gray (ideal) line is the expected progress, the blue (actual) line is the actual progress, and the remaining time is computed every day. If you modify the iteration start time on the Iteration details page, the start time of the time burndown chart will be updated at the same time.
If the actual progress fluctuates, but remains below the expected progress in the mid to late stage, the issues are progressing smoothly and will likely be delivered on time.
If the actual progress remains above the expected progress constantly, the issues are behind schedule and are at risk of delay. You need to adjust the time and iteration plan in time.
