This document describes the classic project management mode in CODING Project Collaboration.
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
Classic project management is a concept relative to Scrum agile project management. It is mainly suited to teams using traditional project management approaches. Traditional project management is based on plans and centered on requirements, resources, and time. Personnel assignments and scheduling take place after requirements are established. In the course of a project, risks are actively tracked and controlled.
Coding Classic Project Management aims to address challenges in traditional project management:
Centralized collaboration: Information on different stages and functions is gathered on a single platform.
Global view: Project progress is summarized in Plans so you can stay on top of multiple iterations.
Project progress: Track progress in Plans and Iterations for transparent processes and control over progress.
Resource management: View the tasks of members at any time in Plans, and assign and coordinate personnel.
Quality control: Track test and bug resolution progress with test and bug management.
The following example uses a virtual mall, Feiniao Market, to describe how a team can collaborate using classic project management.
To gain a foothold in the competitive red ocean of e-commerce, research on potential user groups is essential. Usually, product managers create requirement documentation for products according to pain points in the market or user feedback. You can create a requirement on the Requirement page, and upload attachments or reference external resources (MockingBot Prototype) to easily incorporate ideas at any time. The menu on the right of the requirement details page allows you to adjust the priority, type, and due date of a requirement. You can also specify the estimated time and project progress as needed.
After the requirement research is completed, a requirement pool review meeting is held. After the requirements gathered are discussed and reviewed, the project leader approves the development plan. An iteration can serve as the unit of the development plan.
Using this feature, you can split larger plans (including but not limited to development plans) into specific issues (such as requirements and tasks) assigned to specific assignees. All requirements created by the product manager in the early phase can also be seamlessly integrated into the iteration plan.
Requirements can be broken down into sub-requirements or sub-tasks and associated with bugs and test cases. You can configure other resources required to implement a requirement as a pre-issue, check if a requirement is blocked by another issue, reference other requirements or tasks as resources of this issue, or check which resources have referenced this issue.
In an iteration plan, team members can collaborate by creating issues or accepting issues assigned by others. For example, you can break down a requirement to launch a customer service entry into development and test tasks. After the development has been completed, you can continue breaking down the requirement into a promotion task and hand it over to the operations department for marketing campaigns.
After the various plans have been created and assigned to the specific assignees, in Workspace > My Issues on the team homepage, team members can view the issues to be completed, merge requests initiated by them or merge requests to be inspected, build tasks in continuous integration, and continuous deployment release orders to be confirmed.
For a development task, you can also directly reference merge request records in code repositories. For details, see Reference Resources and Upload Attachments. After associating the items, you can see the code commit record and development status in the development task.
In the menu on the right of the issue details page, you can log time by entering the estimated time and time spent on issues. A complete worklog will be automatically created for retrospectives and efficiency analysis after iterations have been completed.
Before leaving work, members can change the status of the daily task to completed and update the development progress. The iteration progress will update as each issue progresses.
The test phase is crucial to the closed development loop. Self-testing by developers usually resolves most common problems, but it is not enough. Testing helps to identify fundamental logic problems and possible missing items during the development process. CODING's built-in automated testing tools, such as Code Scan and Artifact Scan, help testers quickly create a bug and associate requirements or tasks in an iteration after a bug is found.
You can also log time and update the progress for a bug. In addition to assigning and entering test tasks in an issue, testers can go to Test Management > Test Case Management to write test cases.
In Test Management > Test Plan, you can configure the iteration of the test in Edit.
After all iteration plans have been completed, you can go to an iteration to view the status trend and time burndown chart of the iteration in Overview and Statistics. Managers can stay on top of their team's progress for the plan.
In addition to the default issue statuses, you can customize the workflow of various issues in the issue Workflow in Project Settings > Project Collaboration > Issue Types. See Customize Workflow for details.
Yes
No
Was this page helpful?