This simple little function saves 213 hours for our production research team in half a year

Most people's understanding of the production and research students is that they are doing big work every day .

We think our production and research team is ：

• R&d leader ： What is the latest technology architecture this year 、 Is my team suitable ？

• Develop students ：010001, A meal of code is as fierce as a tiger

• Test students ：OK, All tests passed at one time ！

• Product students ： The development direction of our products in the new fiscal year is xxx, Milestones are as follows ：12345

The actual production research team , Except for what we thought we were doing , It is also full of follow-up of the progress of various tasks 、 Synchronization and coordination ：

• R&d leader ： How is the team's iterative development going today ？ The statistics of the project are not accurate ！

• Develop students ： The code has been written , And forgot to update the status , How can I always forget ！

• Test students ： This demand has never been met , I have to call back again 、 And then inform the developer

• The product manager ： The business side came to me again to ask about the progress of the demand , Requirements are still to be developed , It's time for human flesh to follow

These things are trivial , But it is also an essential link for project promotion . Is there any way to let the machine automatically help us solve these problems ？

today , Xiaobian will show you a load reducing artifact , With the help of cloud effect Projex Automated rules for ,

Realize the automatic flow of task status 、 Automatic assignment of requirements 、 Automatic urging

.

Xiao Ming ： Automation rules ？ It sounds very complicated ！

Yun Xiaomei ： Don't worry. , Automated rules are used , It's as simple as giving orders to tmall elves . You just need to use  “ When XXX, Just XXX”  Just make a sentence .

For example, you are in cloud effect Projex Set in ：

When requirements are associated with code branches , The requirement status changes to under development

When the demand is before the planned completion date 3 God , On mail / Nail and notify the person in charge of requirements to complete as soon as possible

When the subtask is completed , The parent task is automatically completed

When girlfriend and mother fall into the water at the same time , I save ...（ Wake up , You don't have a girlfriend ）

As long as the demand / defects / The task meets your definition of “ When XXX” Conditions , The system will automatically help you complete “ Just XXX” The instructions of the .

That may not be specific enough , below , We use the cloud effect Projex Take the production research team as an example ,

Explain the cloud effect Projex The roles of the team

： R&d leader 、 The product manager 、 Development 、 Testing each role is

How to use automated rules , Automate tasks 6400+ Time of , Effective workload reduction

. Hope to give you some inspiration on the scene .

1、 R&d leader ： Daily iteration progress is regularly notified within the group

Iteration progress of the team as a whole and individual members , Know in time

2、 Develop students ： The task status is automatically transferred ,  Don't worry about forgetting to update the status anymore

The thing that must resonate with students is ： Why do you always forget to update the task status ！

• The code is already under development , But I forgot to change from pending development to development

• The code has been released online , But forgot to change the status to released

But this thing , But it is not just the development of students who suffer .

For the R & D leader , Once the development students' task status is not updated in time , The data of iteration statistics will also be very inaccurate

. This is for the person in charge who hopes to improve the R & D efficiency through data driving , It is also a very big thing ： It's really hard to push the team to update the task status in time ！

One side is easy to forget , On the one hand, it is too painful to push the team to the ground . How to solve this problem ？

Just a few simple steps ！ We just need to be in the cloud Projex It's set in ：

（1） When the associated code under the task is submitted , The system automatically changes the task status to being developed .

（2） When the task is associated with a release change , The system automatically changes the task status to released .

The workload of developing students to update task status will be reduced a lot , The measurement data of the team will also be more realistic .

3、 Product students ： Automatically notify business students of the progress of requirements development

Products serve as a bridge between business and technology , The development progress of requirements needs to be synchronized to the business side in a timely manner .

However, the problem faced by product students is , The subtask is already under development , But the parent task always forgets to update to in development . The business students see that the progress of the parent task is delayed in the pending development , Will come to the product to catch up with the progress . How to deal with this situation ？

Again , We just need to set up a simple automation rule , It will be done ！

Automate rule settings ：

When a subtask is under development , The parent task is automatically changed to under development

4、 Test students ： Get timely information about the requirements , Follow up the testing of requirements in time

In many companies , The test association stipulates ： Before requirement testing, the development students need to write an email to the testing team . Make good use of automation rules , This process can also eliminate .

We just need to set up ：

When a certain type of requirement is proposed , Send E-mail / To the specified nail group

  that will do .

In this way, the development students can save redundant mail operations , Test students can also be informed of the test progress in the group . Some tests may not be completely completed by one of the test students , The person in charge of the test can also, according to the notification within the group , Flexible distribution within the team .

Of course , Requirements testing , It's not a matter of testing a classmate , Product students are also very concerned about whether the implementation of requirements conforms to the logic of the original product . therefore , here , Test students only need to add one more rule ：

When a certain type of requirement is proposed , Automatically notify the students of the product to perform function acceptance

, In this way, the product students can check and accept the requirements in time , Avoid the chaos of war before launching .

summary

Above, we have listed some usage scenarios of automation rules for each role of the R & D team . In practice , Each character can develop different scenarios according to their own needs , for example ：

• When creating a new requirement / When defective , Sending notice

• When the task status is to be developed , And only... Is left from the release window 2 days , Sending notice

• When the task status is test returned , Sending notice

• When the entered defect contains a module , Automatic defect marking and classification

• When the defect creator tests the students themselves , Inform the test students to verify by themselves

• When the defect reopens , Sending notice

 ...

This is limited to space , Let's not list more .

We just need to know , In daily project collaboration

Automatic flow of task status 、 Requirements are automatically assigned 、 Automatic urging 、 Platform integration, etc

, We can use the cloud effect Projex Simple automated rule setting in , Easy to finish , No omission ！

To make it easier for people to use automated rules , Cloud effect Projex The product manager of has preset a large number of automation rule templates in the product （ Here's the picture ）, Help you get started quickly .

As shown in the figure below , Cloud effect Projex Our production and research team has eaten crabs more than half a year in advance . In the past six months , Cloud effect Projex Total settings 15 Two rules of Automation , Cumulative execution of automated tasks 6419 Time . Let's assume that the original task requires human resources to follow up 2 minute , Half a year later , It is equivalent to saving... For the cloud effect team 213 Hours . this 213 Hours , To do other, more important things , Is it not fragrant ？

If your team also wants to work less , Click on the link below , Go to cloud effect project collaboration Projex Free experience ！

https://www.aliyun.com/product/yunxiao/project?channel=yy_yccb_yc

Special recommendation

6 month 29 Japan

, We are specially invited to

Alibaba cloud 、 Nanjing University 、Thoughtworks、InfoQ Industry university research community 6 A leader

, Have a big live broadcast ,

Discuss together BizDevOps： Technological change under the tide of digital transformation

, And find a way to break the game .

Watch the live broadcast and you will learn ：

• Challenges and opportunities of digital transformation for product R & D ？

• Why do we need from DevOps trend BizDevOps？

• BizDevOps  What methods and practices does the system contain ？

• How to really apply and implement BizDevOps, Improve the efficiency of enterprise R & D ？

Recommended audience ： Enterprises CIO、CTO、CDO, And practitioners who pay attention to R & D efficiency and digital construction of production and research .

Click on

  Make an appointment now

  Watch the live broadcast , Join in BizDevOps Nail exchange group ：44686237