Discovery typically brings together the project sponsor, product owner, user researchers, business stakeholders, domain experts, and often IT/security leads. We use activities like interviews, service mapping, content inventories, user journeys, and a discovery brief to capture goals and constraints. This team and these artifacts help avoid assuming the solution and set direction for solution architecture.
Public Q&A
Who should be involved in the discovery phase to clarify the problem?
Useful next steps
Use this answer as a practical starting point. Current scope, specifications, compatibility, availability, pricing, timing and next steps should be confirmed directly with Annex where they affect a decision.
Related Topics
