How to Build Your First Project Plan with Free Training

A project plan is more than a list of things to finish. It connects a useful outcome to the work, people and decisions needed to reach it. If you are exploring project coordination or moving toward project management, you can practice those connections before you have the job title.

Start with a small fictional project. Write a plan another person could question. Then revise it when a constraint changes. This gives you something more concrete to discuss than a list of terms you recognize.

The exercise below pairs with READY’s free Project Management Foundations course. Its public outline covers outcomes, scope, stakeholders, scheduling, risks, changes, delivery and handover. The course is independent READY learning, not an official Google or Coursera course or credential. A free READY account is required for the guided learning experience.

1. Choose an outcome before choosing tasks

Imagine a fictional neighborhood organization planning a job-search workshop. It wants participants to leave with a clearer next step. “Run a workshop” describes an activity; it does not tell you whether the workshop helped.

For this exercise, propose the following outcome: by the end of one workshop, at least 16 of 20 participants can write one specific job-search action and identify a relevant resource. These numbers are invented practice assumptions, not READY results or a benchmark.

The workshop organizer owns the decision to accept that target. The facilitator can collect voluntary, anonymous exit responses to check it. Attendance alone is not the outcome measure. Nor does a useful exit response prove that anyone later found employment.

In your own plan, write three lines: who should benefit, what should change, and how you would check the change. If you cannot name the evidence, narrow the outcome before expanding the task list.

2. Make the boundary visible

For the fictional workshop, include a session outline, a verified resource list, registration instructions, an accessible room arrangement and an exit question. Exclude individual resume rewriting, recruitment services and promises of interviews or jobs.

That boundary protects the quality of the work. It also makes a later request easier to discuss. If someone asks for one-to-one coaching, you can explain that it is additional work rather than quietly absorbing it into the original plan.

Write an acceptance condition for each important deliverable. “Resource list complete” is vague. “Every link checked, access requirements stated, and the facilitator has reviewed the list” is observable. It still does not imply an external organization endorses the workshop.

3. Connect tasks through dependencies

Use working days for this fictional schedule. Assume one task starts only after its prerequisites finish, and that different people can perform parallel tasks without a capacity conflict:

• Confirm the audience and outcome: 1 day.
• Draft the session outline after that confirmation: 2 days.
• Confirm the room and accessibility arrangements after that confirmation: 1 day.
• Publish the invitation after the outline and room are ready: 1 day.
• Allow registration after the invitation: 3 days.
• Rehearse after the outline is ready: 1 day.
• Hold the workshop after registration and rehearsal are complete.

Under these assumptions, the earliest readiness point is the end of working day 7. The sequence is 1 day for confirmation, 2 for the outline, 1 for the invitation and 3 for registration. The room and rehearsal can finish within that window. Adding every task duration would give 9 days, but that would incorrectly treat all work as sequential.

Now test the assumptions. If the same person must handle the outline and room arrangements, the parallel plan may be unrealistic. If room confirmation takes four days instead of one, the invitation waits and readiness moves to the end of working day 9. Write the dependency that changed; do not simply replace the date without an explanation.

4. Give risks an owner and a response

A risk is a possible future problem. An issue is a problem already happening. Keeping them separate helps a team respond without exaggerating certainty.

Example risk: the proposed room may not meet an attendee’s access needs. Assign an owner to confirm requirements and the venue’s arrangements before invitations go out. The response is not “monitor accessibility.” It is a specific check with a decision point and an alternative if the room is unsuitable.

Example issue: the confirmed room becomes unavailable. Record the fact, the people affected and the next decision. Do not keep reporting the original venue as confirmed while someone informally searches for a replacement.

Choose three realistic risks for your plan. For each, write a trigger, an owner, an action and the evidence that would show the action was completed. Avoid treating a completed action as proof that all risk has disappeared.

5. Test a change without rewriting history

Suppose the organizer requests an additional interview-practice segment. Assess what it changes: facilitator preparation, workshop duration, participant expectations and the rehearsal. Offer bounded options, such as replacing an existing segment or running a separate later session.

Label the new segment “requested” until the responsible person decides. Preserve the original plan alongside the proposed change so another person can understand the tradeoff. A recommendation is not an approval.

Use READY’s change-request impact practice for another exercise in comparing scope, capacity and schedule. Then use the scope-change communication resource to practice explaining an agreed decision to different audiences. Read each resource’s access and self-review instructions; do not assume a written exercise is automatically saved or graded.

6. Finish with a handover, not just a completion label

At the fictional workshop’s close, record which deliverables were accepted, what the exit responses showed, what remains unresolved and who owns the next action. If only 12 of 20 participants submitted a response, report that coverage. Do not turn 12 responses into a claim about all 20 participants.

Keep your sample compact: one page for the plan, one dependency sketch and one change note. Label it “fictional practice project.” Explain the assumptions you made, the choice you changed and what you would need to verify in a real setting. Do not present the exercise as employment history, client work or independently reviewed competence.

Before you move on, check your work

• Is the outcome different from merely finishing the activity?
• Can someone see what is included and excluded?
• Does the schedule account for dependencies and people’s capacity?
• Are requested changes separate from approved decisions?
• Does every unresolved item have an owner and next action?
• Are the example and any results clearly labeled fictional?

You do not need a more elaborate template to begin. You need a small plan whose reasoning is visible. Explore Project Management Foundations, choose the module that addresses your weakest part, and revise your example after the lesson. For other directions, browse the READY Free Training catalog.

This exercise is a learning aid. Completing it does not award a third-party credential, establish READYScore certification or guarantee an employment outcome.