Oct 29View SourceAlanIt was a classic project for not needing Agile and turned into an example of why we were so glad to have been using Agile.- Marketing decided to target a completely different market segment, eliminating the need for a cache, completely altering significant portions of the basic design.- The new version of the base technology had critical bugs and deviations from previous version performance.- The ISO protocol documents were not clear for some uses and the industry norms were actually corner cases of the protocols, defined only by general product behavior, not the documents.- The product space altered drastically with the introduction of a new competitor.Engineers argued for traditional development methods. We used Scrum anyway.- We had a product spec document that was not going to change.- We knew the technology very well, we were just using a newer version of the tech.- We knew the well defined, ISO documented, industry wide protocols.I once worked on a hardware and firmware project where:- We knew the product space intimately.
Several months into the project:
On Tue, Oct 29, 2013 at 6:48 AM, Jean Richardson <jean@...> wrote:
That might be a way to end the conversation, but I don’t think it’s my most effective opener. I tend to hear these kind of comments/objections as requests for more information. Otherwise, I think they wouldn’t be talking to the topic at all. They’d just circumvent any attempts at agile adoption quietly, bringing all their significant skills to bear on the effort.
A week from Friday I’m presenting to a PMI audience where I have been asked to speak on the topic “When Will the Pendulum Swing Back and We Won’t Have to Use Agile Anymore.”
I suggest they quit using Agile immediately.
"It is not necessary to change. Survival is not mandatory."
-- W(illiam) Edwards Deming
Happiness... is not a destination: it is a manner of traveling.
Happiness is not an end in itself. It is a by-product of working,
playing, loving and living.