Comments for It's a Delivery Thing http://itsadeliverything.com The art of leading software development teams Wed, 16 May 2012 21:53:11 +0000 hourly 1 http://wordpress.org/?v=3.3.2 Comment on Software Craftsmanship is a community of practice with overlapping values by Steven Thomas http://itsadeliverything.com/software-craftsmanship-is-a-community-of-practice-with-overlapping-values#comment-780 Steven Thomas Wed, 16 May 2012 21:53:11 +0000 http://itsadeliverything.com/?p=597#comment-780 Thanks for dropping by Dave. Unfortunately, I won't be able to attend SCNA - at least not this time around. Thanks for dropping by Dave. Unfortunately, I won’t be able to attend SCNA – at least not this time around.

]]> Comment on Software Craftsmanship is a community of practice with overlapping values by Dave Hoover http://itsadeliverything.com/software-craftsmanship-is-a-community-of-practice-with-overlapping-values#comment-779 Dave Hoover Wed, 16 May 2012 16:39:39 +0000 http://itsadeliverything.com/?p=597#comment-779 Hi Steven, I think you'd be surprised at how much I agree with your post. :) I wrote most of the book in 2005 and 2008, and my thoughts on these issues have definitely evolved in the intervening years. Are you coming to SCNA this year? Hi Steven, I think you’d be surprised at how much I agree with your post. :)

I wrote most of the book in 2005 and 2008, and my thoughts on these issues have definitely evolved in the intervening years.

Are you coming to SCNA this year?

]]> Comment on Software Craftsmanship is skilled software development in small scale production by Steven Thomas http://itsadeliverything.com/software-craftsmanship-is-skilled-software-development-in-small-scale-production#comment-762 Steven Thomas Sun, 22 Apr 2012 12:58:41 +0000 http://itsadeliverything.com/?p=594#comment-762 Doug, good point. I guess I was not thinking about scale in terms of a small number of production units but was thinking in terms of the number of customers/users. The original craftsmen produced a small number of production units for a small number of customers/users. But software developers can produce a very small production run (one unit) for a world wide customer/user base - which is what we do at the BBC. And that type of scale requires certain practices to do well. Practices that are unnecessary for a developer writing some software for themselves; again only one production unit but in this case only one customer/user and a tolerant one at that. Doug, good point. I guess I was not thinking about scale in terms of a small number of production units but was thinking in terms of the number of customers/users. The original craftsmen produced a small number of production units for a small number of customers/users. But software developers can produce a very small production run (one unit) for a world wide customer/user base – which is what we do at the BBC. And that type of scale requires certain practices to do well. Practices that are unnecessary for a developer writing some software for themselves; again only one production unit but in this case only one customer/user and a tolerant one at that.

]]> Comment on Software Craftsmanship is skilled software development in small scale production by Doug Bradbury http://itsadeliverything.com/software-craftsmanship-is-skilled-software-development-in-small-scale-production#comment-761 Doug Bradbury Sun, 22 Apr 2012 12:13:53 +0000 http://itsadeliverything.com/?p=594#comment-761 I wouldn't be too troubled by the idea of small scale. The interesting thing about software is that once you build it, it's instantly distributable and easily copied. There is no "mass production" step needed in software. So a software craftsman is able to build small scale, then go large scale with minimal effort. I wouldn’t be too troubled by the idea of small scale. The interesting thing about software is that once you build it, it’s instantly distributable and easily copied. There is no “mass production” step needed in software.

So a software craftsman is able to build small scale, then go large scale with minimal effort.

]]> Comment on Agile Project Initiation by Methodologies and Project Madness | beyondcenter http://itsadeliverything.com/agile-project-initiation#comment-759 Methodologies and Project Madness | beyondcenter Mon, 09 Apr 2012 15:10:34 +0000 http://itsadeliverything.com/wordpress/?p=6#comment-759 [...] Macbeth returns to the resources (The Witches) who had been advising him since Project Initiation. At this point in the play, the audience might question the Witches role. Perhaps they are [...] [...] Macbeth returns to the resources (The Witches) who had been advising him since Project Initiation. At this point in the play, the audience might question the Witches role. Perhaps they are [...]

]]> Comment on Agile Roles and Responsibilities by Methods to the Project Madness | beyondcenter http://itsadeliverything.com/agile-roles-and-responsibilities#comment-758 Methods to the Project Madness | beyondcenter Sun, 08 Apr 2012 19:08:00 +0000 http://itsadeliverything.com/wordpress/?p=14#comment-758 [...] project decisions. Some might argue that Lady Macbeth was not just a stakeholder, but actually an Agile Customer or Business Sponsor or perhaps an Agile Product Manager. One thing was for certain, [...] [...] project decisions. Some might argue that Lady Macbeth was not just a stakeholder, but actually an Agile Customer or Business Sponsor or perhaps an Agile Product Manager. One thing was for certain, [...]

]]> Comment on Two Pillars of the Lean Thinking House by Agile/Lean As I Wish It Would Be | The Agile Radar http://itsadeliverything.com/two-pillars-of-the-lean-thinking-house#comment-302 Agile/Lean As I Wish It Would Be | The Agile Radar Mon, 16 Jan 2012 14:47:49 +0000 http://itsadeliverything.com/wordpress/?p=32#comment-302 [...] two pillars of Lean, as defined by Toyota, are continuous improvement (Kaizen) and respect people. Scrum and Agile are [...] [...] two pillars of Lean, as defined by Toyota, are continuous improvement (Kaizen) and respect people. Scrum and Agile are [...]

]]> Comment on Two Pillars of the Lean Thinking House by agile42 | Agile/Lean As I Wish It Would Be http://itsadeliverything.com/two-pillars-of-the-lean-thinking-house#comment-289 agile42 | Agile/Lean As I Wish It Would Be Thu, 22 Dec 2011 21:14:00 +0000 http://itsadeliverything.com/wordpress/?p=32#comment-289 [...] two pillars of Lean, as defined by Toyota, are continuous improvement (Kaizen) and respect people. Scrum and Agile are [...] [...] two pillars of Lean, as defined by Toyota, are continuous improvement (Kaizen) and respect people. Scrum and Agile are [...]

]]> Comment on Two Types of Post Implementation Review by Ruth Devenish http://itsadeliverything.com/two-types-of-post-implementation-review#comment-258 Ruth Devenish Mon, 31 Oct 2011 14:39:02 +0000 http://itsadeliverything.com/?p=388#comment-258 I used Steven's workshop approach recently to drive out lessons learnt from a project as part of a PIR. Having not been involved in the project, and with most of the team having left the BBC, this approach was invaluable. The timeline in particular helped to both refresh memories, and focussed discussion really well. I will definately be using this again. I used Steven’s workshop approach recently to drive out lessons learnt from a project as part of a PIR. Having not been involved in the project, and with most of the team having left the BBC, this approach was invaluable. The timeline in particular helped to both refresh memories, and focussed discussion really well. I will definately be using this again.

]]> Comment on Minimum Releasable Feature by Venky http://itsadeliverything.com/minimum-releasable-feature#comment-110 Venky Wed, 14 Sep 2011 06:25:02 +0000 http://itsadeliverything.com/wordpress/?p=33#comment-110 Very informative article. Very informative article.

]]>