Description

FIT5057 Project Management
Assignment Two – Team Assignment

FIT5057 Project Management
Assignment Two – Team Assignment

Project name or description

MONTH 20XX

FIT5057 Assignment 2 Writing Guide

This guide aims to support your success in Assignment 2 by providing guidance on each deliverable within the project management plan for your IT portfolio. Remember, this is a starting point – your own exploration of project management concepts and tools will further enhance your submission.

For essential readings, please refer to PMBoK (7th Edition) sections:

Important Reminders:

Understanding FIT5057 Project Management Concepts

● Don’t leave this for the last minute!Early feedback can help identify areas that need more detail, clarification, or critical analysis.
● Prepare for change and update, that’s normal.
● The report is not just an opportunity to showcase your project planning skills but also to reflect on what you’ve learned through the process.
● All templates are provided. YOU should adapt it to your project’s unique needs.
● Conceptual Understanding: Demonstrate a thorough understanding of the core project management principles covered in your coursework. These concepts serve as the foundation for each task within the assignment.
● Justification: Clearly explain your reasoning behind choices, tools, or methods selected. Successful project plans demonstrate not only the ‘what’ but also the ‘why.’
● Professionalism in Writing: Use clear, organised, and error-free language throughout your plan. Present your ideas with the same level of care you would offer a client.
● Visual Clarity: Charts, tables, or diagrams can often communicate complex information or relationships more effectively than text alone.
● Accurate Referencing: Employ your designated referencing style (APA7) correctly and consistently to acknowledge your sources. Refer to Monash Library guidelines.

Contents
DELIVERABLE 1: Project Integration Management [5%]
Task 1.1 Project Charter
DELIVERABLE 2: Project Scope Management [10%]
Task 2.1: Requirements Traceability Matrix
Task 2.2: Project Scope Statement
DELIVERABLE 3: Project Work Breakdown structure and Project Schedule Management [10%]
In-Class Demonstration
Submission for Assessment
DELIVERABLE 4: Project Cost Management [10%]
Task 4.1 One-page Cost Model
Task 4.2 Cost Baseline
Task 4.3 Summary of Assumptions
DELIVERABLE 5: Project Risk Management [15%]
Task 5.1 Risk Register
Task 5.2: Probability & Impact Rationale
Task 5.3: The Matrix & Analysis
DELIVERABLE 6: Project Quality Management [10%]
Task 6.1 Quality Standards/Requirements
Task 6.2 Metrics and Measurement
DELIVERABLE 8: Project Stakeholder and Communication Management [10%]
Task 7.1: Building Your Stakeholder Register
Task 7.2: Engagement Strategy
References
Appendices
DELIVERABLE 1: Project Integration Management (Individual Submission)

Task 1.1 Project Charter

Reflect on the alignment between your project’s objectives and the client’s business strategy. How does your project charter demonstrate an understanding of this alignment?
Use a logical template (like the one provided earlier) to ensure your information is presented clearly.
A strong charter covers all elements in the template, clearly showing how they connect to deliver the project’s value.
Your charter is an important communication tool. Ensure it is well-formatted, easy to navigate
Define success in clear, measurable terms. For example, instead of “improve efficiency,” aim to “reduce processing time by 20% by target date.”

DELIVERABLE 2: Project Scope Management

Task 2.1: Requirements Traceability Matrix
How does your RTM ensure that every requirement directly contributes to the project’s objectives? Mapping Relationships: Develop a table or spreadsheet to illustrate how the project’s requirements link to specific deliverables or design elements. A sample template has been provided.
Go beyond merely listing requirements. Group or categorise requirements to emphasise dependencies or highlight those critical to project success.
Be sure to include both functional requirements (what the system/product must DO) and non-functional requirements (qualities it must HAVE, such as performance, reliability).
Note:you use colour-coding or grouping techniques?

Task 2.2: Project Scope Statement
The template is your starting point, not your final draft!Why does your project matter? What problem does it solve?
Replace vague words like “improved” with something you can measure (e.g., “20% faster”). This is the part to Clearly stating what your project IS and what it IS NOT responsible for.

DELIVERABLE 3: Project Work Breakdown Structure (WBS) and Schedule(Individual & Group Task)
This deliverable has both individual work AND team collaboration. You’ll create a Work Breakdown Structure (WBS) and Gantt chart for your individual project.ALSO, You’ll share these within your team, get feedback, and improve them before adding them in.

Task 3.1: Your Work Breakdown Structure (WBS)
Does the WBS align with the project charter and scope statement?Is Level 3/4 appropriate, providing enough breakdown without being overly granular.
Break each major phase into smaller, manageable tasks.?
How does your WBS reflect a detailed understanding of all tasks required to complete the project?
Task 3.2: WBS Team Time
Your team leader will organise this. Everyone presents their WBS.
Explain why you organised your WBS the way you did.
Does it align with the project’s goals?
Be constructive! Take the feedback and update your WBS in 3.1 for the final submission.
Task 3.3: Gantt Chart
Get the Right Tool: Use ProjectLibre, MS Project, or similar – spreadsheets won’t cut it!
NEED to Match WBS, set estimated durations.What 3 things must be done for you to feel the project is on track? These become your milestones.
● Milestones: At least 3, explainable with SMART criteria (Specific, Measurable, etc.).
● Dependencies: Which tasks have to happen before others? Show these links.
● Your Rationale: Write a short explanation of your choices (durations, dependencies).
Task 3.4: Gantt Chart & Reflection Time
Similar Format: Team meeting, present your chart, get feedback, then iterate.
Team Reflection: This is IMPORTANT. Discuss together:
How did everyone’s plans change based on feedback?
What did you learn about going from theory (in class) to practise?
One team member will present to the tutor, showing a sample Gantt chart.

