Comments for My mind wonders... http://danrough.net Mon, 24 May 2010 08:36:55 +0000 hourly 1 http://wordpress.com/ Comment on The Cost of Hidden Work by Not Time Boxing or Commitments but Managing Risk by Using SLAs « My mind wonders… http://danrough.net/2010/03/19/the-cost-of-hidden-work/#comment-1316 Not Time Boxing or Commitments but Managing Risk by Using SLAs « My mind wonders… Mon, 24 May 2010 08:36:55 +0000 http://danrough.net/?p=203#comment-1316 [...] in Progress limit by restricting the amount of streams available to feature work but because of Hidden Work previously discussed, amongst other things, these often failed to focus the team in respect of [...] [...] in Progress limit by restricting the amount of streams available to feature work but because of Hidden Work previously discussed, amongst other things, these often failed to focus the team in respect of [...]

]]> Comment on The Cost of Hidden Work by The Cost of Hidden Work « Rubber Tyres –> Smooth Rides http://danrough.net/2010/03/19/the-cost-of-hidden-work/#comment-1299 The Cost of Hidden Work « Rubber Tyres –> Smooth Rides Fri, 19 Mar 2010 12:44:38 +0000 http://danrough.net/?p=203#comment-1299 [...] http://danrough.net/2010/03/19/the-cost-of-hidden-work/ [...] [...] http://danrough.net/2010/03/19/the-cost-of-hidden-work/ [...]

]]> Comment on Plan The Work But Don’t Work The Plan by danrough http://danrough.net/2010/02/26/plan-the-work-but-dont-work-the-plan/#comment-1294 danrough Fri, 26 Feb 2010 15:57:01 +0000 http://danrough.net/?p=191#comment-1294 Yep, interesting. The article outlines something that I missed when discussing the complications in working in small batch size; context. As it goes on to suggest, lightweight Use Cases are great as is Jeff Patton's suggestion of User Story Mapping. Yep, interesting. The article outlines something that I missed when discussing the complications in working in small batch size; context. As it goes on to suggest, lightweight Use Cases are great as is Jeff Patton’s suggestion of User Story Mapping.

]]> Comment on Plan The Work But Don’t Work The Plan by Bangers http://danrough.net/2010/02/26/plan-the-work-but-dont-work-the-plan/#comment-1293 Bangers Fri, 26 Feb 2010 15:47:38 +0000 http://danrough.net/?p=191#comment-1293 I wonder if elephant carpaccio'd be interesting: http://alistair.cockburn.us/Elephant+carpaccio I wonder if elephant carpaccio’d be interesting:

http://alistair.cockburn.us/Elephant+carpaccio

]]> Comment on One Piece Flow, One Piece At a Time by danrough http://danrough.net/2009/06/01/one-piece-flow-one-piece-at-a-time/#comment-1248 danrough Thu, 04 Jun 2009 08:40:40 +0000 http://danrough.wordpress.com/?p=169#comment-1248 Thanks David, it's a book that is on my list, a list which is ever growing at the moment as new and interesting techniques emerge. I wonder, if you could take the time to outline the steps you take when setting a team up to use Kanban for Software Development? Perhaps this is something for a blog post from you or if not an email would be great. It would be great if it covered: How you define Standard Work, who's involved in the definition of it? How do you get to an understanding of your Queue Limits? Who's involved in Mapping the Value Stream? How does the team know when to do a retrospective? What guidelines do you use for the Retrospectives, presumably they're happening a lot more often if you follow the stop the line mentality and in which case do you timebox them to a shorter period than an hour? Anything else I've missed? Thanks David, it’s a book that is on my list, a list which is ever growing at the moment as new and interesting techniques emerge.

I wonder, if you could take the time to outline the steps you take when setting a team up to use Kanban for Software Development? Perhaps this is something for a blog post from you or if not an email would be great.

It would be great if it covered:

How you define Standard Work, who’s involved in the definition of it?

How do you get to an understanding of your Queue Limits?

Who’s involved in Mapping the Value Stream?

