Comments for Evan Bottcher http://evan.bottch.com // TODO: think of a witty and intelligent tagline Tue, 03 Jan 2012 20:08:46 +0000 hourly 1 http://wordpress.org/?v=3.1.2 Comment on Projects are evil and must be destroyed by Continuous Delivery and ITIL: Change Management http://evan.bottch.com/2010/08/29/projects-are-evil-and-must-be-destroyed/comment-page-1/#comment-7655 Continuous Delivery and ITIL: Change Management Tue, 03 Jan 2012 20:08:46 +0000 http://evan.bottch.com/?p=192#comment-7655 [...] 1This in turn suggests that the most effective mechanism for delivering services in this way are cross-functional product teams which are responsible for a service from inception to retirement. If this vision is to be made a [...] [...] 1This in turn suggests that the most effective mechanism for delivering services in this way are cross-functional product teams which are responsible for a service from inception to retirement. If this vision is to be made a [...]

]]> Comment on Projects are evil and must be destroyed by Bart Kooijman http://evan.bottch.com/2010/08/29/projects-are-evil-and-must-be-destroyed/comment-page-1/#comment-7635 Bart Kooijman Fri, 19 Aug 2011 09:48:10 +0000 http://evan.bottch.com/?p=192#comment-7635 I am so surprised this article has not received so much more attention. For many IT organisations this is indeed the fundamental root cause of a lot of their problems in IT (costs to high, projects over budget, projects exceeding deadlines, no productivity, no delivery of quality software and much more). I have the strong feeling management heavily underestimates the way a project is financed impacts how people behave (incentives) and thus the results. I am so surprised this article has not received so much more attention. For many IT organisations this is indeed the fundamental root cause of a lot of their problems in IT (costs to high, projects over budget, projects exceeding deadlines, no productivity, no delivery of quality software and much more). I have the strong feeling management heavily underestimates the way a project is financed impacts how people behave (incentives) and thus the results.

]]> Comment on Projects are evil and must be destroyed by Rup Jones http://evan.bottch.com/2010/08/29/projects-are-evil-and-must-be-destroyed/comment-page-1/#comment-7610 Rup Jones Sat, 04 Jun 2011 23:11:35 +0000 http://evan.bottch.com/?p=192#comment-7610 I can identify with all of it. Our latest endeavour has been to do exactly as you've suggested, but like Gregory Smith says, our 'dedicated' (rotating) support person regularly gets sucked into support problems, and if they need help from other team members, they also get sucked into the vortex, causing real impact on other progress. I've used this as customer bait to get them to prioritise unsexy, but supportability focused stories/requirements in the hope that it eventually makes development team progress more focused, with the added benefit that we can hand over a more simple system to a 'BAU' team. I can identify with all of it. Our latest endeavour has been to do exactly as you’ve suggested, but like Gregory Smith says, our ‘dedicated’ (rotating) support person regularly gets sucked into support problems, and if they need help from other team members, they also get sucked into the vortex, causing real impact on other progress.

