Schedule and Budget Steering Committee Feedback Checklist Answer ALL questions Answers with Yes/No do not need an
Question:
Steering Committee Feedback Checklist
- AnswerALL questions
- Answers with “Yes/No” do not need an explanation
- Answers with “Unsure” need an explanation
- Provide a minimum of 2 feedback items for the last question in each section and include:
- WHAT to improveor WHAT was done wellAND
- WHY the feedback is being provided
- RECOMMENDATIONS for the project team to consider
- Post.
- Once complete, start new thread andcopy-pasteyour feedback (content below the line) and post on the discussion board for the team you are providing a peer review before the due date and time.
- Do not attach file.
- Restrictions& Recommendations
- You cannot repeat/reuse feedback from previous sections in the overall section. The overall section must have standalone and unique feedback
- Your feedback is beproject specific and not generalized. For example, if there is a grammar error, be specific to where it is in the document.
- Spelling, grammar, and professionalism feedback is to be listed in the overall section. The previous sections are to focus on content of the document.
EXAMPLE OF EFFECTIVE FEEDBACK
Feedback Point | WHAT is the feedback? | WHY are you giving this feedback? | Recommendations for improvement |
#1 | Task 2.2 and Task 2.3 have no dependencies | This dependency will greatly impact your schedule – you cannot start construction without a permit. If there is a delay in the permit, then your start date will also be impacted. | Add an FS relationship between the 2 tasks |
#2 | There are no costs listed with Task 3.7 | This task has 40 hours’ worth of work and lots of materials are required to accomplish; that has a significant impact to your budget. | Include labour and cost of materials for task 3.7 (and perhaps equipment if that is part of the task) |
#3 | Task 5.2 is a summary task and has a name associated to it | Remove name, summary tasks should not have a resource assigned to it (standard industry practice) | Remove “Project Manager” from 5.2 |