Helplist over Checklist

In the last week, I discussed the non-functional requirements of a project with a project developer (we have some descriptions about non-functional requirements that are relatively high ), the purpose is to implement these things.

 

This form of discussion reminds me of the review process in cmme. It is very similar, but it is actually different.

++ ++

The review process in CMMS is that when some artifacts of the project are generated, some senior personnel sit down and hold a bunch of items (document or checklist) to discuss whether these artifacts can pass the review, the project enters the next stage or stage.

Although this seminar was also discussed by experienced people sitting with the project staff according to some things (helplist. However, the goal is to help the project team identify possible risks or omissions.

 

That is to say, this seminar takes place at the beginning or in progress of a stage, rather than at the last step of a stage. There is nothing magical about this. It has nothing to do with agility and has been adopted by many teams. However, this is an important aspect that reflects the team culture.

 

Ex-ante help is easier to accept than ex-post audit, and also easier to manage risks. But how many projects have actually been implemented?

 

Finally, helplist over checklist again.