Managing a Project Team (UCT Module 7) Assessment Answers: UCT Project Management Foundations Notes (PMF)

Managing a project team is one of the most practical, highest-impact topics in project management assessments, especially at foundation level. This study guide provides model assessment answers aligned with UCT Project Management Foundations (UCT Module 7) and focuses on how to plan, organise, lead, and control people during a project. It also covers how to respond to common assessment prompts: conflicts, performance issues, stakeholder communication, motivation, team agreements, and measuring team effectiveness.

The guide is written to be usable as exam-ready notes: it includes explanations, frameworks, step-by-step processes, and worked example answers you can adapt directly to typical questions in UCT-style assessments for project management.

Understanding the Role of the Project Manager and the Team in Project Delivery (UCT Module 7)

A project team is not just a group of people assigned tasks; it is a structured system for producing outcomes under constraints (time, budget, scope, quality, and risk). In UCT foundation assessments (often linked to modules such as Project Management Foundations, sometimes assessed through short structured answers and case-based scenarios), marks are usually awarded for showing that you understand the difference between management and leadership, and how team dynamics affect project performance.

The Project Manager’s Core Responsibilities (People-Focused)

In a typical UCT Module 7 question, you may be asked to explain how a project manager manages a team. A high-mark answer usually includes the following responsibilities:

Plan team requirements
- Determine the roles needed (e.g., project coordinator, analyst, designer, engineer, QA).
- Estimate capability needs (skills, experience, availability).
- Consider internal vs external resourcing and procurement time.
Build the team
- Recruit or assign team members.
- Clarify reporting lines and responsibilities.
- Ensure the team has access to tools, information, and authority.
Set direction and expectations
- Translate project scope into deliverables and tasks.
- Define success criteria: what “done” means.
- Establish team working agreements (attendance, communication channels, escalation routes).
Lead and motivate
- Use leadership styles appropriate to maturity, risk, and team culture.
- Recognise progress, remove barriers, and maintain morale.
- Coach where needed and correct performance issues.
Manage performance
- Track output and quality against plan.
- Monitor workload and capacity.
- Address underperformance through feedback and improvement plans.
Control and coordinate
- Run meetings effectively (stand-ups, status meetings, retrospectives).
- Use change control processes for scope and responsibilities.
- Manage conflicts and maintain focus on objectives.
Manage stakeholder communication
- Keep stakeholders informed in a structured, planned way.
- Escalate issues early and transparently.

An exam answer becomes stronger when you explain that managing people is part of delivery control: even the best schedule fails if the team lacks clarity, motivation, or authority.

Leadership vs Management: How It Shows in Assessment Answers

UCT foundation marking often rewards students who distinguish management functions (planning, organising, controlling) from leadership behaviors (influencing, aligning, motivating). A concise explanation you can use in exam answers:

Management ensures the team has clear objectives, plans, resources, and monitoring.
Leadership ensures the team is engaged, aligned to purpose, and supported to deliver despite uncertainty.

A simple sentence that scores well in short answers is:

“The project manager combines management (planning, assigning, monitoring) with leadership (influencing, motivating, resolving issues) to ensure the team delivers the project outcomes.”

Team Roles, Accountability, and Clarity

Many assessment questions include ambiguity like “manage the team” or “improve teamwork.” A high-mark response clarifies what “manage” means by referencing roles and accountability. Use concepts such as:

RACI (Responsible, Accountable, Consulted, Informed)
Clear deliverable ownership
Escalation paths
Authority to act (not just assigned tasks)

Example: Clarifying Accountability Using RACI (Case Scenario)

Scenario: A UCT IT project is delivering a new student registration dashboard. After two weeks, delays occur because both Developers and QA claim the requirements are unclear.

A strong assessment answer would include:

Assign Accountable for requirements: e.g., Business Analyst (Accountable).
Set Responsible for development tasks: Developers.
Set Responsible for test planning/execution: QA Lead.
Set Consulted: UX designer, Data team.
Set Informed: Project Sponsor, Steering Committee.

