129k views
3 votes
Which activity is NOT belong to project plans process?

A. Use requirements to size the project or process iteration
B. Base estimates on product size
C. Update plans as requirements change
D. Use requirement priorities to drive process iteration
E. Have developers review requirements

User Fidi
by
7.8k points

1 Answer

4 votes

Final answer:

The activity that does NOT belong to project plans process is having developers review requirements.

Step-by-step explanation:

The activity that does NOT belong to project plans process is E. Have developers review requirements.

In the project plans process, the focus is on using requirements to size the project, basing estimates on product size, updating plans as requirements change, and using requirement priorities to drive process iteration. Having developers review requirements is a task that falls under a different phase of the project development process.

User Nefreo
by
7.3k points