When and how are the requirements for task completion normally created?

Answer 1

During project initiation as part of the project charter

Answer 2

During project status meetings when the task is initiated

Answer 3

During task planning as part of project scope planning activities during the beginning of a project or beginning of a phase

Answer 4

A Core Team member should review the results of the task with the individual responsible for doing the task

Answer 5

The team member responsible for the task should notify the team at a status meeting that it is complete

Answer 6

Tasks are verified as complete during technical reviews such as Design Reviews, Code Reviews, Test Reviews, or other technical reviews

Answer 7

Break the task into “micro-tasks” or “mini-deliverables.” These are planned and tracked by the project leader

Answer 8

The risk is placed in the risk register and the risk status is regularly reported at project meetings

Answer 9

The project leader uses earned value management to track high-risk tasks

Answer 10

To direct the initiation and track completion of tasks at suppliers, vendors, or extended team members to ensure that they stay in sync with the rest of the project

Answer 11

To get approval from finance to start project work and expend project funds

Answer 12

To place suppliers and vendors on contract for project activities

When and how are the requirements for task completion normally created?

How should project leaders verify that tasks have been completed?

How should the project leader track progress on a high risk task?

Under what conditions should a project leader use a Work Authorization Process?