Back to lesson
1. When and how are the requirements for task completion normally created?
During project initiation as part of the project charter.
During task planning as part of project scope planning activities during the beginning of a project or beginning of a phase.
During project status meetings when the task is initiated.
2. How should project leaders verify that tasks have been completed?
Tasks are verified as complete during technical reviews such as Design Reviews, Code Reviews, Test Reviews, or other technical reviews.
The team member responsible for the task should notify the team at a status meeting that it is complete.
A Core Team member should review the results of the task with the individual responsible for doing the task.
3. How should the project leader track progress on a high risk task?
The risk is placed in the risk register and the risk status is regularly reported at project meetings.
The project leader uses earned value management to track high risk tasks.
Break the task into “micro-tasks” or “mini-deliverables.” These are planned and tracked by the project leader.
4. Under what conditions should a project leader use a Work Authorization Process?
To get approval from finance to start project work and expend project funds.
To place supplier and vendors on contract for project activities.
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.
Back to the top
© 2017 GoSkills Ltd.
Skills for career advancement