Comments for The Bovine Synchrotron

Comment on Upcoming talk on building micro services by Andy Palmer

Andy Palmer — Sun, 22 Jan 2012 18:57:29 +0000

This sounds awesome. We should pair on something sometime soon (that isn’t a service for rates)

Comment on Why your organisation won’t be agile – Part I by Rapunzel’s Ivory Tower | The Agile Radar

Rapunzel’s Ivory Tower | The Agile Radar — Mon, 12 Dec 2011 15:07:47 +0000

[...] James Lewis recognized some of these challenges. (but was perhaps more brutal than my insider view) [...]

Comment on Why your organisation won’t be agile – Part I by Rapunzel's Ivory Tower | The Agile Pirate

Rapunzel's Ivory Tower | The Agile Pirate — Tue, 13 Sep 2011 18:41:07 +0000

[...] James Lewis recognized some of these challenges. (but was perhaps more brutal than my insider view) [...]

Comment on Agile Brazil and ThoughtWorks, Porto Alegre by Rafael Noronha

Rafael Noronha — Thu, 01 Jul 2010 23:40:00 +0000

Nice talk at #AgileBrazil.

Keep up on sharing agile adoption experiences!

Comment on With measurement comes control by Michael Norton

Michael Norton — Tue, 16 Mar 2010 15:47:56 +0000

James:

Very good post. Visibility can be a detriment in the wrong organization. Trust is critical and abuse of an open environment can destroy that rust.

Keep it up.

Comment on BCS – SPA talk on Agile Adoption Anti-patterns – March 3rd by kash

kash — Thu, 04 Mar 2010 18:28:29 +0000

will the slides be posted online?

Comment on Why your organisation won’t be agile – Part I by Anonymous Coward

Anonymous Coward — Wed, 17 Feb 2010 00:50:16 +0000

What’s wrong with Golf Course Agile? It’s a simple truth that not every organization is prepared for (or will succeed with) self-organizing teams, pair programming, etc.

Having said that, I would suggest that ALL software development organizations will benefit from visibility, predictability, repeatability, and dare I say *Software Production Management*

Comment on Why your organisation won’t be agile – Part I by james

james — Mon, 15 Feb 2010 09:27:36 +0000

Hey Robert – glad you enjoyed the post. You are absolutely correct in this – and this is certainly one of the failure modes for projects that I see. How can you expect people to execute something they have never seen work? I’m going to talk about this a bit more in my next post I think.

Comment on Why your organisation won’t be agile – Part I by MyWeeklyLinks – Week 6 « Ole Morten Amundsen

MyWeeklyLinks – Week 6 « Ole Morten Amundsen — Sun, 14 Feb 2010 15:16:40 +0000

[...] Why your organisation won’t be agile Attacking mainstream agile. Or, really, the mainstream implementation of [...]

Comment on Why your organisation won’t be agile – Part I by Robert Reppel

Robert Reppel — Sat, 13 Feb 2010 15:27:12 +0000

I find that keeping a project in “pull” mode instead slipping back into “push” is an ongoing struggle: The need for (perceived) security and predictability constantly railroads folks into the direction of making a “traditional” project plan with tasks broken down and assigned several weeks in advance and written-in-stone dates where a set of specified-in-advance features need to be available.

Indeed, courage seems to be the least fashionable part of Agile, for very good reasons: The “traditional” way to run a project feels intuitive to most managers because they usually have never seen anything that works better. They rightly think that using no project plan at all will lead to chaos. By comparison, getting one’s ducks in a row by waterfall planning and assigning tasks in advance will work much better. Ergo, projects fail because not enough of that was done. These are deeply held convictions, seemingly backed up by experience. Building a case for doing things differently can be a livelihood-threatening exercise. When management mandates agile practices it’s far safer to go the Scrummerfall or “Cargo Cult Agile” route instead.