preface

Usually project development will always encounter a lot of problems, many of which are caused by the lack of project management, such as the omission of page requirements, test cases did not cover all the requirements, after testing found that the environment is not matched, project staff information asymmetry, and so on, but these problems, is completely avoidable. Because of this, a project management approach is needed to avoid and solve these problems. Companies are now using more or less online platforms to manage project development, such as Zen Dao, JIRA, etc. Most of these platforms have huge systems and rich functions. Using the whole system requires high learning costs, and most of them are paid platforms. Many of these features may not be needed solely for project iteration management. To simplify the use of tools and focus on project management, I recommend teambition multi-person collaboration platform developed by Ali. One of the features of the platform is that you can choose project templates and add additional applications to suit your needs. For example, you can choose agile development, team task management, to-do list and other project templates. You can also add a variety of customized applications (such as language knowledge base, flow pipeline, IM multi-person conversation, ecloud large file management, etc.).

Without further words, I will briefly describe my simple use of Teambition (teambition has far more functions than this, and I need to explore the functions I need by myself), so that project management can form a closed loop, and all project related information can be checked.

Ahead of multi – figure high energy warning ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 Environment Construction

This stage includes the following contents, based on the trust of everyone, only the key points are selected for demonstration:

  1. Visit teambition website www.teambition.com
  2. Registered account
  3. Create a new business and switch to it
    1. Subsequent projects were created in the enterprise to use more functionality

  1. Go to the app store and add all the apps you can, which you’ll use later in your project

2 New Project

2.1 Creating a Group

Enter the project, first create a group, the group is equivalent to the project team

2.2 New Project

Under this group, create a new project

  • Each iteration creates a new project, so it is best to name the project after the version number

2.3 Selecting a project Template

Here I choose agile development workflow

  • As for the reason, the process in this template is relatively complete, which also meets my expectations
  • After the selection, fill in the project name and select the project group



3 Select the project application

After creating a project, it will enter the project panel by default

3.1 Deleting Unnecessary Applications

Personal choice to delete the following apps :(if you want to use the features of these apps, you can choose to keep them)

  • The iteration
  • Wiki, namely Thoughts
  • The schedule of
  • Working hours

Note: Delete may need to refresh to take effect

3.2 Adding an Application

Personal choice to add the following apps :(if you want to use the features of other apps, you can choose to add)

  • file
  • risk
  • milestone
  • Gantt chart

4 Project Settings

4.1 Test plan Setting

  1. Open the project Settings window

  1. Open the “Test Case Submit Defect Disassociated requirements” button (important)
    1. Associate defects with requirements for later submission

4.2 Label Settings

  1. Open the TAB Settings window

  1. Add new tags (for information tags)
    1. Interface to be confirmed
    2. Interface confirmed
    3. demand
    4. .

5 demand

5.1 Creating A Requirement Category

  1. Sort by page creation requirements
  2. Create a secondary category under the page
    1. Secondary categories can be popovers, components, etc
  3. Put requirements into different categories for easy management

5.2 Creating Requirements

  1. Create requirements under the requirements category
    1. You need to click requirements and manually add requirements classification in the popup of requirements editing
  2. Create sub-requirements under large requirements

5.3 Adding a Requirement State

  1. Open project Settings (see 4 Project Settings)
  2. Select task type Settings

  1. Select workflow Configuration
    1. You can also select field configuration to configure the fields displayed by different tasks

  1. Configuring workflows
    1. To be dealt with: after confirming requirements, development has not started
    2. In development: Front-end development in progress
    3. To be coordinated: to complete front-end development and enter the coordinated coordination stage (transfer from development)
    4. To be accepted: To complete front-end development and enter the acceptance stage (transfer from development to joint adjustment)
    5. Completed: Acceptance is complete

5.4 Association Requirements

  1. Click on requirements to edit
  2. Click Add from Resource to select the requirements to associate from the requirements list
    1. Associated requirements also display associated information



5.5 Modify the requirement status based on the progress

  1. Modify the task status as appropriate
  2. Modify labels as appropriate

6 Test Plan

6.1 Creating a Test Plan

  1. Delete the original sample test plan
  2. Create a new test plan

6.2 Creating use Case groups from requirements

  1. Click requirements to open the requirements edit page
  2. Click Create Use Case group

6.3 Creating use Cases in a Use Case group

  1. Click Create use case

  1. Click on the use case to edit the use case information

6.4 Modify the use case status based on the progress

7 defects

7.1 Submit defects from test cases

  1. Click on the use case to edit the use case information
  2. Click Submit defect
    1. You can go to the defect page to add defect classification before submission

  1. Edit defect information, submit

7.2 Defects relate requirements and test cases

7.3 Test cases are associated with defects

7.4 Requirements relate test cases to defects

Eight tasks

8.1 Display tasks according to categories

8.2 Transfer tasks according to progress

An overview of the nine

9.1 milestone

  1. Add milestones to the overview

  1. Select milestone classification in tasks for viewing, and transfer tasks according to progress (refer to 8 tasks)

9.2 risk

  1. Add risks to the overview

  1. Select risk classification in tasks for viewing, and transfer tasks according to progress (refer to 8 tasks)
  2. There is a separate risk module, in theory the same as the risk classification of the task module

10 gantt chart

  1. Filter task types — requirements, milestones
    1. You need to add a filter — task type

  1. Set the start time for requirements
    1. Milestones only have deadlines

11 files

Archive requirements documents, test cases and other files according to the update time for future query

The last

Ok, the above example is just the tip of the iceberg of teambition based on personal usage habits. Teambition has many more functions than this, including many other applications. Many fields, processes, etc. in each application can be configured. The advantage of separating different functions into applications is that users are free to combine modules according to their own needs. This way, the whole management system looks less complicated, because all the functions are required and none of them are redundant. If you liked this article, or if it was helpful to you, please like, comment or follow it. If you need to reprint, please attach the source of this article, thank you! Juejin. Cn/post / 689152…