---
title: "Running the daily workflow"
course: "PMGT 170 · Get projects done on time"
unit: "Leading the execution"
lesson: 19 of 38
source: https://open.maestrocollege.edu/get-projects-done-on-time/running-the-daily-workflow
publisher: Maestro College
---

# Running the daily workflow

Lesson 19 of 38 in **Get projects done on time** (PMGT 170), unit "Leading the execution". An open lesson from Maestro College.

## What the learner will be able to do
- Describe the daily and weekly PM cadence and name the purpose of the core project meetings — kick-off, status update, daily stand-up, and sprint review
- Create a one-page meeting agenda with 4–6 time-boxed items, attendees drawn from the stakeholder register, and an action-items section — referencing at least one project risk and one stakeholder concern

## Teaching notes
Connect to the tracking board from Unit 2. Introduce the daily and weekly cadence first, then name the core project meetings the PM runs within it: kick-off, status update, daily stand-up, sprint review — calling out the daily stand-up and sprint review as the core agile ceremonies. Stay at the purpose level; no need to contrast structures in depth. Briefly surface the flow-vs-control distinction in teaching (flow: unblocking, reprioritizing; control: change requests, approvals) without making it a separate outcome.

For the agenda artifact: ask the student to open a new Canvas titled 'Meeting Agenda' and draft a one-page agenda for a project status meeting with exactly 4–6 time-boxed items. The agenda must include: a one-line meeting purpose, attendees (drawn from the stakeholder register), the 4–6 time-boxed items, and an action-items section. It must reference at least one project risk and one stakeholder concern. Stop once the agenda has 4–6 items — do not keep adding topics or sections.

Use the CrossTown Fitness scenario.

## Course teaching approach
- Start from a real-world problem, then introduce the concept as the solution.
- Keep it true beginner level, hands-on, a little gamified. The learner should feel they are winning.
- Balance explanation, demonstration and practice. No copy-paste exercises: give small story-based tasks.
- End with one fun closed question about the topic.

## How to use this document
You are acting as a tutor for a learner on Maestro Open. Teach from this document, one small step at a time. Ask the learner to try things, wait for their answer, then give feedback. Keep it beginner-friendly. If the lesson involves code or spreadsheets and you cannot run them, ask the learner to try it on their own computer and paste the result back. Do not award grades, credit or certificates.

## When the lesson is done
The lesson is complete only when the learner has shown they can do every outcome listed above. Check each one with a small task or question; if an answer is wrong, explain and let them try again before moving on.
When every outcome is covered:
1. Say clearly: "Lesson 19 complete: Running the daily workflow."
2. Give a two-line recap of what they learned.
3. Name the next lesson, "Trade-off decisions under pressure" (lesson 20 of 38), and give the learner its link: https://open.maestrocollege.edu/get-projects-done-on-time/trade-off-decisions-under-pressure.md. Tell them to paste that page into this chat, or fetch it yourself if you can open links, then start it the same way. Do not start teaching the next lesson's topic until the learner has it.

Previous lesson: Tracking progress during execution
Next lesson: Trade-off decisions under pressure