CAPM Practice: Demonstrate an understanding of product roadmaps

Technical debt and infrastructure investments belong on the roadmap, framed in business terms: 'Platform modernization to enable faster feature delivery' or 'Database migration required for GDPR compliance.' Hiding them leads to underfunded technical work that eventually creates crises.

**Why not A:** Hiding infrastructure work from stakeholders erodes trust and prevents informed decision-making. Stakeholders need visibility into technical investments to understand trade-offs between new features and platform stability. Transparency about technical debt builds credibility and supports resource allocation discussions.

**Why not B:** Limiting technical debt visibility to internal task boards means it competes poorly for prioritization against customer-facing features. Placing it on the roadmap with clear business impact framing ensures leadership understands the consequences of deferral and can make informed investment decisions.

**Why not C:** Excluding non-customer-facing work from roadmaps creates a false picture of the team's capacity and priorities. Technical debt and infrastructure investments directly affect delivery speed, system reliability, and the ability to build future features. Omitting them leads to unrealistic expectations about feature delivery timelines.