spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

The 12 Principles Behind the Agile Manifesto

Written by SPK Blog Post
Published 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

How to Prepare Your Organization for an AI Rollout

How to Prepare Your Organization for an AI Rollout

Managing your organization’s knowledge base may be challenging, especially if information is scattered across multiple systems. Discover how Atlassian’s AI Rovo agents help manage this.What You Will Learn In this eBook you will discover: Why knowledge management...

Related Resources

Reducing CAD File Errors and Rework

Reducing CAD File Errors and Rework

File mistakes and unnecessary rework remain all too common in the engineering space. Inefficient CAD file management due to poor collaboration and hardware limitations can result in missing details or time-consuming corrections. This is why reducing CAD errors is so...

The Cost of Confusion: Streamlining Service Manuals

The Cost of Confusion: Streamlining Service Manuals

While service manuals may seem like just a reference guide, they should be considered part of the product itself.  When service documentation is outdated, inconsistent, or difficult to follow, it leads to costly errors, frustrated customers, and compliance risks. In...

Future Trends in PLM: What Engineering Leaders Need to Know

Future Trends in PLM: What Engineering Leaders Need to Know

Product Lifecycle Management (PLM) solutions are evolving with advances in cloud computing, AI, automation, and sustainability initiatives. For engineering leaders, staying ahead of these changes is critical to driving innovation, maintaining compliance, and improving...