The collection of decisions about how a system will be built – from Grady Booch in the early 80’s.
If the Team was doing some serious exploratory work like architecture or analysis, maybe brainstorming sessions with a few SMEs would be appropriate.
There is always a balance between prioritizing purely on Business Value and prioritizing based on Architectural Significance. The Team is usually doing both types throughout the project, with the balance shifting from architecture-heavy Sprints to business-value-heavy Sprints as the Team moves through a release.
Cite This Term
"Architecture." ScrumDictionary.com. AccessedOct 26, 2020.https://scrumdictionary.com/term/architecture/.