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

The 12 Principles Behind the Agile Manifesto

Published by SPK Blog Post
on January 29, 2019

Last March we introduced “The 12 Principles Behind the Agile Manifesto,” a multi-part series that examined the key principles behind an effective agile development strategy. Over the course of this series we have introduced the principles, defined them, and provided guidance for executing them with your team. The ultimate goal of any development cycle is to create an end product that is valuable for the customer or end user, the difference with agile is how it gets done.

The whole reason for adopting Agile methodologies is meeting customer needs.

Read each of The 12 Principles Behind the Agile Manifesto here:

    1. Satisfy the Customer With Early and Continuous Delivery – These are the only requirements for software to be valuable: It needs to work, and it needs to be in the hands of users, not stuck in development. A software product is worthless until can be put to its intended use.
    2. Principle Number Two – Harnessing Change – Changing requirements are a fact of life. Whether you’re building software or waiting tables at a restaurant you must accommodate unforeseen changes.
    3. Principle Number Three – Deliver Frequently – Feedback drives the Agile process. The sooner it can be provided, the more responsive an organization can be.
    4. Principle Number Four – Organizational Cohesion – Agile’s mission breaks down the silos of expertise within an organization, encouraging active collaboration between departments.
    5. Principle Number Five – Cultivate Supportive Environments – If you want a team of motivated people working on your project, you need to supply an environment that nourishes and cultivates that motivation.
    6. Principle Number Six – Promote Face To Face Interaction – The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
    7. Principle Number Seven – The Primary Progress Indicator – As part of sprint planning, each backlog item should have a definition of what it means to call it complete.

Principles 8 through 12 still to come!

David Hubbell is a Senior Software Engineer at SPK & Associates with a focus on DevOps, Continuous Delivery and application development.

Latest White Papers

Three Trends Are Transforming The Service Desk

Three Trends Are Transforming The Service Desk

Your IT service desk is about to change. Find out what's shaping the future. Three factors — enterprise service management (ESM), collaboration, and intelligent service management — are driving the transformation of the service desk. To better meet customers’ needs...

Related Resources

January 2022 vCAD feature updates

January 2022 vCAD feature updates

Happy New Year vCAD Users! It was a busy 2021 in terms of vCAD development and feature enhancements. We've been receiving lots of feedback regarding the platform, and we're assembling a roadmap for 2022 based on our users' needs. Here's what to expect in 2022:...

SPK’s vCAD Solution Increases Productivity, Security, and Savings

SPK’s vCAD Solution Increases Productivity, Security, and Savings

SPK helps a tech manufacturer to increase security and availability of its CAD systems and data by moving them to the cloud—while helping them to save $30k per year.   The Client A well-known maker of power distribution units for IT racks and related equipment...

Accelerating Product Development with Engineering Operations

Accelerating Product Development with Engineering Operations

What is Engineering Operations (EngOps)? Why do you need it, and how do you effectively deploy it?There’s a strange interplay between IT and engineering teams in most firms. That’s because the tech stack that engineers need to design, build, test, and release products...