This Schedule Data Software Development workbook documents the supporting information behind the ProjectAdm approved schedule — the durations, dependencies, early/late dates, total float, and free float for every one of the 214 activities that Eduardo Montes planned across 28 two-week sprints, 5 milestone gates, and 12 WBS packages. Schedule Data is the raw dataset that feeds the Project Schedule; without it, the schedule is just a chart with no verifiable basis.

What Is Schedule Data?

Schedule Data is a PMBOK 8 output in the Planning Performance Domain consisting of the supporting information used to describe and control the project schedule. It includes activity attributes, duration estimates, resource assignments, constraints, assumptions, identified risks affecting the schedule, and schedule alternatives. Schedule Data is the audit trail that proves how the approved schedule was derived — reviewers and auditors can trace every planned date back to a documented estimate and a logical dependency. In hybrid projects like ProjectAdm, Schedule Data bridges both worlds: Agile activities are described in story points and sprint capacity terms, while predictive milestones include fixed-constraint dates and dependency types (FS, SS, FF, SF).

What This Schedule Data Software Development Includes

The ProjectAdm Schedule Data workbook contains six structured worksheets:

• Activity List — 214 activities across 12 WBS packages; each row shows WBS code, activity name, predecessor IDs, dependency type, lag/lead days, and responsible team member
• Duration Estimates — Three-point estimates (optimistic/most likely/pessimistic) and the resulting PERT estimate for all predictive-phase activities; story-point-to-hours conversion table for Agile activities
• Early/Late Dates — ES (Early Start), EF (Early Finish), LS (Late Start), LF (Late Finish) calculated by CPM forward and backward passes; computed by Eduardo Montes during Sprint 1 planning
• Float Analysis — Total Float and Free Float for each activity; critical-path activities flagged in red (TF = 0); near-critical activities flagged in yellow (TF ≤ 5 days)
• Resource Assignments — Each activity mapped to one or more team members (Marcus Webb, Julia Chen, Bruno Silva, Camila Rocha, Lucas Park); hours per activity per resource
• Schedule Assumptions and Constraints — 18 documented assumptions (e.g., "MariaDB server provisioned by Jan 20, 2025") and 7 hard constraints (milestone gate dates M1–M5); ISS-002 impact on float documented as a schedule risk

How Eduardo Montes Used This Schedule Data Software Development

Eduardo Montes built the Schedule Data workbook during Sprint 0 (Jan 15–28, 2025) using a bottom-up estimating approach: each team member provided three-point estimates for their assigned activities, which Eduardo then assembled into the CPM network. The critical path ran through the MariaDB schema design → core API development → frontend integration → QA regression chain, totaling 13.5 months with zero float on those activities. When ISS-002 (MariaDB performance degradation) struck in Sprint 5, Eduardo returned to this workbook and recalculated float — confirming that a 3-sprint delay would consume the entire buffer without breaching M2 (Apr 30, 2025), provided the team parallelized frontend work. That float analysis, grounded in the Schedule Data, justified the decision not to trigger a baseline change. By Sprint 20, the team had recovered: SPI = 1.02, confirming that the float management strategy had worked.

How to Use This Schedule Data Software Development Document

When building your own Schedule Data Software Development dataset, invest time in the float analysis tab. Float is perishable — it disappears as the project progresses and risks materialize. Document total float and free float at baseline, then refresh the calculation at each sprint review. Activities that start the project with 10 days of float but lose 2 days per sprint will reach zero float by Sprint 5; early visibility lets you act before the activity lands on the critical path. Also document your schedule assumptions explicitly: the ProjectAdm team's assumption that MariaDB would be provisioned by Jan 20, 2025 proved accurate, but if it had been wrong by a week, the float analysis would have immediately shown the impact.

Ready to create your own schedule data set? Download the blank Schedule Data Template (PMBOK 8).

• Download the Schedule Data Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Schedule Data in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Excel (.xlsx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Planning