Junior Project Coordinator

Sample Answer

The five phases are initiation, planning, execution, monitoring and control, and closure. In initiation, you define the project purpose, objectives, and feasibility, and produce a project charter and identify key stakeholders. In planning, you develop the detailed project management plan: scope, schedule, cost, quality, resources, and risk. In execution, the team carries out the work to produce the deliverables. Monitoring and control runs concurrently with execution — you track progress against the baseline, manage change requests, and address risks and issues as they arise. In closure, you formally complete all deliverables, hand over to the client or operations team, conduct lessons learned, and archive project documentation.

Sample Answer

A risk is a potential event that has not yet happened — it may or may not occur in the future. An issue is a problem that has already occurred and is currently affecting the project. In practice, a good project coordinator maintains a risk register that tracks identified risks, their probability, impact, mitigation strategy, and owner. When a risk materialises, it moves to the issue log and becomes something that needs immediate management action, not just monitoring. In SA corporate environments, especially in banking and IT, the distinction matters for reporting — executives want to see risks separated from active issues.

Sample Answer

I would first have a direct conversation with the stakeholder — not a formal escalation yet — to understand whether the missed milestones reflect a capacity problem, an unclear expectation, or a deeper blocker I was not aware of. I would review whether the milestone was clearly defined with a specific deliverable and due date, because ambiguity on my side may be contributing to the problem. If the issue persists after that conversation, I would document the impact of the delays on the project plan and share it with the stakeholder formally, giving them visibility into the downstream effects of their dependencies being late. If it continues after that, I would escalate to the project sponsor with documentation, not as a complaint but as a formal risk to project delivery that requires a decision.

Sample Answer

A RACI matrix is a responsibility assignment tool that maps project tasks or deliverables to four roles: Responsible (the person doing the work), Accountable (the single person ultimately answerable for the outcome, usually a decision-maker), Consulted (people whose input is needed but who are not doing the work), and Informed (people who need to be kept updated but do not have a formal role). I would use it at the beginning of a project during planning to clarify ownership — particularly in projects with multiple departments involved where people are unclear about who is doing what. In South African matrix organisations, where team members report to multiple managers, a RACI prevents the confusion of either duplicated effort or tasks falling through the cracks.

Sample Answer

During my studies, I coordinated a group research presentation where a team member submitted their section the night before, which was completely off-brief and needed to be redone. I had not built buffer time into the plan and had not checked in on their progress early enough. I stayed up with that person to restructure their section and pulled in another team member to help with the visual slides. We delivered on time and passed well. The lesson I took: check on dependencies at the midpoint, not just the deadline, and build two days of buffer into any plan that relies on others. I now build explicit checkpoint dates into any project I coordinate.

Sample Answer

The triple constraint, also called the project management triangle, refers to the three interdependent variables in every project: scope, time, and cost. The principle is that you cannot change one without affecting at least one of the others. If a client wants to add more scope, either the timeline must extend or the budget must increase — you cannot get more for free. In practice, this is the most important concept for managing client expectations. When a stakeholder requests a change in scope midway through a project, the first thing I would do is assess the impact on time and cost and present that trade-off to the project sponsor for a decision. It keeps the conversation factual rather than emotional.