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

The Ultimate Jira Data Protection

The Ultimate Jira Data Protection

Remote work is here to stay, and companies are turning to cloud-based solutions to support their teams. Atlassian's suite of products is a top choice for businesses worldwide. But, many businesses are still unsure about its built-in data protection capabilities....

Related Resources

PTC LiveWorx 2023 Highlights

PTC LiveWorx 2023 Highlights

PTC LiveWorx is the premier event bringing together professionals and innovators from various industries. It ignites the exploration of digital transformation, industrial innovation, and emerging technologies. From engaging keynote presentations to hands-on workshops...

Solidworks Error: No Database Attached To This View – Part 2

Solidworks Error: No Database Attached To This View – Part 2

Hi everyone, I am Daniela, the SolidWorks PDM SME for SPK and Associates. Today, I’ll be showing you how to fix the SolidWorks error message “no database is connected to this view.”  This video is split in to two parts. Check out part one here. You can watch the video...

5 Reasons to Celebrate SPK’s 20th Birthday

5 Reasons to Celebrate SPK’s 20th Birthday

It’s a landmark year for our team at SPK and Associates this year - we’re celebrating our 20th birthday! We’ve grown from our humble beginnings in Los Gatos, California with two people working for us back in 2003. Now, we’re an internationally established business and...