This prevents “task ping-pong,” which is a common real-world team problem and commonly tested in case-based marking.

Team Performance Drivers: What Actually Predicts Success

Marks are often gained by explaining drivers of performance rather than listing generic statements. Key drivers include:

Clarity: everyone understands goals and responsibilities.
Capacity fit: workload matches available time and capability.
Communication quality: information reaches the right people early.
Trust and psychological safety: team members raise issues without fear.
Support and resourcing: barriers are removed quickly.
Feedback loops: early detection of issues reduces rework.

A useful exam phrasing is:

“Team performance is influenced by clarity of roles, realistic capacity planning, effective communication routines, and timely issue resolution.”

South African Context Example (UCT Foundations-Friendly)

UCT projects often operate in environments with stakeholder diversity (academic departments, administrative divisions, IT, procurement, finance). In South Africa, constraints such as procurement lead times, bandwidth limits, and schedule conflicts with academic calendars can affect team output.

Assessment-style example you can adapt:

A team member is unavailable due to exam marking periods.
A procurement process delays software licenses.
Meetings must be scheduled around teaching timetables.

In your answer, show how the project manager adjusts by:

re-planning tasks,
reallocating responsibilities temporarily,
escalating resource constraints,
updating the team agreement and communication schedule.

Common Exam Traps (and How to Avoid Losing Marks)

To write “assessment answers” rather than essay fluff, avoid:

Vague statements: “motivate the team” without describing methods.
No structure: list points without linking them to outcomes.
Ignoring conflict: conflict is commonly tested; show how you prevent/escalate/resolve.
No linkage to project controls: team management should connect to time, cost, quality, risk, and deliverables.

A well-structured UCT-style answer typically ends with a concluding line like:

“Managing the project team ensures capability, alignment, communication, and accountability—therefore improving predictability of delivery.”

Planning and Developing the Project Team: Roles, Capabilities, and Team Agreements (UCT Module 7)

Planning a project team is where most “foundation-level” marks are earned because you can demonstrate method. Many students lose points by skipping the early planning steps and jumping directly into leadership or conflict resolution. UCT Module 7 assessments often reward answers that start with team planning, then move logically into development, agreements, and performance monitoring.

Determining Team Composition and Required Competencies

A strong exam answer explains that the project manager determines:

What roles are needed
What competencies each role needs
How many people
When they are needed
How long they will be available

Use a structured approach:

Break down the work (WBS)
- Identify deliverables and activities.
Map activities to roles
- Determine who performs what.
Assess skills and competency
- e.g., requirements analysis, UI/UX, data engineering, QA testing.
Estimate required time and availability
- Use calendar-based planning (including known unavailability).
Plan for gaps
- Use training, mentoring, temporary recruitment, or subcontracting.

Example: Competency Planning with a Simple Skills Matrix

Create a quick skills matrix in your exam answer (even if not asked for, it shows structure). Example:

Activity/Deliverable	Required Skill	Role
Define functional requirements	Requirements elicitation	Business Analyst
Design user interface	UI/UX design	UX Designer
Implement dashboard logic	Software development	Developer
Test and validate	QA testing	QA Lead

Then add a paragraph explaining what happens if a role is missing:

If UX design capacity is insufficient → re-scope lower-priority UI features or bring in contractor support.
If QA is under-resourced → increase testing time buffer or adjust release schedule.

Recruitment/Assignment and Onboarding

A team-building answer also includes how team members are integrated. Onboarding should include:

project overview and objectives,
scope boundaries,
reporting structure,
tool access and documentation location,
communication routines,
risk and change expectations.

A high-mark onboarding paragraph often mentions that onboarding should not be a one-time meeting; instead it should be an iterative process supported by:

templates,
project documentation,
initial mentoring,
early check-ins (first week success).

Team Development: From “Forming” to “Performing”

Even when the assessment does not name specific models, exam markers appreciate that you recognise team development stages. A common model used in project management foundation teaching is Tuckman’s stages:

Forming: initial orientation, uncertainty.
Storming: conflict and role negotiation.
Norming: agreements and routines develop.
Performing: stable high output.
Adjourning: wrap-up and knowledge capture.

