
Saved by sari
TBM 41/51: Why Goal Cascades are Harmful (and What to Do Instead)
Saved by sari
Architectural goals — for example, desired performance, availability, and security — should be approached by iteratively specifying target conditions at the program level. Following the Principle of Mission, set out a clear vision of the goals of your enterprise architecture without specifying how the goals are to be achieved, and create a context
... See moreclear statement of measurable outcomes, which key stakeholders sign on to at the beginning of the project, can resolve many of these problems early.
Goals should not be about building products or delivering project scope. They should explain why such a thing would be useful. Goals should present the problem to be solved, not the solution. Avoid design constraints in a goal definition.