This can be any type of project, a small project (e.g. the acquisition of a new computer system for a small or medium sized company) or a sub-project of a larger project (e.g. the relocation of staff as part of a construction project).

You need to demonstrate your learning in this unit (Topics 1 to 6), i.e. tools and techniques, use appropriate templates and apply learning to prepare a feasible project plan which the organisation would accept. Use the components of the project plan below as a guide.

Discuss possible projects in your team and plan for the staffing of your project team. Normally only one team member would need access to the organisation, providing the project background and therefore this team member is required as liaison-officer for the project. Other roles could be project manager, budget manager, risk manager etc. Assign roles as you see fit (see deliverables and Team work Plan Hurdle below).

Possible components for the project plan

The components below should only be used as a suggestion. Although it is expected that your project plan would cover the 7 main components listed below, not all aspects will be relevant for every project and additional aspects will be required. For example, under “1. Proposal and feasibility” one team may decide to perform a SWOT analysis whereas another team may choose a macro or PESTLE analysis.  Choose the most suitable structure and content to best present your project plan as appropriate for your project and your clients’ requirements.

1. Proposal and feasibility

Working as a project team needs to be planned carefully. Consider a SWOT analysis based on any available information, assumptions and research. Consider a macro environmental analysis (PESTLE) keeping in mind the relationships with potential third parties or external entities.

Present this section with an analytical review that addresses the following question, supported by your analyses: Is this project feasible and suitable for the organisation?

2. Project organisation

Organisational Structures: Consider a suitable project-based organisational structure. Consider the relevance of interdependencies, economies of scale, organisation size etc. in selecting the suitable mixture.

How many locations are required by the proposed project? Reflect on location specific factors in recruiting personnel. Determine typical outsourcing processes and analyse how the recruiting process can occur.

Present with an analytical summary of the overall corporate requirements in the project organisation with justifications for your choices.

3. Management issues & effectiveness

Teams will likely be culturally diverse, often headed by teams from different geographic locations. Consider the various schools of management thought. In your viewpoint, which of these would apply to this venture? There may be a need for a particular management style. When people or teams come together, conflict is likely. Reflect on possible conflicts that may arise and if conflict occurs. Should there be an overarching corporate policy? Or will there be a need for multiple approaches? Consider performance measures that can apply. Provide an analytical summary with justifications. If outsourcing project components is an option, how is this controlled and managed? What are possible variables for success for this project? Consider types of best practices. Justify your stance in an analytical summary.

Present this section by justifying your viewpoints regarding management styles and conflict management approaches as well as providing recommendations. Present effectiveness by providing relevant summaries, best practices justifying them e.g. supported by tables.

4. Plan (schedule)

Prepare a Statement of Work (SoW); specifications for the project; and work break down structure (level 3 is sufficient). Identify the schedule, milestones and dependencies. Which activities are on the critical path for this project?

Prepare an overview using MS Project.  Present only a short summary schedule in your project plan presentation and submit your full MS Project plan as a separate file in the assignment dropbox.  How you present a summary of your schedule is up to your team, but consider showing summary level activities, key milestones and dates, and critical path activities.

5. Resource and cost plan

What types of estimates are relevant for this project? Prepare relevant pricing estimates. Allocate cost against schedule for the project(s) under 4 above (tip: team member doing resources/costs and schedule will need to work closely together). Consider the risks that would affect costing and schedules. Explain and justify how you propose to monitor performance in the project.

Prepare a short summary or/and use project management software (see above). Include high-level pricing and exemplary resource allocation.

6. Project risk assessment

Select an appropriate risk approach. There can be a combination of strategies or only one. Prepare a risk assessment. Identify and classify the project risks associated with the project. Recommend exemplary methods for risk response, management and mitigation.

Present this section by addressing the above questions with appropriate summaries and chart.

7. Contracts & quality management plan

Describe the procurement strategy. What types of contracts are relevant for the project? How will quality be achieved on this project? Are there relevant quality standards and how will the project meet these standards? Prepare another list with possible strategies for the project to excel, rather than just meeting the requirements.

Prepare a short exemplary quality management plan providing key policies, objectives, assurance, control and audit methods.

Prepare an analytical summary and recommendations based on this to the stakeholders.

Part A deliverables – Project plan presentation

Prepare a consultancy format 30 – 40 minute (max) presentation (roughly 15-20 slides, assuming 2min per slide) of your project plan using PowerPoint, with relevant and concise information based on detailed analysis and research. Only present the outcomes of your work in your presentation. This requires detailed background work and preparation to identify and develop all required outcomes, present this background work as supporting documents to your presentation. In addition to your presentation document include any relevant attachments you wish to include, including e.g. your project schedule, WBS, MS Project file etc. to demonstrate your background work. Also include any supporting documents such as recordings, scripts you wish to include.

All project plan presentations should include a script (as if you were delivering the presentation to a client).  Use the notes section at the bottom of each slide to capture your script.  Your team may also use the “voiceover” feature in Powerpoint to capture your voices delivering the presentation, although this is not required.  If your team decides to use this “voiceover” approach, make sure that you still provide a written script.

Ensure your presentation strongly and convincingly relates to the project in an applied fashion and does not reiterate any theory. Your audience knows the relevant theory.