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 Two – Harnessing Change

Published by SPK Blog Post
on April 19, 2018

Welcome back to the second installment in our 12-part series examining Agile Manifesto principles. Today we’ll discuss the idea of coping with changing requirements throughout a project’s lifetime as in the Agile Manifesto principle:

“Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.”

Changing requirements are a fact of life. Whether you’re building software or waiting tables at a restaurant you must accommodate unforeseen changes. Such changes might take the form of customer demands or technical or regulatory constraints. Rolling with change is a defining characteristic of Agile. The goal here is maximizing long-term, sustained competitiveness and reducing the time to market.

Change is inevitable, not an obstacle to be resisted. Agile seeks to leverage this fact rather than fight it. In many instances being the first to capitalize on emerging market demands means dominance. That being the case, Agile cultivates a working style lending itself to moving quickly in new directions when opportunities — not obstacles — present themselves.

Moving quickly to capitalize on new opportunities manifests itself in several ways: short development cycles, frequent feedback, striving for simplicity and so on. However, the real focus of this principle is the attitude behind those manifestations. Agile seeks to harness change — it regards changing conditions and the ability to adapt to them as an asset. This is an outlook, an attitude, a way of coping with change. If that mindset is missing from an organization, it makes adopting other Agile practices much more difficult.

Read more from post one in the series “A Deep Dive into the Agile Manifesto’s 12 Core Principles.”

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...