fbpx
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

The 12 principles Behind the Agile Manifesto: Principle Number Three – Deliver Frequently

Written by SPK Blog Post
Published on May 3, 2018

Today’s Agile principle revolves around deriving maximum value from your development effort. This is principle three in our twelve-part series discussing the core ideas behind the Agile Manifesto:

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

This is the backbone of the Scrum model — short development iterations centered around the completion of a finite set of well-defined features or tasks. The result satisfies the definition “done” and ought to be usable or at least testable.

I’m a perfectionist, so my natural tendency is to hold onto a project until it’s “presentable.” For me, this means implementation of all requested features. The application should be more-or-less complete.

Perfectionism, however, defers testing and feedback. I’m not working on all the features simultaneously. So the most efficient use of time is letting the product owner review and comment on features as they emerge with each sprint. In some cases, a feature may even go into production, allowing end users to extract value as soon as possible from development efforts.

Software is worthless until it’s put into use. If a feature is not realistically able to be released to end users, the next best thing is getting it in the hands of testers ASAP for scrutiny, oversight and input. Feedback drives the Agile process. The sooner it can be provided, the more responsive an organization can be. Therefore, we want working features delivered on the shortest reasonable timescale.

Read more from post two in the series “The 12 Principles Behind the Agile Manifesto: Principle Number Two – Harnessing Change.

Keep your eyes on the SPK and Associates blog for more articles unpacking Agile Methodology.

David Hubbell
Senior Software Engineer
SPK & Associates

Latest White Papers

Costs and Benefits of Moving a .NET Application to the Cloud

Costs and Benefits of Moving a .NET Application to the Cloud

Do you know the full cost and benefits of moving your .NET application to the cloud? In this guide we’ll cover everything you need to know about your .NET cloud migration. Is this guide for you? If you’re faced with outdated legacy systems and the pressures of digital...

Related Resources

Jira Service Management Cloud vs JSM Data Center Comparison 2023

Jira Service Management Cloud vs JSM Data Center Comparison 2023

Change is inevitable, especially in our industry. And even more so since the birth of cloud services. So, as Jira Service Management (JSM) Data Center approaches its end of life in February 2024, you’ll need to gear up. Otherwise you risk a seamless transition...

SolidWorks Subscription Changes: What You Need To Know

SolidWorks Subscription Changes: What You Need To Know

We're thrilled to share that all-new SolidWorks Desktop CAD licenses will now encompass "Cloud services" as part of your subscription. Moreover, for our existing SolidWorks users, a seamless avenue will open up to integrate these secure cloud capabilities. You might...

What Is Data As A Strategic Asset?

What Is Data As A Strategic Asset?

Data is business gold. Today, data has transcended its traditional role and ascended to the status of a strategic asset, capable of propelling organizations to new heights of success. And, this paradigm shift marks a departure from viewing data as a mere byproduct, to...