An iterative incremental software development process

Scrum Software Development

Subscribe to Scrum Software Development: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get Scrum Software Development: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Scrum Authors: Pat Romanski, Stackify Blog, Ken Schwaber, Eric Robertson, XebiaLabs Blog

Related Topics: RIA Developer's Journal, Scrum Software Development

RIA & Ajax: Article

The Evo-Cycle: Doing Software the Right Way - In 16 Stages

The evolutionary cycle of a software project involves discrete stages

In the adventurous world of software development, we have all come to experience, criticize, and embrace many software lifecycle approaches (e.g., RUP, Agile, Scrum, XP, etc.). At their core, they intend to identify various stages in the software process and optimize their instrumentation through various iterative techniques. Through my own consulting experience on many projects, I have come to expect a slightly different discrete set of "stages" that invariably accompany software endeavors. Expanding on these traditional software stages, this evolutionary software cycle or "evo-cycle" brings with it an incredible burden for managers and developers alike, often resulting in staff attrition, process degradation, or the dreaded burnout. Knowing the evo-cycle, software professionals can prepare better mentally for its unrelenting impact.

Software professionals usually take a great deal of pride in some combination of:

  •   Chasing and groking the latest software methodology/technology
      (e.g., JPA, PMP, Spring JMS, Ruby, AJAX, etc.) making them more 
      marketable (and better positioned to pay their bills!)

  •   Creating software products and libraries (open source included)
       that can be reused (the DRY principle) by other technologists

  •   Building and deploying software projects that are successfully
       used by their business customers.

More Stories By Gregory Bohmer

Gregory Bohmer is a seasoned architect/implementor of JEE/JSE and open source initiatives on a wide range of enterprise-level applications. Clients include various branches of the U.S. Federal Government. He is currently the president and principal architect at Tactical Trust, Inc.

Comments (3) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Tomislav 01/13/08 06:58:16 PM EST

Wonderful catalogue of work hazards, too many lively reminders of my own experiences!

Gregory 01/08/08 01:58:13 PM EST

This is a case of an error in the online form of this article. The print article is simply titled "Software Takes Stamina". Not sure what happened with this online version, it appears someone at sys-con took the liberty of changing the title.

-The original author.

jrt 01/03/08 11:27:58 AM EST

What a crock -- Exceptional usage of attention getting title and buzzwords that have no follow up in what is presented in the article itself.

"AJAX and Ruby Makes You More Marketable ...
... and better positioned to pay your bills!"

Where in the article is the information regarding how AJAX and RUBY will make you more marketable?

Where is the information about AJAX and RUBY providing a better position to pay your bills!?