Comments for Dan Rawsthorne http://drdansplace.com Sat, 06 Mar 2010 02:09:02 -0600 http://wordpress.org/?v=2.8.4 hourly 1 Comment on Make-up Stories by Just a guy http://drdansplace.com/2009/04/make-up-stories/comment-page-1/#comment-85 Just a guy Sat, 06 Mar 2010 02:09:02 +0000 http://drdansplace.com/?p=12#comment-85 I did like your story, and I particularly liked this part: doing the “right thing” is not always the right thing to do. I have to admit I use to hack code and never to follow standards (authority issues) but by reading your blog I can see there's more than meets the eye. Anyway, nice blog Dan! I did like your story, and I particularly liked this part: doing the “right thing” is not always the right thing to do.

I have to admit I use to hack code and never to follow standards (authority issues) but by reading your blog I can see there’s more than meets the eye.

Anyway, nice blog Dan!

]]> Comment on Scrum Evolution Explored by Dan Rawsthorne http://drdansplace.com/2009/05/scrum-evolution-explored/comment-page-1/#comment-68 Dan Rawsthorne Thu, 20 Aug 2009 00:23:24 +0000 http://drdansplace.com/?p=25#comment-68 Nothing else changes but the planning. The review cycle is the same, there is still Sprint Planning, etc. But the Sprint Planning changes so that the main result is the Sprint Goal, not the Sprint Backlog. Then the WIP is generated in an agile way in order to achieve the Goal given the reality of the work that's actually getting done. The only difference is that the team doesn't commit to stories at the beginning, it just commits to them as time becomes available. The main problem is prevention of "scope creep" within the stories once they have been committed to - so you need good definitions of done and a team mature enough to abide by them. Dan Rawsthorne Nothing else changes but the planning. The review cycle is the same, there is still Sprint Planning, etc. But the Sprint Planning changes so that the main result is the Sprint Goal, not the Sprint Backlog. Then the WIP is generated in an agile way in order to achieve the Goal given the reality of the work that’s actually getting done. The only difference is that the team doesn’t commit to stories at the beginning, it just commits to them as time becomes available.

The main problem is prevention of “scope creep” within the stories once they have been committed to – so you need good definitions of done and a team mature enough to abide by them.

Dan Rawsthorne

]]> Comment on Scrum Evolution Explored by Rod Claar http://drdansplace.com/2009/05/scrum-evolution-explored/comment-page-1/#comment-67 Rod Claar Wed, 19 Aug 2009 14:18:28 +0000 http://drdansplace.com/?p=25#comment-67 Nice article, Dan. How do you see Scrum III measuring the delivery of business value if the the Kanban flow is driving the work? Rod Claar Nice article, Dan.

How do you see Scrum III measuring the delivery of business value if the the Kanban flow is driving the work?

Rod Claar

]]> Comment on Scrum Evolution Explored by Rod Claar http://drdansplace.com/2009/05/scrum-evolution-explored/comment-page-1/#comment-66 Rod Claar Fri, 12 Jun 2009 15:58:44 +0000 http://drdansplace.com/?p=25#comment-66 Nice, Dan. One question. How does Scrum III keep business value and business priority up front with the team? Rod http://EffectiveAgileDev.com Nice, Dan. One question. How does Scrum III keep business value and business priority up front with the team?

Rod
http://EffectiveAgileDev.com

]]> Comment on About Me by Richard Watson http://drdansplace.com/about/comment-page-1/#comment-64 Richard Watson Wed, 13 May 2009 21:14:11 +0000 http://drdansplace.com/?page_id=2#comment-64 Does Scrum work for teams who do help desk support? Or for teams who do hardware projects not software development. We were wondering if that was possible... Thank you. Rich Watson Does Scrum work for teams who do help desk support? Or for teams who do hardware projects not software development.

We were wondering if that was possible…

Thank you.

Rich Watson

]]>