A Short History of Iterative Software Development

[This post has also been published on DZone.com, where it has gathered well over 5,000 views.]

It is useful to know about the various iterative software development project methodologies and how they originated, not so that you can follow them religiously but so that you can add them to your bag of tricks.

I recommend learning about the following.

  • Kanban (1953), whose origin lies within the Toyota manufacturing process innovations
  • Scrum (1986), and its storied origin in the 1986 Harvard Business Review seminal article The New New Product Development Game, which examined 6 major Japanese and American companies to conclude that successful teams had replaced sequential approaches with iterative ones
  • Rational Unified Process (1996), proposed by IBM in response to some of the growing market forces looking for alternatives to the Waterfall family of methodologies
  • Lean (1998), and its origin in Toyota's manufacturing system
  • Agile (2001), especially the contents and motivation behind the Manifesto for Agile Software Development, written by many of the software development thought leaders of our time

A good starting point might be to read the content at the two links I've provided in this post.

I believe it is more important to understand the driving forces behind these movements than it is to understand the detailed practices that are in vogue today.

On most projects, I end up adopting or recommending not a pure version of any one of these methodologies, but a hybrid methodology employing those practices and techniques that seem best suited for the team and project at hand.

A final word. Whereas the methodologies listed above mostly concern themselves only with the softer aspects of project management, it is important to understand what I call technical Agile practices, i.e. the many software development tools and practices (e.g. unit testing, continuous integration) that must be mastered in order to extend the theories expounded in these methodologies into practical reality.

Comments

Post a Comment

Popular posts from this blog

Milwaukee Appliance Hand Truck

Image
Milwaukee Appliance Hand Truck, leaning against my shed Also known as a cart or a dolly. The model is HDA700. I paid around $120 for it. Here's a list of the features. Wrought iron frame 800 pound load capacity 6 inch non-marking wheels (solid, non-inflatable, never go flat) Stair climbers to help move loads up and down stairs and curbs Padding to prevent the cart from damaging the appliance (this is the white strip in the picture above) Belt or strap that goes around the appliance to secure it to the cart and keep it in place Manual ratchet belt tightener, the buckle-like part at one end of the belt (more on this below) Belt tightener handle (this is the red handle in the picture above) to add more tension to the belt once the manual ratchet has been used to the tighten the belt  I recently used this hand truck to move a big ass 320 pound refrigerator out of my garage (where it was delivered) and up a couple of steps to the deck, up one more step through the doubl
Read more

Utility trailer buying guide

Image
Introduction I recently bought a utility trailer . (I'll explain momentarily what that is and why you might consider buying one.) Going through the process (research, preparation, purchase, registration, setup and maintenance) has taught me that it's not a simple endeavor and very little good documentation exists in the public domain (e.g. on the Internet). Hence, this post. Research In dictionary terms, of course, "to trail" means "to follow" (or to trace the path of a primary vehicle). Alternately, Wikipedia defines a trailer as an unpowered vehicle pulled by a powered vehicle. So, let's get acquainted with what a utility trailer is and why you might consider buying one. If you're a hardworking, blue collar American you probably already have one -- it's the back half of your pickup truck . Well not quite, but that's the reason Australians refer to a pickup as a utility vehicle. A pickup is characterized by the presence of a flat
Read more

My Experiments with the PICAXE 08M2+

Image
PICAXE 08M2+ I generally prefer to do things the hard way. For example, you can either microwave a frozen dinner or cook from scratch. The microwave option is a good backup plan, but cooking from scratch has far too many advantages, as I outlined in a recent blog post on the do-it-yourself way of life. In the electronics and robotics world, the analogy of cooking from scratch is to build circuits using a bare bones micro-controller chip (e.g. the PICAXE ) rather than a fancy board (e.g. the Arduino ). Therefore, once I get a circuit working with the packaged Arduino approach (e.g. this robot I built recently), I usually try to replicate the circuit using more basic components like the PICAXE. My decision to consider the PICAXE was influenced by Charles Platt's coverage of it in his awesome book Make: Electronics . But essentially, I am a minimalist and I want to see how much I can get done with a bare bones chip rather than a bulky board-based micro-controller like the Ar
Read more