fbpx
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

Total Economic Impact for Atlassian Open DevOps

Total Economic Impact for Atlassian Open DevOps

Forrester's Total Economic Impact Study found that Atlassian Open DevOps could net your organization a potential ROI of 358%. Discover an overview of this Forrester research paper below and download your free copy. Forrester Research Into Atlassian Open DevOps Agile...

Related Resources

LastPass Business For Corporate and Client Security

LastPass Business For Corporate and Client Security

At SPK, we want to empower employees to safely manage their own passwords. Additionally, for organizations, we want to enable the enforcement of password standards. Businesses that follow good password standards, such as increased complexity, non-duplicate passwords ...

Why You Should Be Using PTC Windchill As Your PLM Software

Why You Should Be Using PTC Windchill As Your PLM Software

As a manufacturer, you have to be both structured and agile to constantly stay in line or ahead of the industry. You have to deliver quality products that meet the customer’s needs today whilst being future-proofed for tomorrow.  Aside from that, you also need to...

Smarter Engineering For Medical Devices

Smarter Engineering For Medical Devices

Medical devices are subject to some of the strictest design control regulations in the world. And for good reason. U.S. medical devices are governed by the Food and Drug Administration (FDA). In order to meet the high standards, teams must communicate - effectively....