Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

When to Design and Check requirements in scrum?

Last post 05:19 pm August 7, 2017 by Pablo Cruz Navea
2 replies
09:20 am August 3, 2017


In scrum when we should design software architecture ?.

because software architecture can affect the time of develop and estimations

08:31 pm August 3, 2017

Do you think there should ever be a *specific* time for this in an agile way of working, or ought architecture to be emergent?

05:19 pm August 7, 2017

Software architecture is about design and design decisions. Thus, we should be talking about taking decisions to see the software architecture emerge throughout the Sprints. When these decisions are taken? In every Sprint. Each Sprint ends with a piece of working software (Done, Increment) which already has architectural decisions incorporated. Depending on your context (and what the PO has deemed as valuable), you can also end with documentation for software architecture as companion to the working software.

Of course, there is no problem with crafting an initial "big-overall-picture diagram" in the first hours of your first Sprint, but remember that a diagram is only a diagram ;) not a software architecture.