DELIVERABLE 4: Project Cost Management

Task 4.1: Cost Model

The one-page limit is there for a reason! Focus on clear numbers, not long explanations.
WBS is Your Guide: Use the tasks you broke down in your WBS to structure your cost model.
Clarity: Is the model easy to understand quickly? Well-organised, clearly labelled.
Comprehensiveness: Does it include all key cost categories (labour, materials, contingency, etc.)
Justification: Are cost estimates supported by notes, references, or in-line explanations?

Task 4.2: Cost Baseline
Is it easy to visualise how spending is distributed across the project timeline? Do baseline numbers match the overall cost model? Does the baseline highlight any periods of significant spending?

Task 4.3: Assumptions
Assumptions bridge the gaps between what you know for sure and what you need to estimate to build your plan. Identification: Are the most impactful assumptions clearly listed ?
Justifications: Are they supported, even briefly, by logic or reference sources?It’s about demonstrating you’ve considered the risks and have reasons for your choices. This could be Past project costs, vendor quotes, market research reports.
Relevance: Do the assumptions selected matter most to the project’s cost risks?

DELIVERABLE 5: Project Risk Management
Task 5.1 Risk Register
Show you can spot what might go wrong AND start thinking about how to manage it for project success.
Use the provided template. Spreadsheet templates let you sort the register by priority, owner, etc., for quick insights.
For each risk, is it negative (threat), positive (opportunity)

Task 5.2: Probability & Impact Rationale
What clues make you believe a risk is very likely vs. less likely? Are they based on past experience, data, etc.?
Probability: How likely is this risk to actually happen?
Impact: If it DOES happen, how badly will it derail your project?
Justify why EACH risk is worth considering.Statistics from similar projects, industry reports ex, (“X% of projects face this type of issue…”)
Task 5.3: The Matrix & Analysis
Use the Template: It’ll have the axes labelled for you (probability and impact).
Put each risk on the matrix according to your assessment from Task 5.2.
Management Implications: Explain how the matrix helps with decisions on:
Resource Allocation, Prioritisation: Focus mitigation efforts where the matrix shows the biggest danger.

DELIVERABLE 6: Project Quality Management

Task 6.1 Quality Standards/Requirements
Define what success looks like for your project AND build a plan to make sure you achieve it. Refer back to your scope statement and Focus on those most critical to project success. Avoid vague terms like “user-friendly.” State exactly what success looks like. If you choose a number like 95%, briefly explain why it’s acceptable for your project’s context. Briefly explain why those standards are right for your project, and any assumptions you’re making.

Task 6.2 Metrics and Measurement
How will you KNOW if you’re hitting your standard? Metrics need the right type of measurement. For each standard you set, ask yourself, “What data/feedback would show me this is being met?”
How NOT Just What: Think through the process. A possible example BAD: “Metric: User satisfaction” * GOOD: “Metric: User satisfaction survey at prototype stage and after launch. If scores drop below 80%, conduct interviews to identify improvement areas.”
Justification Matters: Briefly explain why you chose each standard and how it links back to stakeholder needs.

DELIVERABLE 7: Project Stakeholder and Communication Management

Task 7.1: Stakeholder Register
Your register isn’t just a list, it’s a tool for building strong stakeholder relationships.Use the template, Introduce the stakeholder register as a structured method for understanding the diverse players and their potential impact. All the instruce have been provided in the template. Brainstorm anyone impacted by the project or who can influence its success – clients, end-users, internal teams, even the general public if relevant.

Task 7.2: Management & Engagement Plan

Focus on stakeholders with high influence who are OUTSIDE your project team. These are the people you need to proactively manage.For each stakeholder, come up with 2-3 ways to keep them informed, engaged, and address any potential concerns.Engagement isn’t just at the start! How is communication maintained throughout the project?

References
Use APA 7th style for all references.
10 total references is the minimum; emphasise finding the right sources, not just any source, to support their work.
Your references should support and enrich your own ideas, not just be added for show.
Example:
Thorough risk identification is crucial for project success. While traditional brainstorming can be effective, using a structured approach like a risk breakdown structure (RBS) can ensure a more comprehensive analysis (Hillson & Simon, 2018).
Source Citation:

Hillson, D., & Simon, P. (2018). Practical Project Risk Management: The ATOM Methodology (2nd ed.). Management Concepts Press.

Appendices (if applicable)
Include any additional documents, charts, or information relevant to the report.