Theory on requirement's complexity

Last post 08:40 pm January 22, 2018 by Ian Mitchell

1 reply

11:27 am January 20, 2018

Hi all,

Following Gunther Verheyen statements on complexity (Sprint Pocket Guide, pp 54) may one lead to the conclusion that the requirement's complexity might have an impact on the outcome of a sprint.

In my understanding this shouldn't be, since requirements should be clearly defined and be sliced into appropriate parts to be manageable.

What is your opinion?

Ian Mitchell

08:40 pm January 22, 2018

You can slice and dice a requirement as much as you like, but while that may help it to become more manageable, you won’t actually bring any complexity under control until you have empirical evidence of having done so through delivery.

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.