Posted by Mike on May 28, 2009
If you are an industry underdog, then:
- “If you’re outmatched by the competition, isn’t it silly not to take a chance?”
If you are the niche leader, then:
- “Right now, great teams (such as the Colts and Patriots) use the no-huddle selectively, as a way to maximize their dominance.”
Hmmm… Is agile software development, kinda like the no-huddle offense?
- “Why not put together a lighter, better-conditioned offensive line and a radically simplified playbook and see what happens?”
Perhaps smaller teams in coordinated efforts will improve speed to market?
- “The strategy that’s right for heavyweights has nothing to do with how welterweights should fight.”
Something to aspire to:
- “Generally, he’s doing so much more with so much less.”
Posted by Mike on September 19, 2008
Dr. Dobb’s Journal has an article called
Beyond Functional Requirements On Agile Projects in its October 2008 issue. I think that it is not only worth reading for the subject matter contained in the title, but also for the view you will get of agile software development.
Figure 1, in the article, shows the full system lifecycle when using agile software development. I especially appreciated the mention of Iteration -1 and Iteration 0. These two iterations are completed before starting the Construction Lifecycle. They include pre-project activities (Iteration -1) and the Inception Phase (Iteration 0). The Inception Phase includes the work required to get the project started, including initial modeling and planning.
The article makes mention of disciplined agile. This implies that you can also have undisciplined agile. It’s all about mastering your craft and this is important enough that the article concludes with a strategy of Developer Education.
There is more to the article and it is well worth the read.
Posted by Mike on March 4, 2008
Today, I am concentrating on prep. work for three planning sessions I have scheduled for Wed., Fri., and Mon. The goal for these sessions is to identify the remaining tasks that we know of, for interfaces and forms, on our project. Next, we are going to prioritize and schedule these tasks into 4-week sprints. Once this is done, I will add any new tasks into the project plan.