This Stakeholder Register Software Development workbook identifies, assesses, and tracks every stakeholder in the ProjectAdm SaaS platform project — from Henry Douglas (PO/Tech Lead/Co-Sponsor) to the 12 beta testers and the ISS payment-gateway integration partner — with the engagement level, influence/interest scores, and communication strategy that Eduardo Montes used to keep the right people informed and the right people engaged throughout all 28 sprints.

What Is a Stakeholder Register?

A Stakeholder Register is a PMBOK 8 output in the Stakeholder Performance Domain that documents all identified stakeholders, their roles, interests, levels of engagement, and interdependencies. It is the foundation of the Stakeholder Engagement Plan — you cannot plan engagement strategy without first knowing who the stakeholders are, what they want, and how much influence they have over the project. The register is a living document: stakeholders join and leave projects, and their interests and influence levels change as the project progresses. In a SaaS development project, the stakeholder landscape is particularly dynamic — beta users who were "unaware" in Sprint 1 become "leading" advocates (or "resistant" critics) by Sprint 20 depending on how well the product addresses their pain points.

What This Stakeholder Register Software Development Includes

The ProjectAdm Stakeholder Register workbook contains three worksheets:

• Stakeholder Inventory — 31 identified stakeholders across 6 categories: Core Team (7), Governance (3), Internal Users (8), External Partners (4), Beta Testers (12, represented as a group), and Regulatory (2); each row includes name/group, role, organization, contact, and date identified
• Assessment Matrix — Power/Interest grid score (1–5 each axis) for all 31 stakeholders; quadrant classification (Manage Closely / Keep Satisfied / Keep Informed / Monitor); current engagement level (Unaware / Resistant / Neutral / Supportive / Leading); desired engagement level; gap analysis (positive gap = needs more engagement, negative gap = over-engaged)
• Engagement Strategy Log — Sprint-by-sprint notes on stakeholder engagement actions: escalations, change requests handled, satisfaction survey results, and engagement level updates; ISS-001 escalation to Henry Douglas documented in Sprint 3; CR-002 (Gantt chart, $4,500 approved) documented in Sprint 8

How Eduardo Montes Used This Stakeholder Register Software Development

Eduardo Montes created the initial Stakeholder Register in Sprint 0 and reviewed it at every Sprint Retrospective. The most critical insight from the register was the gap between Henry Douglas's desired engagement level (Leading) and his actual level in Sprints 3–5 (Supportive) — a gap caused by ISS-001 (AI rate limits) and ISS-002 (MariaDB performance) creating uncertainty about delivery timelines. Eduardo responded by increasing the frequency of one-on-one updates with Henry to weekly (vs. the default biweekly Sprint Review) and providing him with the Schedule Forecasts workbook for direct SPI visibility. By Sprint 8, Henry's engagement level had moved to Leading. The register also flagged the payment gateway integration partner as a high-influence/low-interest stakeholder — correctly predicting that CR-003 (PagSeguro removal) would be straightforward to negotiate once the partner confirmed API deprecation.

How to Use This Stakeholder Register Software Development Document

When building your own Stakeholder Register Software Development, pay attention to the engagement gap column. A stakeholder with a large positive gap (desired: Leading, current: Unaware) is a project risk — they have influence but no commitment. Close the gap before a critical milestone, not after. Also look for stakeholders whose influence is underestimated early in the project: the 12 beta testers in ProjectAdm started as a "Monitor" group (low power, low interest) but became "Keep Informed" by Sprint 18 when their feedback drove 3 acceptance criteria changes in User Stories. Update the register to reflect reality, not wishful thinking.

Ready to create your own stakeholder register? Download the blank Stakeholder Register Template (PMBOK 8).

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