This Change Request Software Development document shows how Eduardo Montes formally documented CR-002 — the addition of a Gantt chart view to the ProjectAdm SaaS platform — following a stakeholder request in Sprint 8. This example illustrates how a real change request is structured in a hybrid Agile/Predictive environment: capturing the reason for change, impact on scope, cost, and schedule, the decision-making rationale, and the formal approval trail required by PMBOK 8's Planning Performance Domain.

What Is a Change Request?

A Change Request is a formal proposal to modify any aspect of a project's approved baselines — scope, schedule, cost, quality, or resources. In PMBOK 8, change requests are processed through the integrated change control process and must be evaluated for their impact on all other project baselines before approval or rejection. On Agile projects, minor changes may be handled through backlog refinement, but any change that affects a cost baseline, schedule baseline, or scope baseline requires a formal change request processed by the change control board (CCB). This document is the primary tool for maintaining baseline integrity.

What This Change Request Software Development Includes

This filled example documents CR-002 in full, following the ProjectAdm change control process:

• Change Request ID and Date — CR-002, submitted February 14, 2025 (Sprint 4), approved February 21, 2025; requestor: Henry Douglas (Product Owner); PM: Eduardo Montes
• Change Description — Add a fully interactive Gantt chart view to the ProjectAdm board module, supporting task dependencies, drag-to-reschedule, critical path highlighting, and export to PDF; feature not included in original scope baseline
• Justification — Three enterprise trial users in beta testing (Sprints 3–4) rated absence of Gantt as primary reason to not convert; competitor analysis confirmed Gantt is table-stakes for Professional tier pricing; estimated to increase Professional-to-Enterprise conversion by 15%
• Scope Impact — Adds one new WBS package (1.7 — Gantt Chart Module) with 8 user stories and approximately 3,200 lines of new JavaScript/PHP code; requires new MariaDB table (gantt_dependencies) and updates to 3 existing controllers
• Schedule Impact — +2 sprints (4 weeks) added to WBS package 1.7 delivery; original completion date Feb 14, 2026 unchanged — absorbed by pulling forward dark mode (CR-001) and deferring PagSeguro (CR-003) to free sprint capacity
• Cost Impact — +$4,500: Marcus Webb 60 hours @ $45/hr = $2,700; Julia Chen 40 hours @ $40/hr = $1,600; Lucas Park additional QA 5 hours @ $35/hr = $175; contingency reserve draw: $25 rounding buffer; funded from contingency reserve (net reserve: $37,500 remaining)
• Risk Assessment — Low: team has prior Gantt implementation experience; Medium: MariaDB recursive CTE performance for deep dependency chains (ISS-002 mitigation plan applied)
• Decision — APPROVED by CCB (Eduardo Montes + Henry Douglas) on February 21, 2025; cost baseline updated to $242,500; scope baseline updated with new WBS 1.7

How Eduardo Montes Used This Change Request Software Development

Eduardo Montes used this Change Request Software Development document as the authoritative record for CR-002 throughout the ProjectAdm lifecycle. When the Gantt chart module was delivered in Sprint 12 (June 2025), the approved change request served as the acceptance criteria reference — Lucas Park cross-checked each of the 8 user stories against the CR-002 scope description during QA. The $4,500 cost draw was recorded in the Change Requests Log (CR Log entry #2) and the updated cost baseline was reflected in all subsequent Earned Value calculations. The document was also referenced during the M3 milestone review when Henry Douglas presented the updated financial projections showing the Gantt feature's impact on the Professional tier conversion rate.

How to Use This Change Request Software Development Document

Use this example to understand the level of detail required in a Change Request Software Development document that will hold up under audit. Notice that CR-002 quantifies every impact — hours, cost, sprint allocation — and explicitly documents how the schedule impact was absorbed without extending the project end date. This level of rigor is what distinguishes effective change control from informal scope creep.

Download the Template and Deepen Your Knowledge

Ready to create your own change request? Download the blank Change Request Template (PMBOK 8).

• Download the Change Request Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Change Request 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 Word (.docx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Planning