This Product Backlog Software Development document shows the complete, ordered backlog of all 1,200 story points that Henry Douglas (Product Owner) and the ProjectAdm team planned and delivered across 28 sprints. This Excel register captures every user story, epic, acceptance criteria, story point estimate, sprint assignment, and delivery status for the full ProjectAdm SaaS platform — from the Authentication epic through to the AI Suggestions engine and Spanish localization.

What Is a Product Backlog?

A Product Backlog is a PMBOK 8 output in the Planning Performance Domain that represents the ordered list of everything that might be done in the product — user stories, features, bug fixes, technical improvements, and other work items. In Agile environments, the Product Backlog is owned and prioritized by the Product Owner (Henry Douglas on ProjectAdm), refined continuously through backlog grooming sessions, and used as the input to sprint planning. The backlog is a living document — it changes throughout the project as new information emerges, change requests are approved, and issues are resolved.

What This Product Backlog Software Development Includes

The ProjectAdm Product Backlog workbook covers 1,200 story points across 5 epics and 28 sprints:

• Epic 1 — Core Platform (Sprints 1–8, 336 SP) — Authentication (Google OAuth, email/password, SSO stub): 48 SP; Project CRUD + role-based access: 56 SP; Kanban board (drag-and-drop, columns, swimlanes): 120 SP; Team management + invitations: 44 SP; Notifications (email + in-app): 36 SP; Admin panel (user management, billing): 32 SP
• Epic 2 — SaaS Engine (Sprints 9–16, 312 SP) — Multi-tenant data isolation: 48 SP; Subscription management (4 tiers): 64 SP; Stripe integration (checkout, webhooks, ISS-004 fix): 72 SP; PayPal integration: 48 SP; Gantt chart module (CR-002): 80 SP
• Epic 3 — Advanced Features (Sprints 17–24, 360 SP) — Advanced filtering (ISS-002 fix + feature): 96 SP; Dark mode (CR-001): 64 SP; AI suggestions engine (ISS-001 fix + OpenAI): 112 SP; WBS view (CR-004): 56 SP; Spanish localization (ISS-005): 32 SP
• Epic 4 — Quality and Security (Sprints 1–28, distributed, 120 SP) — PHPUnit test suite (321 tests, Lucas Park): 80 SP; Penetration test remediation (Sprint 26): 16 SP; WCAG 2.1 AA accessibility pass: 24 SP
• Epic 5 — Go-Live (Sprints 25–28, 72 SP) — Landing page + documentation: 40 SP; Production deployment + load test: 24 SP; Onboarding flow (5-step, Camila Rocha): 8 SP
• Backlog Metrics — Initial backlog (v1.0, Jan 28, 2025): 1,092 SP; CR additions (CR-001 through CR-004): +108 SP; Total delivered: 1,200 SP in 28 sprints; Average velocity: 42.9 SP/sprint; Sprint with highest velocity: Sprint 22 (48 SP); Sprint with lowest velocity: Sprint 15 (38 SP — ISS-002 impact)
• Backlog Health Indicators — Ready items (3-sprint look-ahead fully groomed): maintained throughout Sprints 6–28; Story size distribution: 1–3 SP (50%), 5–8 SP (38%), 13 SP (12%); No stories >13 SP (all large stories decomposed before sprint planning)

How Eduardo Montes Used This Product Backlog Software Development

While Henry Douglas owned the Product Backlog Software Development as Product Owner, Eduardo Montes used the backlog Excel workbook as the primary velocity tracking and forecasting tool. The sprint assignment column allowed Eduardo to run weekly "what if" scenarios: if velocity dropped to 38 SP/sprint (Sprint 15 low), which features would be at risk? This forecasting kept Eduardo ahead of potential delivery shortfalls rather than reacting to them, enabling the proactive ISS-002 corrective action rather than a last-minute M3 crisis.

How to Use This Product Backlog Software Development Document

When managing your own Product Backlog Software Development register, maintain a "3-sprint look-ahead" of fully refined stories at all times. The ProjectAdm rule — any story that would be sprint-planned within the next 3 sprints must have complete acceptance criteria and story point estimate — prevented sprint planning sessions from being derailed by unrefined backlog items.

Download the Template and Deepen Your Knowledge

Ready to create your own product backlog? Download the blank Product Backlog Template (PMBOK 8).

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