From the Sage MAS Team

[#1]

MME R&D – Agile Software development

The MAS and Accpac teams have been working with the “agile” software development methodology for some time now. MAS 90/200 4.4 and MAS 500 7.3 were both developed using this methodology. In conjunction with the SCRUM process framework, agile enables us to deliver high quality software, faster.

So what is “agile” software development? Agile is relatively new to the MME R&D team, but it really has been around for quite some time. Agile is a “lightweight” method as opposed to heavyweight methods such as Waterfall. Waterfall is considered a sequential development method with very distinct phases; e.g. the requirements phase, design phase, implementation phase, verification (QA) phase, and maintenance phase (post release). All components from each phase are completed before entering the next phase.

Agile is considered an iterative process that incorporates repetitive cycles that have many of the phases listed in the Waterfall method. Each iteration attacks a small chunk (story) of the overall project, including design, implementation, and QA components. Each iteration is typically called a “sprint” and can be anywhere from 2 to 4 weeks in length.

Agile has its roots in other lightweight processes developed in the mid-1990’s such as Adaptive Software Development, Feature Driven Development, Extreme Programming, and Dynamic Systems Development. The Rational Unified Process (RUP) also attempted to institutionalize iterative software development.

In 2001, 17 software development industry leaders, including Kent Beck, Martin Fowler, Jeff Sutherland, and Mike Beedle gathered in Utah to attempt to create a common iterative methodology. They called the new methodology “Agile Software Development” and created the “Agile Manifesto” as the guiding or core principles. The Agile Manifesto captures all the desired end-states of software development:

–        Customer satisfaction by rapid, continuous delivery of useful software

–        Working software is delivered frequently (weeks rather than months)

–        Working software is the principle measure of progress

–        Even late changes in requirements are welcome (features are balanced in conjunction with a specific release date)

–        Close, daily cooperation between business people and developers

–        Face-to-face conversation is the best form of communication

–        Projects are built around motivated individuals, who are trusted

–        Simplicity

–        Self-organized teams

–        Regular adaption to changing circumstances

Agile software development, along with frameworks like SCRUM are beginning to be the norm for software development teams. And Waterfall is slowly being acknowledged as inadequate for delivering large software projects as companies are looking for new ways to stay competitive in a very competitive software marketplace. At Sage, we have already seen the benefit of Agile and SCRUM and are working hard to make it even better.

Regards,

Scot Larsen

Director, R&D, MAS 90/200