ONES uses Project one-stop project management evaluation sharing

As a "program girl" who has been developing for more than six years, I have participated in many projects, many products, and used many project management tools.

For example, I have used task management tools such as Redmine, ZenTao, and JIRA before. I use JIRA more. Most of the management tools I have used are focused on a certain convenience. The performance is good, but the centralized project management is combined. In terms of tools, the tools I have used still have many shortcomings. When I was investigating better project management tools as a technical manager in the previous team, I heard my colleagues recommend this ONES, but it may not have been available at that time. Now it is so perfect. I recently visited the official website and found that the user-friendliness of ONES has risen to a level. I have always wanted to promote the team to use ONES, because some communication reasons have not been able to promote it. Project management + task management is a thing. Development students recognize the development tasks. The project manager just wants to monitor the progress and report it. It is still very difficult to re-tune it.

Let me take my ONES account as an example to show everyone. During my trial and trial process, I think the team has some value in using ONES.

Because it was a test, I re-applied for a test account and test project. Our team is more inclined to agile development, so I did not hesitate to build an agile project haha ​​(*^▽^*)

 

A very important point of agile development is to start with requirements as the core. All R&D activities start with requirements to complete each goal. Therefore, a very important part is also requirements management. I think a project management tool can do it well. Demand management is also a reason why I don't use him. In order to facilitate the dismantling of goals, we can specify our phase goals in units of weeks, half months, months, etc. Here, a phase goal is also called an "iteration", and I can define a new one each time. How long is the cycle of the iteration? This is good, because the tightness of the team is different at all times, and the iteration cycle may not be the same every time.

 

When performing requirements management, I think that every requirement can also be understood as a task, and most of the meaningful requirements need to be coded and implemented by developers.

Regarding the new requirement, here is one of my favorites. You can estimate the planned start and end time of the requirement, estimated working hours, etc., as well as upload the requirement document and other attachment information to facilitate tracking every detail of the requirement.

 

In the demand management list interface, I can manually edit and modify the status of a single demand, whether it is in development or testing, each task is clear, and which tasks are not completed at a glance.

 

This is the bug management page, there is not much to say, because most of the bug management is similar, it is nothing more than testers fixing bugs, our developers will mark the fixes, and the test students will verify whether a state is fixed, and gradually improve A process of project quality.

 

Associated code warehouse, this I am associated with one of my test projects

 

Project overview page to view the total progress and status of the project. I find it particularly useful to maintain and modify the status of the project separately. It is possible to maintain those parts of the project that have not been included in the specific development plan but are in the early stage of the project’s business opportunities, demand investigation and other stages, regardless of whether it is the development leader or When the project manager wants to report the work summary, he can directly use the data on this page to explain the problem. The progress and deadlines of each project are too important when reporting upwards.

No matter the progress of the project can be updated, the required progress bar can also be manually edited and updated.

 

The overview of the iterations in the project shows the actual completion of the development of this milestone in our project, whether there is any delay, and how long is expected to be completed, monitoring the health status of the target progress.

The project module can also associate various documents of the project and add document pages.

 

These are the data statistics part of the project. The data statistics about the project are also a place to provide us with good materials for writing weekly and monthly reports, especially clear and comprehensive statistics.

 

BUG statistics:

These are some of the statistical dimensions, which are relatively simple and concise, but they are very practical and can greatly reduce the management cost of the person in charge of R&D:

 

The last point is that I suddenly discovered that project management is very powerful here, that is, we can customize the properties of the project! For example, my APP project needs to involve platform issues, so I can add a "target platform" attribute to give users more room for customization in project management.

 

In general, I have not used a large-scale test account to use it, and have not experienced some permissions or anything, but I think this should be particularly suitable for novice administrators of the team to try, after all, it can save a lot of project progress attention , Summary, and reporting time, the tool layer has been very convenient to help us monitor the health of the project, so that we can put more energy into the key points of the project, so as not to blindly develop, but also to ensure the efficiency and collaboration of the development team. I think this is also a very important value of project management tools.

 

 

 

 

Guess you like

Origin blog.csdn.net/Stephanie_1/article/details/108714779