Your exam answer can use it without heavy theory by explaining what the project manager does at each stage.

Example: Managing Storming (Conflict Stage)

Storming often includes:

disagreement on approach,
unclear ownership,
competing priorities,
differences in working styles.

The project manager responds by:

clarifying roles and deliverable ownership,
facilitating structured discussions (agenda + decision criteria),
using evidence (requirements, data, constraints),
documenting outcomes (minutes, action logs),
setting escalation routes.

This makes the answer both realistic and marks-oriented.

Team Agreements and Ground Rules (Why They Matter)

Team agreements prevent common failure modes:

unclear meeting norms,
unclear response times,
blame-based communication,
inconsistent work quality standards.

A team agreement can cover:

Communication
- channel selection (email/Slack/Teams),
- meeting cadence,
- response-time expectations.
Work standards
- definition of done,
- documentation standards,
- version control practices.
Collaboration
- review process,
- peer feedback expectations,
- how to request help.
Decision making
- who decides vs who recommends,
- how disagreements are resolved.
Escalation
- timeline for escalating risks and blockers,
- who to notify and how quickly.

Example Team Agreement Clause (Assessment-Friendly)

You can include a short clause such as:

“Any blocker that risks the timeline must be escalated within 24 hours to the project coordinator, with a mitigation proposal.”

This demonstrates discipline. Even if your course does not require numbers, including a timeline shows you can operationalise process.

Motivation and Engagement: Practical Methods

Motivation in team management must be connected to actions. A project manager can use:

Meaning and purpose
- link tasks to project value (student experience, business impact, service quality).
Autonomy
- allow team members to choose how to complete tasks within boundaries.
Competence
- provide feedback and opportunities to learn.
Recognition
- acknowledge achievements publicly and specifically.
Fairness
- workload distribution based on capacity.
Support
- remove barriers and provide tools.

Counter-Argument to “One-size-fits-all Motivation”

A good exam answer may include a counterpoint:

Motivation differs by individual. Some respond more to recognition, others to autonomy or growth.
Therefore, the project manager should monitor engagement signals (attendance, contribution quality, meeting readiness) and adapt leadership approaches.

UCT-style answers tend to reward reflective and realistic thinking, not rigid slogans.

Measuring Team Development: Indicators for Assessment

Even in foundation modules, marks often come from measurable team management. Indicators can include:

meeting attendance and punctuality,
action item closure rate,
reduction in rework,
increasing predictability of deliverables,
decreased escalation frequency (or faster escalation resolution),
improved quality metrics (defect rates),
team survey feedback (if available).

A useful exam response links measurement to improvement cycles:

“If indicators are worsening, adjust planning, communication, coaching, or resourcing.”

Leading, Communicating, and Resolving Conflicts in a Project Team (UCT Module 7)

Leading a project team is about influencing how the team behaves under pressure. Conflict is normal in projects because constraints create trade-offs: scope vs time, quality vs cost, and individual vs team interests. UCT assessments often include case questions requiring conflict management and communication planning. This section provides structured ways to write those answers and score well.

Communication Planning: Who Needs What, When, and How

A strong “assessment answer” usually includes a communication plan concept:

communication objectives,
audience,
channels,
frequency,
content format.

For foundation level, you can refer to stakeholder communication and team communication separately.

Team Communication Routines

Typical routines include:

Kick-off meeting
- align goals, roles, timeline expectations.
Daily/weekly stand-ups
- highlight progress, blockers, next steps.
Status meetings
- track deliverables, risks, changes.
Planning sessions
- allocate work and adjust priorities.
Review meetings
- present outputs to stakeholders.
Retrospectives
- capture lessons and improve teamwork.

A good exam answer explains why routines matter:

They reduce uncertainty.
They detect issues earlier.
They create transparency and accountability.

Stakeholder Communication vs Team Communication

UCT assessments may ask about “managing the team” but marks are improved by showing you understand that stakeholders influence team capacity and priorities.

