School: Minister Destiny Testimony Schools Track: Adult Class: Certificate Topics — Year 1 (Foundations) · Home: Schools — Adult track Certificate behind this topic: "Project Management Skills for Leaders" — LinkedIn Learning, earned by Minister Destiny Marie Morgan (May 29, 2025) Founded and presented by: Minister Destiny Marie Morgan, Minister
This lesson is educational information from Minister Destiny Testimony Schools. It teaches the public body of knowledge in this subject — the same ground Minister Destiny studied for her certificate — in this school's own words. It is not the original course, it does not award the original credential, and it is not legal or medical advice. If you are in danger right now, call 911.
Before you start
- This school never asks your name. Your progress is saved to your student record, so you can pick up on any device. If you pass this unit's quiz (80% or higher, retakes allowed), you earn a downloadable certificate with a blank line — you write your own name on it after you save it. Quiz answers are not shown; if you miss a question, re-read the lesson and try again.
- This unit is not about software, charts for their own sake, or the project manager's full professional toolkit. It is about the leader's share: the decisions only the person leading the work can make, and the honesty that keeps a project real.
- Minister Destiny Marie Morgan earned this certificate while building real things on real deadlines. Projects in community and creative life fail the same way corporate ones do — unclear done, silent slippage, burned-out teams — and this unit teaches the defences.
The lesson
Part 1. Project or Ongoing Work? Knowing Which You Are Leading
A project is work with a beginning, an end, and a defined result: launch the website, run the conference, move the office, publish the book. Ongoing work has no end: answering enquiries, maintaining the website, serving customers. The distinction sounds obvious and is constantly blurred, and the blur is expensive. Treat ongoing work as a project and you will declare it "finished" while it still needs staffing forever. Treat a project as ongoing and it never finishes at all — it just becomes a permanent, unexamined drain with no moment where anyone asks whether it worked.
Leaders protect both kinds by naming them correctly at the start. For a project, write the end down: the date or the condition that closes it, and what happens to anything it leaves running. For ongoing work, staff and budget it as a rhythm, not a sprint. Many painful workloads are simply projects that were never closed — their maintenance quietly inherited by whoever launched them. Closing is a leadership act, and Part 6 returns to it.
Part 2. Scope and the Definition of Done
Scope is the boundary of the work: what is included, and — written down with equal clarity — what is not. Most scope trouble is not bad faith; it is a hundred reasonable additions, each small, none ever weighed against the deadline and the team. Leaders defend scope kindly and firmly: every addition is welcome to be proposed, and every proposal gets the same honest question — what leaves, what moves, or what extra resource arrives, to make room for it? Additions without subtractions are how deadlines become fictions.
Inside scope sits the definition of done, the most valuable paragraph in any project. Done describes the finished result in checkable terms: not "website updated" but "twelve pages live, booking form tested end to end, accessibility check passed, and the old site redirecting." Write it with the people who will receive the work, because their done and your done are often different countries. When done is checkable, progress becomes measurable, arguments about "nearly there" evaporate, and finishing becomes an event the team can actually celebrate instead of a rumour.
Part 3. Breaking Work into Steps and Owners
A project becomes manageable when it is broken into steps small enough to see: tasks of days, not months, each with one named owner. "Team to organise the venue" owns nothing; "Leah to confirm the venue contract by Friday" owns something. The breakdown itself is a thinking tool — the act of listing steps exposes the forgotten work (the insurance nobody mentioned, the translation, the testing week) while forgetting is still free. Leaders do this breakdown with the doers, not for them: the people closest to the work know where its hidden corners are, and a plan they helped build is a plan they believe.
Sequence the steps by dependency: what must exist before what else can start? The invitation cannot be designed before the date exists; the date cannot be fixed before the venue is confirmed. Lay the dependencies out and the project's true shape appears, including its critical path — the chain of dependent steps that sets the earliest possible finish. Time spent arguing with the critical path is wasted; time spent protecting it — clearing blockers for the people on it, first — is leadership.
Part 4. Schedules, Dependencies, and Seeing Slippage Early
A schedule is a hypothesis: these steps, in this order, taking about this long. Experienced leaders hold schedules honestly, which means building them from estimates by the people doing the work, adding margin where uncertainty is real, and then watching the schedule the way a pilot watches instruments — frequently, and believing what they say. Slippage is almost always visible early, in small signals: a step that starts late, a dependency delivered half-finished, estimates quietly growing at every check-in. The projects that fail "suddenly" usually whispered for weeks.
Seeing slippage early only helps if responding to it is safe and useful. The leader's response menu is short: add resource, remove scope, move the date, or accept lower polish in a defined place — chosen openly, with the trade-off stated, rather than the default fifth option, which is hoping. Hoping is the most expensive option on the menu because it spends the team's remaining margin without buying anything. And protect the people reporting slippage: the first bad-news carrier who gets blamed teaches the whole team to report green until the week it goes red beyond hiding.
Part 5. Risk Spotting Without Drama
Risk is anything that might knock the project off its plan: a supplier failing, a key person leaving, a cost doubling, a permission arriving late, a technology not working as promised. Leaders spot risks by asking, at the start and at every review, one plain question: "What could make this late, over budget, or not good enough — and what would we see first if it were starting to happen?" Write the top risks down with their early-warning signs and a rough plan for each: prevent what you can, prepare a response for what you cannot, and accept small risks knowingly rather than discovering them.
Proportion is the skill. A risk list of forty items manages nothing; five real ones, owned and watched, manage a great deal. Revisit the list at each status review, because risks expire and new ones are born as the work changes. And distinguish a risk from a problem: a risk might happen; a problem is happening. Problems get the Part 4 menu immediately. Risks get watched, cheapened, and planned for — the quiet work that makes project success look, from outside, like luck.
Part 6. Status Without Spin, Closing, and Lessons Learned
Status reporting is where project culture is proved. A useful status is short, regular, and structured: what was planned, what is done, what is next, what is blocked, and what decision or help is needed — with the overall state stated honestly as on track, at risk, or off track, and why. Spin — reporting green because red is unwelcome — does not protect a project; it merely ensures that help arrives after it can no longer help. Leaders set the price of honesty by their reaction to the first red report they receive: thank it, act on it, and the reports stay true.
Closing deserves the same seriousness as starting. Confirm the definition of done is met, hand over anything the project leaves running to a named owner, release the people and the budget formally, and thank the team specifically. Then hold the lessons-learned conversation while memory is fresh: what surprised us, what would we do differently, what should become a checklist for next time? Write three to five lessons down where the next project will actually find them. A team that closes well starts its next project already smarter — which, across a leader's career, is the whole compounding advantage.
Words to know — Project Management Skills for Leaders
- Project — Work with a beginning, an end, and a defined result — as distinct from ongoing work, which runs as a rhythm.
- Scope — The written boundary of a project: what is included, and what is explicitly not.
- Definition of done — A checkable description of the finished result, agreed with the people who will receive the work.
- Owner — The one named person responsible for a step; shared ownership usually means no ownership.
- Dependency — A relationship where one step cannot start or finish until another does.
- Critical path — The chain of dependent steps that sets the earliest possible finish date of the project.
- Slippage — The early, usually small signs that work is falling behind the schedule.
- Risk — Something that might happen and would knock the project off plan; a problem, by contrast, is already happening.
- Status report — A short, honest account: planned, done, next, blocked, and what help or decision is needed.
- Lessons learned — The recorded surprises and improvements from a finished project, kept where the next project will find them.
Myths vs facts — Project Management Skills for Leaders
- Myth: Good project management is mostly good software. Fact: Tools record a plan; they do not create scope, honesty, or ownership. The leader's decisions in this unit are the management.
- Myth: Adding a small feature never hurt a deadline. Fact: Deadlines die by a hundred small additions, none weighed against what must leave or move. Scope discipline is kindness to the date.
- Myth: A confident green status keeps morale up. Fact: False green delays help until it cannot help. Teams trust leaders whose red reports are welcomed and acted on.
- Myth: Risk management is pessimism. Fact: Risk work is what makes optimism affordable: five real risks, owned and watched, protect the whole plan.
- Myth: Once a project launches, closing is paperwork. Fact: Unclosed projects leak maintenance, budget, and guilt for years. Closing — handover, release, lessons — is a leadership act.
Think it through — Project Management Skills for Leaders
A community centre director is leading a summer programme launch in eight weeks. The plan lives in her head. Three weeks in: the venue paperwork is "nearly done," the flyer designer is waiting on dates the director has not confirmed, two volunteers have quietly stopped attending planning meetings, and a funder's report deadline — which nobody listed as a step — falls in week six. In meetings, the director reports "all on track," because the team looks tired and she does not want to add pressure.
Walk it through: (1) Part 2 starts the repair: write the scope and the definition of done — programme dates, sessions, enrolment numbers, safeguarding checks — with the staff who will receive the work, so "launched" becomes checkable. (2) Part 3 does the breakdown the project never had: every step listed with the doers, one owner each — which instantly exposes the funder's report and the venue dependency blocking the flyer. (3) Part 4 reads the signals she has been smoothing over: a late dependency, growing estimates, volunteers drifting away are textbook early slippage, and her menu is real choices — confirm dates this week, drop one planned session, or move the launch — stated openly. (4) Parts 5 and 6 fix the culture: name the top risks (venue, volunteer capacity, funder deadline), and replace "all on track" with a structured status — planned, done, next, blocked, help needed. The team's tiredness is not a reason to hide the status; it is the reason the status must be honest, because tired people cannot absorb late surprises.
Try this — Project Management Skills for Leaders
- ☐ Take one piece of your work and classify it honestly: project or ongoing rhythm — then staff it accordingly
- ☐ Write a checkable definition of done for something currently described as "nearly finished"
- ☐ Break a real project into steps of days, each with one named owner, with the doers in the room
- ☐ List your current project's top five risks, each with its early-warning sign
- ☐ Practise a status report in the five-part structure: planned, done, next, blocked, help needed
Resources to keep — Project Management Skills for Leaders
- Project Management Institute (pmi.org) — The professional body's free explainers on project management concepts, roles, and practice.
- Atlassian — Project Management Guide (atlassian.com) — Free, practical guides to scope, planning, and status for working teams.
- U.S. Digital Service Playbook (playbook.usds.gov) — Free public playbook on delivering projects in understandable, checkable steps.
- Mind Tools (mindtools.com) — Accessible articles on planning, risk, and team leadership skills.
What you earned / what's next — Project Management Skills for Leaders
✅ Project Management Skills for Leaders complete (quiz score 80% or higher): You can tell a project from ongoing work, defend a checkable definition of done, sequence owned steps, spot slippage and risk early, report status without spin, and close with lessons the next project will actually use.
Your certificate
Minister Destiny Testimony Schools Certificate of Completion — Project Management Skills for Leaders
This certificate is presented by Minister Destiny Marie Morgan, Minister
Awarded to: ______________________________ (write your name here after you download — your name is never collected or stored by this school)
Date completed: ______________
Congratulations. You learned leadership as steadiness — clear done, honest status, protected people. Teams remember the leader whose projects end cleanly and whose word about progress could be trusted. — Minister Destiny Marie Morgan
This is a certificate of educational completion from Minister Destiny Testimony Schools. It is not a state license, a government certification, or the original course credential.
What's next: Return to the Certificate Topics for your next Year 1 Foundations topic.
Sources
- Project Management Institute — PMI (pmi.org) — Project definitions and practice concepts.
- Atlassian — Atlassian (atlassian.com) — Team project management guides.
- U.S. Digital Service — USDS (playbook.usds.gov) — Delivery playbook principles.
Course Record — Project Management Skills for Leaders
- Learning outcomes: On completing this unit, the student can:
- distinguish a project from ongoing work and staff each correctly
- write a scope with exclusions and a checkable definition of done
- break work into owned steps and map their dependencies and critical path
- read early slippage signals and respond from the leader's menu instead of hoping
- maintain a short, owned risk list with early-warning signs
- report status without spin, close a project properly, and record lessons learned
- Study time: Approximately 1 hour — an estimate covering reading, activities, and the test. Students move at their own pace.
- Assessment: A 10-question test drawn only from this unit's lesson. 80% or higher passes and earns the unit certificate. Answers are not shown; your score is saved to your student record, and retakes are allowed.
- Level: Certificate Topics — Year 1 (Foundations) · Adult school · working rank on completion path: Freshman → Sophomore.
- Version: Version 1.0 — October 2026.
Minister Destiny Testimony Schools — Adult. Educational information only. Help lines: 911 for emergencies · 988 Suicide & Crisis Lifeline (call/text 988).