What are we delivering?
Agree the goal, exclusions, accountable owner and acceptance criteria.
Read the guidePractical playbook
Project management coordinates a defined outcome across scope, dependencies, resources and stakeholders. A realistic plan makes assumptions and decisions visible, then adapts when the evidence changes.
Agree the goal, exclusions, accountable owner and acceptance criteria.
Read the guideSeparate effort from duration and account for uncertainty and dependencies.
Read the guideReview finished work and choose an owned process experiment.
Read the guideA project status report summarizes progress toward an outcome for a stated reporting period. Include completed deliverables, upcoming commitments, risks, changed dates and decisions needed, with an owner for each follow-up.
ExploreA project kickoff aligns the people doing and approving the work on the outcome, scope, roles, constraints and first decisions. Finish with an agreed brief and owned next actions, rather than treating attendance as evidence of alignment.
ExploreScope creep is growth in project work without an explicit agreement about its effect on time, cost or the intended outcome. Manage it by documenting the baseline, recording proposed changes and making the trade-off visible before accepting more work.
ExploreA task describes work to perform; a milestone marks a significant checkpoint or accepted outcome. Use tasks to assign the work and milestones to communicate whether the project has reached an agreed stage.
ExploreA content calendar workflow connects each publishing date to an owned brief, draft, review and release check. Track production status separately from the target date so a scheduled item is not mistaken for a ready item.
ExploreSprint planning selects a realistic slice of work that advances one agreed goal. Start with actual capacity, review dependencies and acceptance criteria, then commit to a coherent set of tasks rather than filling every available hour.
ExploreLead time measures elapsed time from a defined request or commitment to completion. Cycle time measures elapsed time from work starting to completion. The difference commonly includes waiting before active work begins.
ExploreProject estimation makes scope, resource assumptions and uncertainty explicit. Break the work down, estimate comparable units, account for dependencies and review the estimate as evidence improves.
ExploreA project brief defines why the work matters, what will be delivered, who is accountable and how completion will be judged. It creates a reviewable starting agreement before detailed planning begins.
ExploreA sprint retrospective reviews how work happened and selects a small improvement to try next. A useful result is an agreed experiment with an owner, review date and a way to assess whether it helped.
ExploreA task dependency records that one piece of work relies on another task, decision or input. It makes sequencing explicit so people can see what can start, what is blocked and who can resolve the prerequisite.
ExploreFour useful Kanban flow measures are work in progress, throughput, cycle time and work item age. Together they show how much work is active, how much finishes, how long finished work took and how long unfinished work has been active.
ExploreA project handoff transfers responsibility with enough context for the next owner to act. It should include the current state, completion criteria, relevant decisions, open risks and a clear agreement that the recipient accepts ownership.
ExploreEstimate available team hours after leave and focus allocation before committing to sprint work.
ExploreCombine optimistic, most likely and pessimistic estimates into a weighted planning estimate.
ExploreAverage three completed sprints and estimate how many similar sprints a remaining backlog might need.
ExploreBuild a simple labor and non-labor project estimate with an explicit contingency allowance.
ExploreCalculate the share of a defined task set that meets your team's completion criteria.
ExploreEstimate average cycle time from average work in progress and average throughput in a stable workflow.
ExploreCalculate mean cycle time from the total elapsed days of completed work items.
ExploreEstimate remaining working days from outstanding work and an observed daily completion rate.
ExploreCount Monday-to-Friday days between two dates, excluding the start date and including the end date.
ExploreCreate a concise written update covering completed work, next work and blockers.
ExploreDraft a project brief with a goal, deliverables, owner, target date and measurable success criteria.
ExploreTurn retrospective notes into an action plan with an owner, due date and follow-up check.
ExploreGive each next action an owner, a completion condition and a realistic date. My First Task brings tasks, boards, project workflows and issue tracking into one workspace.