Team communication focuses on delivery coordination.
Stakeholder communication focuses on expectations, approvals, and risk visibility.

A high-mark statement:

“Effective team communication is necessary but not sufficient; the project manager must also manage stakeholder expectations through structured updates and transparent escalation.”

Leadership Styles and When to Use Them

In project management education, you commonly see leadership styles discussed in relation to team maturity and task complexity. Your exam answer should not claim that one style is always best. Instead, you can state:

When tasks are new and uncertainty is high, directive guidance may be needed initially.
When the team is competent and trusted, a more participative style improves engagement.
When risk is high or quality is at stake, the project manager must be more assertive and monitoring-focused.

Example: Choosing a Response to Low Quality

If QA reports repeated defects in a release candidate:

directive response: enforce definition of done, require peer review before release.
participative response: run a root cause analysis with the development team to address systemic issues.
supportive response: provide coaching on testing approach.

This shows leadership flexibility.

Conflict Types and Practical Resolution Methods

Not all conflicts are the same. In exam answers, you can categorise conflicts into:

Task conflict (disagreement on how to deliver work)
Process conflict (disagreement on procedures and roles)
Relationship conflict (personal tensions, communication breakdown)
Resource conflict (competing needs for limited time, budget, tools)

Different conflict types require different responses.

Conflict Resolution Framework (Assessment-Friendly)

You can use a simple structured approach:

Identify the conflict
- What exactly is being disputed?
- Which project objective is affected?
Clarify facts
- check requirements, versions, decision logs, evidence.
Listen to perspectives
- understand constraints and assumptions.
Focus on shared goals
- project outcomes, deadlines, quality standards.
Generate options
- propose alternatives and trade-offs.
Decide and document
- agree on next steps and ownership.
Follow up
- confirm whether behavior improves and whether issue repeats.

This process is adaptable to many case prompts.

Worked Assessment Answer Example: Managing a Team Dispute Over Scope

Scenario: In a campus web portal project, the UX Designer wants more time for additional user stories, while the Developer argues that the sprint goal must be protected. The Project Manager notices tension in meetings and delayed decisions.

Model answer structure:

Acknowledge and diagnose
- “This appears to be a task/process conflict linked to scope vs time trade-offs.”
Clarify the objective
- “Sprint goal is to deliver the agreed minimum viable features.”
Separate personal tension from decision criteria
- “The discussion should focus on evidence: requirements, priority, acceptance criteria.”
Use decision rules
- “If new user stories are required, they must be added via change control or moved to the next sprint based on priority.”
Facilitate an options discussion
- Option 1: protect current sprint scope; log new stories for next sprint.
- Option 2: trade off a lower-priority story to include one high-value story.
Document outcomes
- Update sprint backlog, decisions, and responsibilities.
Follow up with team communication
- Reinforce team agreement on how to request scope changes and how decisions are recorded.

This answer scores because it demonstrates conflict diagnosis, evidence-based decision making, and process discipline.

Handling Underperformance and Maintaining Team Fairness

Conflict is not only interpersonal; underperformance can become a team-wide issue. An exam answer should address:

why underperformance occurs (skills gap, unclear requirements, unrealistic workload, personal issues),
how to address it (coaching, clear expectations, measurable goals),
how to do it fairly and respectfully.

Example: Underperformance Due to Unclear Requirements

Scenario: A junior analyst repeatedly produces reports with missing sections. The team starts blaming the analyst, and the quality of downstream work declines.

Good exam answer elements:

Clarify whether the issue is training or unclear definition of done.
Provide templates and examples.
Agree measurable quality criteria.
Set check-in milestones and feedback cadence.
Recognise improvement publicly to rebuild confidence.

Marks are gained when you avoid punitive language and instead focus on improvement through structure.

Escalation: When and How to Move Up the Chain

A high-quality answer mentions escalation thresholds:

sustained schedule risk,
repeated quality failures,
unresolvable stakeholder conflict,
blocked approvals due to decision delays.

Escalation should include:

what is happening,
impact on time/cost/quality,
proposed solutions,
recommendation for decision.

