The Scenario
You have just joined a SA fintech as a junior project coordinator. Your project manager hands you a brief for a new internal initiative ("Migrate the customer onboarding form from PDF to a digital flow") and asks for a complete project plan by Friday.
The Brief
Produce the artefacts a project manager would expect: a one-page project charter, a milestone schedule, a Gantt chart (sketched), and a budget summary. Make sensible assumptions about scope, team size, and timeline; document them.
Deliverables
- A one-page project charter covering: business case summary, objectives (SMART), in-scope and out-of-scope, key deliverables, stakeholders, success criteria, assumptions, and constraints
- A milestone schedule with at least eight milestones across initiation, planning, execution, and closure phases
- A Gantt chart description (text-based or linked sketch) showing dependencies and the critical path
- A budget summary with at least three cost categories (people, software, contingency) and a defended contingency percentage
Submission Guidance
Real coordinators document assumptions because they do not know everything on day one. Where you make a guess, mark it as an assumption. Senior PMs respect that more than guessing confidently.
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.