scheduling

name	scheduling
description	Schedule software project work using priorities, estimates, dependencies, capacity, ownership, sprint plans, timelines, and delivery checkpoints. Use when organizing execution order and who does what when.

Purpose

This skill helps turn prioritized and estimated software work into an execution schedule with owners, dates, sequencing, and checkpoints.

Use this skill when:

• Planning sprints
• Assigning work
• Creating delivery timelines
• Sequencing tasks
• Coordinating ownership
• Planning checkpoints and reviews
• Replanning after scope or capacity changes

Inputs

Expected inputs:

• Prioritized work
• Estimates
• Dependencies
• Team capacity
• Owners
• Milestones
• Deadlines
• Review or release constraints

Inputs usually come from prioritization, estimation, and dependency-analysis. If high-level sequencing is still unclear, use roadmapping before scheduling execution.

Scheduling Principles

Always optimize for:

1. Executable sequencing
2. Realistic capacity
3. Clear ownership
4. Early blocker resolution
5. Visible checkpoints

Avoid optimizing solely for:

• Full utilization
• Best-case estimates
• Cosmetic timelines
• Ignoring review queues
• Assigning work without ownership clarity

Process

Step 1: Confirm Planning Constraints

Determine:

• Planning horizon
• Team capacity
• Deadlines
• Milestones
• Availability
• Review windows
• Release constraints

Flag impossible combinations of scope, capacity, and date.

---

Step 2: Sequence Work

Order work by:

• Priority
• Dependency chain
• Risk
• Owner availability
• Feedback needs
• Release readiness

Schedule blockers and critical-path work early.

---

Step 3: Assign Ownership

For each work item, define:

• Owner
• Start target
• Completion target
• Dependencies
• Review needs
• Checkpoint

Avoid assigning ownerless work to a timeline.

---

Step 4: Produce Schedule

Generate:

• Sprint or timeline plan
• Owner assignments
• Critical path
• Checkpoints
• Risks
• Replanning triggers

Anti-Patterns

Avoid:

• Scheduling before dependencies are understood
• Filling every person to 100%
• Ignoring review, QA, and release overhead
• Assigning work to unavailable owners
• Treating estimates as commitments
• Hiding impossible deadlines

Reviewer Checklist

Before finalizing a schedule:

• Are owners clear?
• Are dependencies sequenced correctly?
• Is capacity realistic?
• Are review and release steps included?
• Are replanning triggers visible?

Escalation Guidance

Escalate when:

• Capacity cannot meet deadlines
• Critical dependencies are unresolved
• Required owners are unavailable
• Scope must be reduced to fit the timeline
• Stakeholders require commitments beyond estimate confidence

Example

Input:

• Prioritized checklist work
• Estimate: 2-3 weeks
• Dependency: API contract before frontend integration

Expected schedule:

1. Week 1: Database fields and API contract
2. Week 2: API implementation and frontend checklist
3. Week 3: Analytics, QA, rollout, and support review

Recommended next step:

• Execute the schedule and use measured outcomes to revisit goal-setting.