A common exam marker phrase:

“Escalate early with context, options, and a recommendation rather than escalating problems without solutions.”

Controlling Team Performance and Managing Change: Schedules, Quality, and Risk (UCT Module 7)

Managing the project team also includes controlling performance: ensuring work outcomes match plan and that team operations adjust when changes occur. UCT foundation assessments frequently integrate team management with project control: if team performance collapses, schedule control and risk management become impossible. This section ties team management to measurable performance control mechanisms.

Team Performance Management: Planning to Monitoring

A coherent answer uses the “plan-do-check-act” logic:

Plan
- define roles, responsibilities, deliverables,
- set success criteria and quality expectations.
Do
- execute tasks.
Check
- monitor progress, quality, and issues.
Act
- adjust workload, clarify requirements, escalate risks, retrain, or revise schedule.

In exam conditions, you can show this by listing:

progress tracking,
quality assurance,
risk monitoring,
change control.

Progress Tracking and Work Visibility

Progress tracking should answer:

What has been completed?
What is next?
Are deliverables on schedule?
What blockers exist?
What is likely to change?

A high-mark answer often includes:

tracking by milestones (not only hours worked),
using work status reports,
linking progress to deliverables.

Example: Milestone-Based Progress

If the project has milestones:

M1: Requirements sign-off
M2: Prototype approved
M3: Pilot release completed

Then team performance is assessed by milestone completion status. If M1 is delayed, it affects all downstream tasks.

Quality Management with Team Involvement

Team management improves quality because quality is produced by the team’s processes, not only by QA. You can explain quality in terms of:

Definition of done
Peer review
Testing strategy
Documentation standards
Root cause analysis
Continuous improvement

Example: Defect Trend Monitoring

If you include quantitative reasoning, do it consistently. For instance (using a hypothetical but internally consistent example you can show in an exam answer):

In sprint 1, the team found 12 defects after testing.
In sprint 2, after improving peer review, defects reduced to 7 defects.
That indicates quality process improvement and should be documented as a lesson.

Even when the assessment doesn’t require numbers, including a defect-trend example can make your answer more concrete.

Capacity Management: Workload, Time, and Dependencies

Projects fail when team workload exceeds capacity without adjustment. Capacity management includes:

workload planning based on availability,
dependency tracking,
reducing multitasking,
identifying critical path activities,
rebalancing tasks when delays occur.

Example: Academic Calendar Constraints

In South African university contexts, team availability may be impacted by:

teaching schedules,
marking periods,
assessments.

A team capacity plan might include:

early planning for heavy workloads before exam weeks,
buffer time for approvals required by academic committees,
scheduling workshops in teaching breaks.

UCT exam questions may not explicitly mention university calendars, but it is a strong realism layer when you reference typical constraints.

Risk Management as a Team Control Tool

Risk management connects to team performance because many risks show up as early warnings:

frequent scope discussions,
missing deliverables,
unresolved dependencies,
increasing rework.

A team control system should include:

a risk register,
regular risk review in status meetings,
mitigation actions owned by specific roles.

Example: Risk Escalation Trigger

If a dependency is not confirmed by week 3, then:

schedule risk increases,
contingency actions are activated,
stakeholder approval is escalated.

Your exam answer should include triggers because it shows control maturity.

Change Management: Handling Requests Without Breaking the Team

Team management becomes unstable when changes are introduced without process discipline. Change management includes:

Identify change
- what exactly changes (scope, timeline, resources, quality).
Assess impact
- time impact, cost impact, quality risk.
Decide
- accept, reject, defer, or re-scope.
Communicate
- update plan, roles, responsibilities, and expectations.
Document
- change record and approval.

A good exam answer will stress that change affects team motivation and trust if not handled transparently.

Counter-Argument: “We Can Just Handle It Informally”

A realistic assessment answer includes why informal changes are dangerous:

it increases rework,
it breaks sprint commitments,
it undermines accountability,
it causes inconsistent expectations.

Therefore, informal decisions must be either formalised quickly or rolled into the next change control cycle.

