Comments on: Three Enhanced Release Burndown patterns http://kanemar.com/2006/11/28/three-enhanced-release-burndown-patterns/ Adventures in Agile Software Development and Scrum Thu, 19 Apr 2012 09:24:37 +0000 hourly 1 http://wordpress.com/ By: Kane Mar http://kanemar.com/2006/11/28/three-enhanced-release-burndown-patterns/#comment-5553 Fri, 29 Dec 2006 23:54:04 +0000 http://kanemar.wordpress.com/2006/11/28/three-enhanced-release-burndown-patterns/#comment-5553 >“Teams that are the first responders to critical application failures”

By this I mean teams solely dedicated to fixing software defects. They may also be known as Tiger teams or Bug-Fix teams.

These teams typically have as much new work [every iteration] as they complete and hence the trend lines [of the Product Burndown] are parallel.

By the way, having a team solely dedicated to fixing bugs is not a good thing (in my oppinion). It is, however, quite common in organizations that use RUP or Waterfall.

]]> By: bruno orsier http://kanemar.com/2006/11/28/three-enhanced-release-burndown-patterns/#comment-5462 Thu, 28 Dec 2006 09:21:30 +0000 http://kanemar.wordpress.com/2006/11/28/three-enhanced-release-burndown-patterns/#comment-5462 What do you mean by “Teams that are the first responders to critical application failures” ?

Thanks

]]>