Akar Sumset
Jul 22, 2017 · 1 min read

Hi Jordan,

Thanks for the response since it gave me the chance to emphasize something, obviously, not emphasized well enough in the article.

I am of the same mindset, too. This is why I wrote:

Involve colleagues early on and listen to their feedbacks, sincerely. In order to get them engaged from the beginning. This will help you create a much better, spotless Definition.

and

The gist is this: Purpose of definition is not to get developers implement exactly what’s described in it but to get the whole company collaborate based on the same knowledge and work towards the same goals.

I see the word “you” is misleading. However, the article addresses whoever takes part in this complex process of definition. The Overview part is possibly created by a product manager while the task flows is created by a business analyst and test cases created by the whole Scrum team… So, when I say “you” I mean whoever contributes to the definition, not just one person. I hope this clarifies my intent.

On top of all that, my experience shows me that there should be someone or some people who oversee the whole thing and make sure the team comes up with a coherent, consistent and goal oriented (regarding both user and company goals) definition. Otherwise, it’s very easy to drift away from goals and — mostly unconsciously, let our preconceptions takeover the product.

Akar Sumset

Written by

Continuously brainstorming… Founder of www.invertiv.com