How does the team know when to do a retrospective? What guidelines do you use for the Retrospectives, presumably they’re happening a lot more often if you follow the stop the line mentality and in which case do you timebox them to a shorter period than an hour?

Anything else I’ve missed?

]]> Comment on One Piece Flow, One Piece At a Time by David Joyce http://danrough.net/2009/06/01/one-piece-flow-one-piece-at-a-time/#comment-1247 David Joyce Wed, 03 Jun 2009 20:20:18 +0000 http://danrough.wordpress.com/?p=169#comment-1247 Can I suggest Corey Ladas Scrumban book, I think the answers to your questions may be in there. Can I suggest Corey Ladas Scrumban book, I think the answers to your questions may be in there.

]]> Comment on The Greatest Trick The Devil Ever Pulled Was Making People Believe That He Didn’t Exist by toby http://danrough.net/2009/04/01/the-greatest-trick-the-devil-ever-pulled-was-making-people-believe-that-he-didnt-exist/#comment-1240 toby Thu, 02 Apr 2009 12:34:11 +0000 http://danrough.wordpress.com/?p=163#comment-1240 my advice to you would be to stop procrastinating and get on with it ;o) my advice to you would be to stop procrastinating and get on with it ;o)

]]> Comment on Agile: Like Fingernails On A Chalkboard by The Greatest Trick The Devil Ever Pulled Was Making People Believe That He Didn’t Exist « My mind wanders… http://danrough.net/2008/05/16/agile-like-fingernails-on-a-chalkboard/#comment-1239 The Greatest Trick The Devil Ever Pulled Was Making People Believe That He Didn’t Exist « My mind wanders… Wed, 01 Apr 2009 11:44:49 +0000 http://danrough.wordpress.com/?p=129#comment-1239 [...] posted a while ago about the fact that I thought that all a team needed to be successful was a clear set [...] [...] posted a while ago about the fact that I thought that all a team needed to be successful was a clear set [...]

]]> Comment on Agile Adoption – Just Say No by An Agile Adoption Pattern: Wax On, Wax Off « My mind wanders… http://danrough.net/2008/05/13/agile-adoption-just-say-no/#comment-1232 An Agile Adoption Pattern: Wax On, Wax Off « My mind wanders… Mon, 27 Oct 2008 13:19:43 +0000 http://danrough.wordpress.com/?p=128#comment-1232 [...] On, Wax Off 27 October, 2008 I know I’ve said before that I don’t believe in an Agile Adoption initiative but humour me a little [...] [...] On, Wax Off 27 October, 2008 I know I’ve said before that I don’t believe in an Agile Adoption initiative but humour me a little [...]

]]> Comment on Agile Adoption – Just Say No by Paulo Köch http://danrough.net/2008/05/13/agile-adoption-just-say-no/#comment-1226 Paulo Köch Tue, 12 Aug 2008 20:46:44 +0000 http://danrough.wordpress.com/?p=128#comment-1226 Well, for a couple of reasons, firstly there are those people that you’ll come across that are naturally resistant to it and it’s better not to expose yourself to that pain in the first place and secondly, I don’t think that to be agile should be the end goal, sure business agility will deliver a lot of benefit to your organisation which they’ll thank you for but agile isn’t necessarily the only way to achieve that, by constantly reviewing what you’re doing and aspiring to do it better at all times you’ll deliver huge value, Dr Deming’s plan-do-check-act cycle (on which agile is loosely based) should help you there as a framework by which to carry that out. Biggest sentence ever. Literally, there's only one period. Well, for a couple of reasons, firstly there are those people that you’ll come across that are naturally resistant to it and it’s better not to expose yourself to that pain in the first place and secondly, I don’t think that to be agile should be the end goal, sure business agility will deliver a lot of benefit to your organisation which they’ll thank you for but agile isn’t necessarily the only way to achieve that, by constantly reviewing what you’re doing and aspiring to do it better at all times you’ll deliver huge value, Dr Deming’s plan-do-check-act cycle (on which agile is loosely based) should help you there as a framework by which to carry that out.

Biggest sentence ever. Literally, there’s only one period.

]]>