A project landscape is the surrounding field of current and planned initiatives, shared capacity, dependencies, platforms, data, and integration points that changes what an architectural decision can responsibly be. An apparently elegant design may become wasteful or risky when another initiative will soon alter the surrounding system, compete for the same team, or replace an integration point. section 2.0
Assess the landscape before committing to a platform, pattern, deployment model, or technology:
- Identify current and upcoming initiatives that could change scope, capacity, or integration needs. section 2.6
- Check whether projects compete for the same teams, platforms, data, or integration points. section 2.0
- Prefer a simpler temporary design when a related initiative is likely to change the surrounding system, while avoiding assumptions that make future change expensive. section 2.0 section 2.6
Internal reporting capability
Several departments need reliable operational reports, but no new strategic data platform is planned. Because usage is modest, reporting windows are predictable, and one small team will own the system, a well-structured application with scheduled refreshes, a managed relational database, basic observability, and clear ownership is more responsible than a distributed architecture with event streams, separate read models, premium database tiers, and high-availability infrastructure. section 2.6
Table 2.3 Project forces and corresponding pressure levels
|
Force
|
Low
pressure
|
Medium
pressure
|
High
pressure
|
|
Time
|
Flexible
time
|
Delivery
date matters but allows trade-offs
|
Deadline
dominates the architecture
|
|
Cost
|
Budget
supports managed services and resilience
|
Cost needs
active control
|
Cost limits
architecture options
|
|
Team
capability
|
Team has
relevant experience
|
Team can
learn with support
|
Team cannot
safely own the proposed solution
|
|
Risk tolerance
|
Experiments
are acceptable
|
Some
uncertainty is acceptable
|
Failure,
instability, or compliance exposure is unacceptable
|
|
Ownership
|
Clear
long-term owner exists
|
Ownership
is shared but coordinated
|
Ownership
is unclear or externalized
|
|
Project
landscape
|
No major
related initiatives affect the decision
|
Related
initiatives may change scope, capacity, or integration needs
|
Competing
or upcoming initiatives make the current design temporary, risky, or
capacity-constrained
|
Use the pressure-level table to compare whether the project landscape creates low, medium, or high pressure through related initiatives, competing capacity, or temporary design conditions. section 2.6