Performance Reviews and Continuous Improvement

You can conclude team control with a continuous improvement mindset:

conduct retrospectives,
update working agreements,
capture lessons learned,
use metrics to improve planning accuracy.

A strong assessment answer ends with the idea that team management is iterative:

plan improves based on what the team learns.

Assessment Answers: Writing Model Responses for UCT Module 7 Questions (Plus Integrated Case Examples)

This final section is designed to help you perform in an exam by providing model assessment answers and the reasoning structure that examiners expect. These are formatted as if you were responding to common question styles: explain, discuss, analyse a case, or propose a plan. You can adapt these to specific prompts by swapping the scenario details.

How Examiners Usually Reward Marks in “Managing a Project Team” Questions

UCT foundation questions typically assess:

understanding of team management concepts,
application to realistic scenarios,
structure (clear steps and logical flow),
appropriate tools (e.g., RACI, communication plans, escalation),
professional tone (not vague, not emotional, process-driven),
link to outcomes (time/cost/scope/quality/risk).

Therefore, an exam answer must do more than define terms. It must show what you would do and why.

Model Answer 1: “Explain how you would manage a project team to ensure successful delivery.”

Model structured answer (UCT-friendly):

To manage a project team for successful project delivery, the project manager must integrate planning, leadership, communication, performance control, and continuous improvement.

Plan team requirements
- Break down deliverables using the WBS and map activities to roles.
- Identify required competencies and ensure capacity matches availability.
- Plan for gaps through training, mentoring, or additional resources if necessary.
Build team clarity
- Assign clear responsibilities using tools such as RACI to reduce ambiguity.
- Confirm reporting lines, authority to act, and escalation routes.
- Establish project-wide “definition of done” and quality expectations.
Develop and align the team
- Use team development approaches to support the movement from forming to performing.
- Facilitate early alignment sessions and provide onboarding support (documentation, templates, tool access).
Lead and motivate
- Use leadership that fits the team’s maturity and risk level.
- Apply motivation techniques through recognition, feedback, fairness in workload, and removing barriers.
- Support the team during disagreements by focusing on evidence and shared objectives.
Communicate effectively
- Define team communication routines (stand-ups/status meetings/retrospectives).
- Maintain stakeholder communication through structured updates and transparent escalation.
- Use consistent channels and formats to reduce misunderstandings.
Control performance and manage quality
- Track progress against milestones and verify deliverables using acceptance criteria.
- Monitor quality through peer review, testing, and defect trend tracking.
- Conduct regular risk reviews and implement mitigation actions.
Manage change
- Handle scope requests using a change control process: assess impact, decide, communicate, and document.
- Prevent informal scope changes that create rework and undermine trust.

By combining structured planning with leadership and measurable control, the project manager improves predictability of delivery, reduces rework, and maintains team effectiveness throughout the project lifecycle.

This answer scores because it includes all major components and ties them to delivery outcomes.

Model Answer 2 (Case-Based): Conflict Between Developer and QA During a Release Sprint

Prompt (typical style):
“Assume that during a release sprint, the Developer and QA are in conflict about whether the product is ready for deployment. Describe how you would manage the team conflict and ensure a quality outcome.”

Model answer:

The conflict between the Developer and QA is a task/process conflict affecting quality and delivery predictability. To manage it effectively, I would take a structured conflict resolution approach while maintaining clarity on quality expectations.

