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

Atlassian Cloud: Understanding Zero Trust Security

Atlassian Cloud: Understanding Zero Trust Security

Where To Start & Why It Matters What is the Atlassian Cloud Zero Trust Security model? Well, for decades, enterprise security controls were built to protect a large, single perimeter around a corporation. Often described as castle-and-moat security, This approach...

Related Resources

Product Design: How to Eliminate 6 Bottlenecks 2022

Product Design: How to Eliminate 6 Bottlenecks 2022

This product design how to blog explains how virtual CAD can be utilized to eliminate the top 6 design bottlenecks in 2022.  Start-ups are emerging every day to disrupt the market. And established enterprises? They’re plugging more into research and development...

Cloud Based Solidworks — Powered By vCAD

Cloud Based Solidworks — Powered By vCAD

https://youtu.be/4bSvsijnGWE Hi my name is Daniela and I am the Solidworks PDM SME for SPK and Associates. Today we'll be covering how to use cloud based SolidWorks inside vCAD. How to use cloud based SolidWorks within vCAD vCAD is a really handy tool that allows you...

PDM SolidWorks Tutorial: Installation Manager

PDM SolidWorks Tutorial: Installation Manager

https://youtu.be/iUbfS29lzOo Introduction to the SolidWorks tutorial Hi, I'm Daniella. I am the SolidWorks PDM SME for SPK and Associates. Today I'll be going through a quick PDM SolidWorks tutorial on blank installation managers. How to resolve blank installation...