« Return to Thread: Top-down User Stories
Re: Top-down User Stories
by Roman Pichler
::
Rate this Message:
Hi Jana,
I suggest asking the product manager to be the (chief) product owner. The individual currently assigned to the product owner role may work with the (chief) product owner in a product owner team. As others have pointed out, the entire Scrum team, product owner, team and ScrumMaster should discover and describe stories collaboratively, for instance in form of requirements workshops. There is nothing wrong with deriving stories form themes. The opposite is true: I have found it to be beneficial. Jeff's user story mapping technique follows a similar approach, for instance.
You may find the description of the product owner role in my upcoming book helpful: www.mikecohnsignatureseries.com/books/agile-product-management.
Good luck,
Roman
--- In agile-usability@..., Jana Jecmen <jana.jecmen@...> wrote:
>
> Hi All,
>
> My company is developing the strategy for going Agile. Here is how we plan
> to maintain the Backlog:
>
> - product management should specify a "theme",
> - product owner should write User Stories for it,
> - developers should estimate them and eventually split them into tasks.
>
> This strategy is believed to give us a framework to stay on track and to
> deliver what product management wants.
>
> Did anybody apply a similar top-down approach in practice?
>
> I like this strategy, but I have a nagging suspicion that this is not an
> Agile methodology. Shouldn't the User Stories be created in a bottom-up
> fashion in Agile?
>
> I would appreciate your comments. Thanks,
>
> Jana
>
I suggest asking the product manager to be the (chief) product owner. The individual currently assigned to the product owner role may work with the (chief) product owner in a product owner team. As others have pointed out, the entire Scrum team, product owner, team and ScrumMaster should discover and describe stories collaboratively, for instance in form of requirements workshops. There is nothing wrong with deriving stories form themes. The opposite is true: I have found it to be beneficial. Jeff's user story mapping technique follows a similar approach, for instance.
You may find the description of the product owner role in my upcoming book helpful: www.mikecohnsignatureseries.com/books/agile-product-management.
Good luck,
Roman
--- In agile-usability@..., Jana Jecmen <jana.jecmen@...> wrote:
>
> Hi All,
>
> My company is developing the strategy for going Agile. Here is how we plan
> to maintain the Backlog:
>
> - product management should specify a "theme",
> - product owner should write User Stories for it,
> - developers should estimate them and eventually split them into tasks.
>
> This strategy is believed to give us a framework to stay on track and to
> deliver what product management wants.
>
> Did anybody apply a similar top-down approach in practice?
>
> I like this strategy, but I have a nagging suspicion that this is not an
> Agile methodology. Shouldn't the User Stories be created in a bottom-up
> fashion in Agile?
>
> I would appreciate your comments. Thanks,
>
> Jana
>
« Return to Thread: Top-down User Stories
| Free embeddable forum powered by Nabble | Forum Help |