I’ve used this as customer bait to get them to prioritise unsexy, but supportability focused stories/requirements in the hope that it eventually makes development team progress more focused, with the added benefit that we can hand over a more simple system to a ‘BAU’ team.

]]> Comment on Projects are evil and must be destroyed by Gregory Smith http://evan.bottch.com/2010/08/29/projects-are-evil-and-must-be-destroyed/comment-page-1/#comment-2992 Gregory Smith Wed, 09 Feb 2011 13:35:57 +0000 http://evan.bottch.com/?p=192#comment-2992 Is this complicated by the fact that some of the work will be funded by capex and some will be funded by opex? Might a develoepr not work on stuff in 1 iteration that has to be attributed to different cost centers? That's not too big a deal but are there other ramifications to a single team taking on both operational and feature based work? I've worked on teams like this before where someone in the team had to wear a pager at all times (rotating) and respond to unresolved L2 tech support calls. While we did realize some of the benefits you describe, it was also very difficult to poredictably complete feature work due the the unpredictable and bursty nature of the support work. We simply worked to make this labor distribution very visible to all stakeholders BUT when we did that people started clamoring for a seperate team to handle all the operational work. Square.One! Is this complicated by the fact that some of the work will be funded by capex and some will be funded by opex? Might a develoepr not work on stuff in 1 iteration that has to be attributed to different cost centers? That’s not too big a deal but are there other ramifications to a single team taking on both operational and feature based work? I’ve worked on teams like this before where someone in the team had to wear a pager at all times (rotating) and respond to unresolved L2 tech support calls. While we did realize some of the benefits you describe, it was also very difficult to poredictably complete feature work due the the unpredictable and bursty nature of the support work. We simply worked to make this labor distribution very visible to all stakeholders BUT when we did that people started clamoring for a seperate team to handle all the operational work. Square.One!

]]> Comment on Projects are evil and must be destroyed by What DevOps Means for Enterprises — Agile Web Development & Operations http://evan.bottch.com/2010/08/29/projects-are-evil-and-must-be-destroyed/comment-page-1/#comment-2115 What DevOps Means for Enterprises — Agile Web Development & Operations Tue, 18 Jan 2011 07:14:21 +0000 http://evan.bottch.com/?p=192#comment-2115 [...] But as we all know, the dev-ops separation is actually a huge barrier when you consider the overall goal of efficiently delivering high-quality, stable services to your users. Probably the best organizational solution I have heard, which came to me from Evan Bottcher, is to move from delivering services using projects to delivering them as products. [...] [...] But as we all know, the dev-ops separation is actually a huge barrier when you consider the overall goal of efficiently delivering high-quality, stable services to your users. Probably the best organizational solution I have heard, which came to me from Evan Bottcher, is to move from delivering services using projects to delivering them as products. [...]

]]> Comment on Projects are evil and must be destroyed by Daniel Prager http://evan.bottch.com/2010/08/29/projects-are-evil-and-must-be-destroyed/comment-page-1/#comment-1349 Daniel Prager Thu, 23 Dec 2010 00:34:11 +0000 http://evan.bottch.com/?p=192#comment-1349 Terrific post. I've referenced it in my own post on <a href='http://agile-jitsu.blogspot.com/2010/12/structured-agile-for-product-teams.html' rel="nofollow">Structure Agile for Product Teams</a>. Keen to read more about your recommendations on "balancing priorities and budgeting" for product teams. Terrific post. I’ve referenced it in my own post on Structure Agile for Product Teams.

Keen to read more about your recommendations on “balancing priorities and budgeting” for product teams.

]]> Comment on Projects are evil and must be destroyed by Continuous Delivery and ITIL: Change Management | Continuous Delivery http://evan.bottch.com/2010/08/29/projects-are-evil-and-must-be-destroyed/comment-page-1/#comment-1084 Continuous Delivery and ITIL: Change Management | Continuous Delivery Mon, 29 Nov 2010 12:55:40 +0000 http://evan.bottch.com/?p=192#comment-1084 [...] 1This in turn suggests that the most effective mechanism for delivering services in this way are cross-functional product teams which are responsible for a service from inception to retirement. If this vision is to be made a [...] [...] 1This in turn suggests that the most effective mechanism for delivering services in this way are cross-functional product teams which are responsible for a service from inception to retirement. If this vision is to be made a [...]

]]> Comment on Setter injection sucks by Li Altro http://evan.bottch.com/2009/02/03/setter-injection-sucks/comment-page-1/#comment-1082 Li Altro Wed, 03 Nov 2010 22:32:24 +0000 http://evan.bottch.com/?p=60#comment-1082 hi and thanks, this web site seriously aided me with a writing theme for my school class at MSU hi and thanks, this web site seriously aided me with a writing theme for my school class at MSU

]]> Comment on DevOps and the Iteration Showcase by DevOps – Ten tips for developers | Evan Bottcher http://evan.bottch.com/2010/08/29/devops-and-the-iteration-showcase/comment-page-1/#comment-1066 DevOps – Ten tips for developers | Evan Bottcher Wed, 15 Sep 2010 22:40:39 +0000 http://evan.bottch.com/?p=200#comment-1066 [...] Evan Bottcher // TODO: think of a witty and intelligent tagline Skip to content Home ← DevOps and the Iteration Showcase [...] [...] Evan Bottcher // TODO: think of a witty and intelligent tagline Skip to content Home ← DevOps and the Iteration Showcase [...]

]]> Comment on Projects are evil and must be destroyed by Fabio Pereira http://evan.bottch.com/2010/08/29/projects-are-evil-and-must-be-destroyed/comment-page-1/#comment-1056 Fabio Pereira Tue, 31 Aug 2010 07:06:52 +0000 http://evan.bottch.com/?p=192#comment-1056 Spot on Evan!!! :) This post is just perfect.. Thinking about root cause analysis, this is really one of the biggest reasons why people behave the way they do on "projects"... We have been talking about these concepts on our current engagement. Merging as much as possible BAU and Projects... Eventually, they will be only one. Very well put ;) Cheers Spot on Evan!!! :)
This post is just perfect.. Thinking about root cause analysis, this is really one of the biggest reasons why people behave the way they do on “projects”…
We have been talking about these concepts on our current engagement.
Merging as much as possible BAU and Projects… Eventually, they will be only one.

Very well put ;)

Cheers

]]>