Skip to main content

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

Hello?

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.

Regards,

Pablo


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.