Diagnose and separate the conflict
- Identify what each party believes is the problem: readiness criteria, test coverage, defect severity, or misunderstanding of acceptance criteria.
- Separate personal tension from the underlying decision to keep the discussion productive.
Clarify facts and acceptance criteria
- Review the agreed definition of done and the acceptance criteria for the release.
- Check the current defect list, defect severity ratings, and test results.
- Confirm what was promised in the sprint backlog and what scope is included in the release.
Facilitate an evidence-based decision
- Convene a short meeting with Developer, QA Lead, and the project manager (and possibly Business Owner if required).
- Ask each party to present evidence: test outcomes, defect counts, known risks, and mitigation options.
Generate options and trade-offs
- Option A: Proceed only if all “release blocking” defects are resolved, even if it shifts the release date.
- Option B: Proceed with controlled risk if defects are non-blocking and mitigation actions are agreed.
- Option C: Defer non-critical features to a follow-up release to protect sprint commitments.
Decide, document, and communicate
- Apply a pre-agreed decision rule: who can approve release readiness and under what conditions.
- Document the decision, including remaining risks and required actions.
- Communicate the outcome clearly to the wider team and stakeholders.
Follow up
- Conduct a short retrospective after the release readiness decision.
- Identify process improvements, such as earlier test integration or clearer defect severity rules.

Through evidence-based clarification, structured decision making, and documented acceptance criteria, the project manager resolves the conflict while protecting both quality and delivery commitments.

This answer also implicitly demonstrates leadership, communication, and control.

Model Answer 3: Managing Underperformance Without Damaging Team Morale

Prompt (typical style):
“A team member repeatedly misses deliverable requirements and lowers overall quality. Describe how you would handle the situation.”

Model answer:

I would handle underperformance with a structured, fair, and improvement-focused approach, because underperformance often results from unclear expectations, insufficient support, or misalignment between capacity and workload.

Check whether the issue is clarity or capability
- Review the deliverable requirements and compare the output against acceptance criteria.
- Identify whether the missing elements reflect misunderstanding, gaps in skill, or inadequate guidance.
Provide clear expectations
- Update the definition of done and provide templates or examples of acceptable deliverables.
- Clarify deliverable structure, required sections, and review process.
Agree measurable improvement goals
- Set a short, measurable target (e.g., “deliver the next report with complete sections and pass quality review”).
- Define a feedback schedule and the review points in the timeline.
Support the team member
- Offer coaching or training on the missing skill.
- Pair them with a senior team member for guidance during the next iteration.
Monitor progress and adjust workload
- Confirm that the workload is realistic given availability.
- If overload is the cause, rebalance tasks and remove non-critical work.
Maintain fairness and morale
- Provide feedback privately and respectfully.
- Avoid blaming language; focus on improvement and delivery standards.
- Recognise improvement when it occurs to rebuild confidence.
Escalate only if required
- If performance does not improve despite support and clear expectations, escalate according to organisational HR/procedure while keeping the project risk visible.

This approach balances quality outcomes, team morale, and professionalism by turning the problem into a controlled improvement cycle.

Model Answer 4: Create a Team Communication Plan (Concise and Assessment-Friendly)

Prompt:
“Draft a team communication plan for a medium-sized project team. Include frequency, audience, and channel.”

Model answer:

A team communication plan should ensure timely coordination, transparency, and early escalation of risks. I would propose the following communication routines:

Weekly status meeting
- Audience: Project team and project coordinator (and QA/technical leads as needed).
- Frequency: Weekly.
- Channel: In-person or video conference.
- Agenda: progress vs milestones, upcoming work, blockers, risks, and decisions required.
Daily stand-up (or three times per week for non-daily teams)
- Audience: Delivery leads and team members.
- Frequency: Daily (or at least three times per week if workload is lower).
- Channel: Chat tool (Teams/Slack) or short stand-up meeting.
- Purpose: share progress, raise blockers early, and align priorities.
Bi-weekly stakeholder update
- Audience: Project sponsor and relevant stakeholders.
- Frequency: Every two weeks.
- Channel: Email summary plus meeting if approvals/decisions are required.
- Content: milestone status, risk summary, changes, and decisions needed.
Retrospective
- Audience: Entire project team.
- Frequency: At the end of each sprint/phase.
- Channel: Meeting with documented action items.
- Output: improvements to working agreements and process changes.
Escalation mechanism
- Audience: Project sponsor or steering group as appropriate.
- Trigger: any blocker that threatens the timeline or quality, or unresolved conflict after facilitation.
- Channel: urgent call + written summary.
- Minimum content: what happened, impact, mitigation options, and recommendation.

