sprint-planning

To plan a sprint with multi-agent review, you provide target sprint goals, requirements, and risk inputs. The workflow runs PM-led prioritization and a technical table with Solution Architect, Dev Teams, and Security Auditor roles to output a draft sprint roadmap.

A technical table is a multi-agent review phase where Solution Architect, Spec Analyst, Dev Teams, Senior Test Engineer, and Security Auditor evaluate candidate features. They negotiate scope adjustments, split tasks, or defer blockers to ensure an achievable sprint roadmap.

Feature prioritization for a software project roadmap involves assessing business value, dependencies, risk, and effort for each candidate feature. The PM ensures every feature has a success metric before the multi-agent technical table reviews technical feasibility.

Sprint planning requires target sprint goals, a requirements list, previous plan details, lessons learned, and risk inputs. These artifacts drive the PM analysis and multi-agent review to produce the prioritized feature set and sprint roadmap draft.

Yes, sprint planning handles cross-team coordination and ADR alignment by applying a multi-agent technical table. Solution Architect, Backend, Frontend, and DB Dev Teams collaborate to negotiate scope and align the generated roadmap with architecture decisions.

Reviewing lessons learned when planning the next sprint involves identifying what didn't work and capturing improvement actions in Phase 0. These findings are shared during the technical table to inform risk management and scope negotiation.