Comments on: Story-Time! The hidden Scrum meeting http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/ Adventures in Agile Software Development and Scrum Fri, 16 Jul 2010 22:31:38 +0000 hourly 1 http://wordpress.com/ By: PMI San Diego Chapter | Home http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-13993 PMI San Diego Chapter | Home Fri, 16 Jul 2010 22:31:38 +0000 http://kanemar.wordpress.com/?p=245#comment-13993 [...] Story Time! The hidden Scrum meeting – ever wonder when the requirements and the analysis happens on a Scrum Team? [...] [...] Story Time! The hidden Scrum meeting – ever wonder when the requirements and the analysis happens on a Scrum Team? [...]

]]> By: Backlog Grooming http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-13959 Backlog Grooming Thu, 06 May 2010 05:53:46 +0000 http://kanemar.wordpress.com/?p=245#comment-13959 [...] http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/ [...] [...] http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/ [...]

]]> By: Keith Forsythe http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-13822 Keith Forsythe Fri, 11 Sep 2009 12:45:08 +0000 http://kanemar.wordpress.com/?p=245#comment-13822 Great post. Prior to each iteration, I conduct a similar process, typically with my senior developers and product owners. I still net add about 30% more stories over the life of the release, but grooming out uneeded stories helps reduce this. Along with hidden meeting, I'm also fond of using the term "hidden user roles" to describe roles like Product Owner and QA Manager when generating stories for a release. To reduce the amount of added stories during the release I strongly urge everyone to include stories like "As a project manager I want to achieve PCI compliance". It's amazing how much time these hidden stories from hidden user roles can take up in a release. More about this here: http://skeptek.com/2009/09/11/tips-for-effective-user-story-gathering-meetings/ Thanks! Great post. Prior to each iteration, I conduct a similar process, typically with my senior developers and product owners. I still net add about 30% more stories over the life of the release, but grooming out uneeded stories helps reduce this.

Along with hidden meeting, I’m also fond of using the term “hidden user roles” to describe roles like Product Owner and QA Manager when generating stories for a release. To reduce the amount of added stories during the release I strongly urge everyone to include stories like “As a project manager I want to achieve PCI compliance”. It’s amazing how much time these hidden stories from hidden user roles can take up in a release. More about this here: http://skeptek.com/2009/09/11/tips-for-effective-user-story-gathering-meetings/

Thanks!

]]> By: martin http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-12981 martin Thu, 21 Feb 2008 23:01:41 +0000 http://kanemar.wordpress.com/?p=245#comment-12981 Hi Kane, Loved the article and how you "groom" your backlog, I have another tactic I like to place on this one. I like to have a role on the team that acts like a scout, depending on the project I will have a resource leave a sprint or is allocated fulltime to user story gathering, estimate gathering, determining priority etc.. The role may be the Product Owner, under the instruction of a product owner or some some of combination. At the same time I have certain team members allocated to a couple of hours in the sprint to assist with providing estimates etc.. Sometimes I prefer to have a down day at the end of a sprint when I get the team as a whole to focus on the backlog prior to the sprint planning meetings. In short as Kane mentions you must keep your backlog updates and in line with the needs of your Clients. Regards, Martin ( CSC ) Hi Kane,

Loved the article and how you “groom” your backlog, I have another tactic I like to place on this one. I like to have a role on the team that acts like a scout, depending on the project I will have a resource leave a sprint or is allocated fulltime to user story gathering, estimate gathering, determining priority etc..

The role may be the Product Owner, under the instruction of a product owner or some some of combination.

At the same time I have certain team members allocated to a couple of hours in the sprint to assist with providing estimates etc.. Sometimes I prefer to have a down day at the end of a sprint when I get the team as a whole to focus on the backlog prior to the sprint planning meetings.

In short as Kane mentions you must keep your backlog updates and in line with the needs of your Clients.

Regards,
Martin ( CSC )

]]>