Technical Solution
The Technical Solution sessions will help the team identify the optimal Technical design to allow the system to fulfil the non-functional requirements. Depending on the nature of the project there is likely to be a number of unknowns that will affect the chosen solution. This may result in the team breaking out to undertake a number of POCs or spikes to increase their understanding. Assumptions which have fed into the architectural design can also be linked to project risks that may require mitigation ahead of the delivery stage.
1 day
Key Focus: Tech Design
BA, Tech Lead, Architect, SM/PM
Non Functional Requirements (NFRS)
- NFRs are captured to feed into the architectural solution
- PARRISSS used to group types of non functional requirements – Performance, Accessibility, Responsiveness, Resilience, Integrity, Scalability, Security, Supportability
Candidate Architecture
- Technical architecture of the proposed solution is documented
- Solution based on NFRs identified by the team
- Architecture describes new / changed / deprecated aspects of the current landscape
Risks & POCs / Spikes
- Team brainstorming session to identify risks to the solution, along with ways to mitigate them
- Spikes / POCs are delivered during the course of the inception phase to allow the risk to be addressed ahead of delivery