Project & Development
Project Management for Beginners: Plan Board for Goal, Scope, Schedule, Team, and Risks
Beginner | 2 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Beginner: No technical terms. Just answer the whiteboard's questions, following the examples, and it takes shape.
Someone leading a small project for the first time uses this project management template for beginners to set the goal, scope, schedule, team, and risks of the plan on one board. The left page of the whiteboard holds the project charter, the five process groups from initiating to closing, a stakeholder map of influence by interest, and three frames for scope, team, and risks; the right page holds a 4 by 4 milestone table, a risk quadrant of likelihood by impact, and three frames on the weekly check, delays, and closing. The task board has five columns, from planning and preparing to in progress, in review, and done, and starts with 4 parent tasks and 12 subtasks, all not started. Starting work without knowing that a project plan follows a set order leaves gaps, so the five PMBOK process groups run through the board as its flow. It suits small projects that finish in a few weeks to a few months, such as an in-house event or a trial of a new service.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Project Management Plan Board for Beginners
How to use: (1) Write the purpose, goal, deadline, and budget on one sheet (board 1, the charter) → (2) Sort the people by influence and interest and decide how to involve them (board 3, the stakeholder map) → (3) Decide what is in and out of scope and who owns what → (4) List the risks, put the milestones in the table, and sort the risks in the quadrant → (5) Check progress once a week
1. Project charter (one sheet you fill in before you start: purpose, goal, deadline, budget)
- Purpose (why you are doing it) e.g. give new hires more contact with each other so they have someone to ask once they are placed
- Goal (the state when it is over) e.g. hold an in-house social on Oct 20 with 60 people and a satisfaction score of 4.0 or higher
- Deadline and budget e.g. event day Oct 20, prep starts Sept 8. Cap of $1,000 (venue 350, catering 500, supplies 150)
- Team (who is responsible) e.g. you are the lead, the host keeps the overall schedule, the venue owner books and sets up, the note taker writes the minutes Lead: ____ / Host: ____ / Venue: ____ / Notes: ____
2. The five project stages (initiating, planning, executing, monitoring and controlling, closing)
- 1. Initiating What you do here: set the purpose, the goal, and the lead, then list the people in 3 and get them to agree. e.g. show the one-page charter to your manager and get approval.
- 2. Planning What you do here: decide the work, the dates, the team, the costs, and the risks. e.g. set four milestones and write the owner and the check for each.
- 3. Executing What you do here: work the plan, send the requests and the orders. e.g. book the venue and send the invitation to everyone.
- 4. Monitoring and controlling What you do here: once a week, look at the gap between plan and reality and act on it. e.g. if you are more than 3 days behind, revisit the scope or the dates.
- 5. Closing What you do here: confirm the results, close the payments and the records, and hand over. e.g. leave the survey and the real costs on one sheet.
3. Stakeholder map (a map of the people around you: influence by interest tells you how far to involve each one)
Vertical axis: High influence (top = can approve or stop it) / Horizontal axis: High interest (right = cares a lot)
- Keep them satisfied Report only what is decided and do not bring them the details. Always tell them the outcome so no bad feeling builds up. e.g. tell the head of admin only the venue and the budget decision
- Manage closely Invite them to the weekly check and get them to agree to the one-page plan. Explain in person at every milestone. The team in 5 is who does what inside your team; 3 is how you deal with each person, including outside it. e.g. your manager and the admin contact who lends the venue
- Monitor (minimum effort) Spend no effort, only keep an eye out. If their interest grows, move them right to keep informed; if it turns out they can block you, move them up to keep satisfied. e.g. another team with nothing to do on the day
- Keep them informed They care a lot, so tell them what is decided on a regular basis without being asked. Answer their questions quickly. e.g. send the new hires who will attend the invitation and the run of the day in advance
4. Scope (in and out)
- In e.g. booking the venue, sending invitations, hosting on the day, the survey
- Out e.g. making souvenirs, filming and editing a video
- Writing the out list is what lets you turn down a late request
- When you do add something, decide together whether the dates or the budget moves
5. Team (who owns what)
- One lead only. When a call has to be made, this person makes it
- e.g. the host keeps the overall schedule, the venue owner books and sets up, the note taker writes the minutes
- When you ask someone, hand them what to do and by when in writing
6. Risks (what would hurt)
- e.g. fewer than 30 people sign up
- e.g. the venue cannot be booked, or an owner is away on the day
- Post them as they come to mind and sort them in the quadrant in 8
7. Milestone table (the four rows below are an example, so replace the dates and content with your own. Monitoring and controlling is watched by the weekly check in 9)
| When | What is finished | Who | How to check | |
|---|---|---|---|---|
| Initiating | Sept 8 | Charter approved by manager | Lead | Save the reply |
| Planning | Sept 15 | Dates, team, budget fixed | Lead and host | Read it on this board |
| Executing | Oct 10 | Venue booked, invitations sent | Venue owner | Booking note and send list |
| Closing | Oct 27 | Survey and real costs in | Note taker | One-page report to manager |
8. Sorting the risks (how likely by how big the impact)
Vertical axis: Size of impact (top = large) / Horizontal axis: Likelihood (right = more likely)
- Prepare an answer Rare, but it stops everything when it happens. Write one line on who you call and what you do. e.g. a power cut on the day
- Act on it now Build the countermeasure into the plan. Put it on the task board with an owner and a date. e.g. not enough sign-ups, so send the invitation twice
- Nothing for now Just keep a note. Move it up if the weekly check shows things have changed. e.g. some of the supplies do not arrive
- Fix it when it hits Assume it will happen, agree the steps, and spend no time preventing it. e.g. a queue at the desk, so open a second line
9. How the weekly check works (15 minutes)
- Same weekday and time every week e.g. Mondays from 9:30 for 15 minutes
- Only three things to look at. Delays, troubles, this week's work
- Compare what is finished in the milestone table with what really happened
- Write what you decided on the board, never leave it spoken
10. Deciding when you are late
- Once you are more than 3 days behind, the lead decides which moves, the scope, the dates, or the people
- e.g. the invitation slipped, so souvenirs move to the out list to buy time
- The sooner you say it, the more options you still have
11. What to leave behind at the end
- e.g. 60 attendees, satisfaction 4.2, cost $870 (under budget)
- Write three lines on what worked and three on what you would change
- Make it so the next owner can read it and run the same steps
Task board contents
Planning 16 items
Write the charter
The work that sets the base of the project. Once the purpose and the goal fit on one sheet, every later decision stops wobbling.
Purpose in 1 line
Write why you are doing this in one line. Done when everyone involved reads it and gives the same reason.
Set a number goal
Write the state at the end as a number. Like the example, use headcount or a satisfaction score, something you can measure.
Set date and budget
Set the start date, the end date, and the cap you may spend, write the breakdown, and get your manager to approve it.
Set scope and team
Draw the line between what you will and will not do, and decide who owns what. This is what lets you turn down extra requests later.
List what you skip
Write down the work you are not taking on this time. With that written, a late request gets an answer about dates or budget instead of a yes.
Assign the roles
Pick one lead, then hand out hosting, booking, and note taking. Make clear who decides when a call has to be made.
Get people to agree
Place the people on the stakeholder map in 3 and decide how to involve each of them, then show the one-page plan to your manager and helpers and get scope and team agreed. Done when the agreement is written down.
Add dates and risks
Make the milestones and the shaky parts visible before you start. Planning ends here.
Set 4 milestones
For initiating, planning, executing, and closing, decide when and what is finished, and write it in the milestone table. Monitoring and controlling is not a milestone but the weekly check, so it lives in 9.
Write how to check
Write how you will tell that each milestone is really finished. Make it something a document or a record can prove.
Sort out the risks
List what would hurt if it happened and place each one in the likelihood by impact quadrant. Decide which ones you act on now.
Run it every week
Do not stop at writing the plan. Check progress once a week and keep a record when it closes.
Do the weekly check
Same time every week, 15 minutes on delays, troubles, and this week's work, and write what you decided on the board.
Flag delays early
Once you are more than 3 days behind, ask the lead to decide which one moves, the scope, the dates, or the people.
Write the closeout
Put the results, the money actually spent, and what you would do differently on one sheet. Make it usable by whoever runs the next one.
