Return to Well-Architected Framework Guide
- Purpose of reviewing an architecture is to identify any critical issues that might need addressing or areas that could be improved
- Outcome of the review is a set of actions that should improve the experience of a customer using the workload
- Team members who build an architecture should use the Well-Architected Framework to continually review their architecture
- Reviews should be applied:
- at key milestones in the product lifecycle
- early on in the design phase to avoid one-way doors
- before the go-live date
- Follow a set of hygiene processes including a Well-Architected review as architecture changes
- Suggested items to facilitate your meetings:
- A meeting room with whiteboards
- Print outs of any diagrams or design notes
- Action list of questions that require out-of-band research to answer
- Common objections to review process can be alleviated by pointing out that:
- Reviews help identify potentially missed issues
- They help develop a playbook to respond to issues that couldn't be addressed before launch
- They don't have to reveal proprietary secrets if they follow the Well-Architected Framework
Top comments (0)