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

Published by SPK Blog Post
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

6 Secrets To A Successful Atlassian Migration At Scale

6 Secrets To A Successful Atlassian Migration At Scale

With large scale migrations, large user bases, multiple Atlassian tools, plenty of apps, and lots of data, moving to Atlassian Cloud may feel like a steep mountain to climb. But, it doesn't have to be. In fact, we've already helped many customers make the move. Plus,...

Related Resources

How To Restore The Data Card And BOM Tab In SolidWorks

How To Restore The Data Card And BOM Tab In SolidWorks

Hi everyone, I am Daniela and I am the SolidWorks and SolidWorks PDM SME for SPK and Associates. Today I wanted explain a setting that I actually had a tough time finding while working with a user. That is how to restore the Data Card And BOM Tab In SolidWorks. So,...

Do I Need An MSP (Managed Services Provider)?

Do I Need An MSP (Managed Services Provider)?

I’m Chris McHale, CEO and co-founder of SPK and Associates. Over the years, I’ve watched businesses grow. And as they do, they sometimes begin to wonder, “do I still need an MSP?”  Today, I want you to discover why businesses, regardless of size, need an MSP. You see,...

What is SOLIDWORKS PDM and How Does It Benefit Me?

What is SOLIDWORKS PDM and How Does It Benefit Me?

SolidWorks Corporations was founded in 1993. In 1997 it was acquired by Dassault Systèmes. Today, it has amassed over six million ecosystem users from designers to drafters. It has become globally accredited as an industry-leading parametric Computer Aided Design...