technical-planning

Create a 3-12 month technical roadmap aligned with business strategy.

Estimate a feature or epic and surface hidden risks.

Identify and visualize dependencies across teams and projects to prevent blocked work.

Run a complete sprint planning process from capacity to commitment.

Model team capacity across quarters, accounting for hiring, attrition, and project work. Use when forecasting resource availability for roadmaps.

Identify and visualize dependencies between teams, systems, and work items to prevent blocked work. Use when planning cross-team initiatives.

Apply evidence-based estimation methods (story points, t-shirt sizing, planning poker) to reduce uncertainty. Use when sizing work for sprints or releases.

Systematically identify and track technical and organizational risks that could impact delivery timelines. Use when planning significant initiatives.

Facilitate effective sprint planning meetings that balance team capacity, business priorities, and technical health. Use when preparing for sprint planning.

Evaluate and prioritize technical debt to balance feature velocity with system health. Use when deciding what debt to address in upcoming sprints.

Build multi-quarter technical roadmaps aligned with business goals, clearly showing strategic investments, trade-offs, and dependencies. Use when planning longer-term technical direction, communicating with stakeholders, or aligning engineering capacity with business priorities.

Track and interpret sprint velocity to forecast capacity, identify bottlenecks, and improve planning accuracy. Use when analyzing team productivity trends.

Decompose complex initiatives into manageable work items with clear ownership and milestones. Use when planning large features or multi-team projects.