This plan provides both operational coordination and stakeholder governance while supporting early detection and resolution.

Integrated Case Example: A Full Assessment-Style “Project Team Management” Response

To practice exam performance, consider a multi-part question where you must describe team planning, communication, conflict handling, and performance control. Below is an integrated answer that you can adapt.

Case scenario (coherent and exam-ready):
A project at a university aims to deliver a new student-facing portal. The team includes a Business Analyst, UX Designer, Developer Team Lead, QA Lead, and a Project Coordinator. During the first month, delivery slips because requirements are unclear, meetings become tense between UX and Development, and QA reports increasing defects.

Integrated response:

Team planning and clarity
- First, confirm required roles and competencies and ensure the availability plan considers peak university workload periods.
- Build clarity by assigning responsibility using RACI: Business Analyst as accountable for requirements, UX as responsible for interface design, Developer team lead as responsible for implementation, and QA lead as responsible for verification.
- Agree a definition of done for each deliverable so “ready” is objectively measurable.
Onboarding and requirements discipline
- Onboard team members with documentation and templates (requirements format, user story structure, acceptance criteria).
- Introduce requirements review routines: weekly requirement refinement with documented decisions.
- Use a change control process for any new or revised user stories to prevent uncontrolled scope expansion.
Communication routines
- Implement weekly status meetings and a short daily/three-times-per-week stand-up to ensure blockers are surfaced early.
- Provide bi-weekly stakeholder updates summarising milestone progress, decisions needed, and risks.
Conflict resolution between UX and Development
- Diagnose whether conflict is task-related (design feasibility vs agreed acceptance criteria), process-related (review timing), or resource-related.
- Facilitate a structured session focusing on evidence: agreed user stories, constraints, technical feasibility, and quality expectations.
- Decide trade-offs using agreed rules: if the design includes features that are outside sprint scope, defer them or trade off lower priority items through the backlog.
Quality management
- Strengthen QA integration by requiring peer review before QA testing and ensuring test criteria are part of the definition of done.
- Use defect severity categories and ensure release readiness is based on agreed blocking criteria.
Performance control and continuous improvement
- Track progress by milestones (requirements sign-off, prototype approval, pilot release).
- Monitor defect trends and rework rate to assess whether process improvements are working.
- Conduct retrospectives after each sprint to adjust team agreements: meeting norms, response times, and review processes.

By addressing clarity, communication structure, conflict resolution, and quality control together, the team can stabilise performance and regain delivery predictability while maintaining stakeholder confidence.

This integrated answer is exam-effective because it responds to likely sub-questions with consistent logic and practical actions.

How to Tailor Your Answer to Different Marks Allotments

In UCT exams, questions often come in different mark allocations. Adjusting length and depth can help you stay within time while still scoring.

For 5–8 marks

Use a list of 5–7 bullets.
Include one tool (e.g., RACI, communication plan, escalation).
Conclude with one sentence linking to outcomes.

For 10–15 marks

Use structured steps (5–7 steps) with short explanations.
Include one case-based example.
Mention measurement (progress, quality, risks).

For 20+ marks

Include: planning → leadership/communication → conflict management → control/change → continuous improvement.
Use a coherent integrated response (like the case scenario above).
Demonstrate trade-offs and risks.

Final Checklist for Exam Answers (Quality-Control for Your Writing)

Before submitting, ensure your response includes:

Clear structure (numbered steps or headings).
Specific actions (not only definitions).
Tools or frameworks appropriate to foundation level (RACI, communication routines, change control).
Conflict and performance addressed explicitly.
Link to project outcomes (time, quality, stakeholder confidence, risk reduction).

Summary: What “Good” Looks Like for UCT Module 7 Team Management Answers

A top-mark “Managing a Project Team” assessment answer demonstrates that team management is a structured discipline: you plan roles and capacity, set agreements, lead and communicate consistently, resolve conflicts with evidence and decision criteria, and control performance through quality and risk monitoring—while managing change through transparent process.

When your answers are written like operational plans rather than generic explanations, they match how UCT project management assessments evaluate understanding and application.