The sample project initiation document and risk register

This is a paper that is focusing on the sample project initiation document and risk register. The paper also discusses and analyzes the methodologies to run a project.

The sample project initiation document and risk register

Assignment 1 –(30% of module mark);
1.            Sample Project Initiation Document (PID) including budgetary information, timescales, objectives, approach, key staff and stakeholder analysis (approx. 750 words plus diagrams, etc.);
2.            Work breakdown Structure containing at least 20 items in the WBS. The WBS should be in the form of a diagram that includes dependencies, milestones and a hierarchy of tasks. You are free to deliver this as a Gantt chart. (use MS Project to develop this) but it is not required. All diagrams should be embedded into your report as images. In addition include with this table a referenced paragraph explaining how a WBS can be used to help manage the
tasks on a project and give a further paragraph briefly explaining the importance of critical path analysis;

The sample project initiation document and risk register

Assignment 2 – (30% of module mark); A risk register containing at least 10 fully documented risks, including owner, mitigation and contingency actions, pre-and post- action weighting and scores.
1.            In approximately 500 words describing the way in which a risk register forms a crucial part of an overall risk management plan.
Assignment 3 – (40% of module mark);
1.            A short report written directly to the project sponsor (approx. 1,500 words) containing both of the following:
1.            An explanation of the need for effective, structured communication between the project manager and members of their team.  Using theory and suitable case examples, tell your sponsor how best you believe the communication process should be structure on your project, so as to ensure the most efficient and effective possible team working.

2.            An analysis and critique of methodologies that might be to run the project case study, principally comparing Agile, Waterfall and PRINCE2 methodologies. Explain their strengths and weaknesses and give your recommendation to the sponsor as to which methodology you believe would be best to use.  There is no right or wrong answer for this and hence marks will be given on the basis of how well you are explaining and justifying your decision. As with the other assignment elements, reference examples and reference to theory is very important.

2.            Submit copies of your previous two assignments (from weeks 5 and 10) as appendices to this third piece of work so that the marker will be able to see continuity between these earlier assignments and this final one.  Simply paste them in at the end and submit as one large document.  If you did not submit assignment 1 and/or 2 but do wish to submit assignment 3 then simply note at the end that you do not have anything to submit for 1 and 2.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *