Comments on: Difficult decisions when you’re between a rock and a hard place http://kanemar.com/2006/06/18/difficult-decisions-when-youre-between-a-rock-and-a-hard-place/ Adventures in Agile Software Development and Scrum Fri, 16 Jul 2010 22:31:38 +0000 hourly 1 http://wordpress.com/ By: Lessons for Product Owners from The Kobayashi Maru « Kane Mar http://kanemar.com/2006/06/18/difficult-decisions-when-youre-between-a-rock-and-a-hard-place/#comment-13540 Lessons for Product Owners from The Kobayashi Maru « Kane Mar Tue, 04 Nov 2008 21:02:25 +0000 https://kanemar.wordpress.com/2006/06/18/difficult-decisions-when-youre-between-a-rock-and-a-hard-place/#comment-13540 [...] Scrum is a natural breeding ground for Kobayashi type situations. I blogged about one such problem here [...] [...] Scrum is a natural breeding ground for Kobayashi type situations. I blogged about one such problem here [...]

]]> By: Dave Nicolette http://kanemar.com/2006/06/18/difficult-decisions-when-youre-between-a-rock-and-a-hard-place/#comment-18 Dave Nicolette Tue, 20 Jun 2006 12:18:41 +0000 https://kanemar.wordpress.com/2006/06/18/difficult-decisions-when-youre-between-a-rock-and-a-hard-place/#comment-18 It's always problematic to change methodologies in the middle of a project. We've encountered the same problem at our company a couple of times. My take-away is this: Don't do it. Introduce Scrum on a new project rather than one that is already underway. Also, RUP is most commonly used in an iterative waterfall fashion. This should not be a surprise. It's been my experience that when you honestly try to use RUP in an "agile" way, with all team members collaborating directly with each other across professional disciplines and focusing together on work for the present iteration, the whole four-stage RUP structure just evaporates because there's no longer any need even for the light level of ceremony RUP defines. It’s always problematic to change methodologies in the middle of a project. We’ve encountered the same problem at our company a couple of times. My take-away is this: Don’t do it. Introduce Scrum on a new project rather than one that is already underway.

Also, RUP is most commonly used in an iterative waterfall fashion. This should not be a surprise. It’s been my experience that when you honestly try to use RUP in an “agile” way, with all team members collaborating directly with each other across professional disciplines and focusing together on work for the present iteration, the whole four-stage RUP structure just evaporates because there’s no longer any need even for the light level of ceremony RUP defines.

]]>