This Statement of Work Software Development document shows how Eduardo Montes defined the complete scope of work for the ProjectAdm SaaS platform development engagement — capturing what the team would deliver, the standards they would work to, the payment and milestone structure, and the governance obligations that governed the development relationship between the project team and ProjectAdm International. This SOW served as both a planning tool and a contractual reference point for the internal development engagement.

What Is a Statement of Work?

A Statement of Work (SOW) is a PMBOK 8 output in the Planning Performance Domain that describes in narrative form the products, services, or results to be supplied by a project. It typically includes a description of the business need, the product scope description, the location and conditions of work, the schedule of work, the applicable standards, and any acceptance criteria. While commonly used in procurement contexts, the SOW is equally valuable for internal projects as the authoritative description of what the project team has committed to deliver and under what conditions.

What This Statement of Work Software Development Includes

The ProjectAdm SOW defines the complete internal development engagement:

• Business Need — ProjectAdm International requires a production-ready multi-tenant SaaS project management platform to replace spreadsheet-based tracking (estimated $180K/year productivity loss), capture recurring SaaS revenue, and provide a white-label offering for enterprise clients by Q1 2026
• Product Scope Description — Full-stack SaaS: PHP 8.1 + CodeIgniter 4.4.4 backend, MariaDB (51 tables), HTML5/CSS3/vanilla JavaScript frontend; features: Kanban, Scrum sprint management, Gantt chart, WBS view, AI task suggestions, multi-tenant billing (Stripe + PayPal), SSO for Enterprise; target: 152,400 LOC, 65 controllers, 50 models, 321 PHPUnit tests
• Schedule of Work — January 15, 2025 – February 28, 2026; 28 two-week sprints; work performed remotely by 7-person team; daily standups 9am BRT; sprint reviews biweekly Friday afternoons; team availability: 80% capacity
• Applicable Standards — PMBOK 8th Edition governance; WCAG 2.1 AA accessibility; OWASP Top 10 security; LGPD compliance; PHP Standards Recommendations (PSR-1, PSR-4, PSR-12); GitFlow branching; mandatory code review before merge
• Milestone Payment Schedule — M1 (Jan 31, 2025): $52,000; M2 (Apr 30, 2025): $68,000; M3 (Jul 31, 2025): $72,000; M4 (Oct 31, 2025): $64,000; M5 (Feb 28, 2026): $24,000; contingency $42,000 held separately
• Acceptance Criteria — Production on AWS multi-region; 100% PHPUnit pass rate (321 tests); load test: 500 concurrent users <300ms avg response; 0 critical security findings; all 4 billing tiers functional; WCAG 2.1 AA compliance; formal acceptance signed by Henry Douglas
• Deliverables List — 12 WBS packages; all project management documents (40+ outputs); source code in Git with documentation; deployment runbook; API documentation (Swagger, 65 endpoints); user manual (English + Portuguese)
• Intellectual Property — All code, documentation, and designs developed under this SOW are the exclusive property of ProjectAdm International upon milestone payment

How Eduardo Montes Used This Statement of Work Software Development

Eduardo Montes used this Statement of Work Software Development document as the primary reference when evaluating whether informal requests from Henry Douglas constituted scope additions requiring a change request. The SOW's deliverables list provided the objective boundary: when Henry Douglas requested the Slack integration verbally in Sprint 16, Eduardo referenced the SOW, confirmed it was not included, and initiated the change request evaluation process. The milestone payment structure also aligned the team's financial incentives with delivery milestones — milestone bonuses were paid within 5 days of each acceptance, reinforcing the delivery rhythm throughout all 28 sprints.

How to Use This Statement of Work Software Development Document

When writing your own Statement of Work Software Development document, make the acceptance criteria section specific and measurable. The ProjectAdm SOW's criteria (500 concurrent users at <300ms, 100% PHPUnit pass, 0 critical security findings) eliminated all subjectivity from the final acceptance decision. Vague acceptance criteria are the most common cause of go-live disputes on software projects.

Download the Template and Deepen Your Knowledge

Ready to create your own statement of work? Download the blank Statement of Work Template (PMBOK 8).

• Download the Statement of Work Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Statement of Work 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