Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Current-state architecture map of the system
Most teams carry the architecture in two or three heads, and the diagram on the wiki shows the system as it was planned eighteen months ago. Drawing a context diagram and a container diagram of what actually runs in production today gives every later decision in this area a shared starting point and shows the surprises early: the cron job nobody owns, the second database, the service that calls back into its caller.
First tasks
- List every deployable unit from the deployment configuration or cloud console
- Sketch the context diagram with users and external systems on one page
- Draw the container diagram with data stores and protocols on each arrow
- Walk the diagrams with two colleagues and mark every disputed arrow
- Commit the diagrams to the repository with the date drawn
Ranked quality attributes for the system
Every design choice trades one quality for another, and a team that has not ranked availability, latency, cost, security and ease of change will argue the same trade-off from scratch every sprint. Agreeing a ranked top five, each with a number attached where one is real, turns those arguments into a short check against something already written down.
First tasks
- Ask five colleagues to name the quality they would protect above all others
- Merge the answers into a single list of candidate attributes
- Run a forced-ranking session with product and engineering leads
- Attach a measurable target to each of the top five attributes
- Publish the ranked list at the top of the architecture page
Architectural constraints and drivers register
Constraints are the decisions already made for you: the cloud provider the company signed with, the language the team knows, the regulator's rules on where data lives, the launch date marketing announced. Writing them down separately from preferences stops the team designing an ideal system that cannot be built, and makes it obvious when a constraint has quietly expired.
First tasks
- Write down every rule the system must follow that the team did not choose
- Sort the list into technical, organisational, regulatory and commercial groups
- Mark each constraint fixed or negotiable and name who could change it
- Confirm the three most limiting constraints with their owners