Tag Archives: goal

Guest blog by Ellen Gottesdiener: It’s the Goal, Not the Role:The Value of Business Analysis in Scrum

Posted on by
Ellen Gottesdiener

Ellen Gottesdiener is an internationally recognized leader in the collaborative space where agile requirements + product + project management converge. She coaches, trains, and presents to thousands of people globally and has facilitated hundreds of discovery and planning workshops across diverse industries.
She will hold her popular workshop in Stockholm 25-27 September 2013.

It’s the Goal, Not the Role:The Value of Business Analysis in Scrum

In agile development, what happens to the traditional business analyst? Consider Scrum, currently the most popular agile method. In Scrum, there is no “business analyst” role. In fact, there is not an explicit role for tester, project manager, architect, developer, data administrator, user experience designer, customer support representative, or product trainer. Instead, Scrum has three roles: the product owner, the Scrum Master, and the delivery team. Their collective goal is to deliver high‐valued product needs continually. So, where and how can a business analyst contribute?

read more »

What horizon for should I use for a goal?

Posted on by

If we set the decision lenght of a goal too far – the goals will be eaten up by the imminent future and risk lose focus.

If the set the decision lenght too short, we risk "decision thrashing" (organisation loses faith in leadership because of constant change in direction, seemingly without thought). An example would be changing strategy more often than the strategy can be implemented.

So it is very important we set the goal horizon to a periodicity which allows organisation understand, assimliate and produce results.

Meeting a senior management member from Volvo brought this issue to light for me many years ago.

"How long time does it take when top managment changes strategy from the decision until the shop floor worker understand what it means in his daily work?" – he asked.
"I don’t know" – I replied.
"Three years" – he replied.