Comments on: the product owner must pull

By: the product owner must pull (revisited) « silk and spinach

the product owner must pull (revisited) « silk and spinach — Tue, 30 Jun 2009 16:07:26 +0000

[...] one comment In the product owner must pull I described what can happen when there are not enough stories in the pile. Here I want to look at [...]

By: energising the iteration review « silk and spinach

energising the iteration review « silk and spinach — Tue, 30 Jun 2009 16:05:54 +0000

[...] make some changes for the iteration review meeting. One month ago the day had gone very badly (see the product owner must pull), so today we needed to recover a great deal of lost trust, credibility and morale. Here’s [...]

By: the marketing team must pull « silk and spinach

the marketing team must pull « silk and spinach — Tue, 30 Jun 2009 15:47:33 +0000

[...] productivity are going to follow. (I mused about the very same thing for software development in the product owner must pull and the product owner must pull (revisited) last [...]

By: 2005 silk and spinach top ten « silk and spinach

2005 silk and spinach top ten « silk and spinach — Tue, 30 Jun 2009 15:32:15 +0000

[...] the product owner must pull (revisited) [...]

By: lean manufacturing reading list « silk and spinach

lean manufacturing reading list « silk and spinach — Sat, 12 May 2007 21:12:16 +0000

[...] manufacturing concepts – such as pull, jidoka, gemba etc – can be applied to software development with positive effect (see Lean Software [...]

By: organise around value streams « silk and spinach

organise around value streams « silk and spinach — Sat, 12 May 2007 20:16:57 +0000

[...] When the bottleneck is outside of development, it often seems as if we have a sportscar being pulled along by a donkey. And the message from Rittal is clear: as long as we retain functional divisions, the [...]