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

The 12 Principles Behind the Agile Manifesto

windchill features best plm software
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

Model-Based Definition Capabilities in Creo

Model-Based Definition Capabilities in Creo

Model-based definition (MBD) is a design approach that revolves around creating, organizing, and managing a 3D Model. Explore how PTC Creo utilizes MBD to help you achieve an efficient design.  What You Will Learn In this eBook,...

Related Resources

Optimizing Solidworks PDM Implementation

Optimizing Solidworks PDM Implementation

When multiple employees of a Fortune 100 medical equipment manufacturing company reached out to us for support with workflow functions and permissions, we knew there was a better way.  Rather than fixing the issues that would inevitably keep occurring with their...

Transforming Product Development with Configuration Management

Transforming Product Development with Configuration Management

When developing products, there are many components to keep track of such as parts, data, and configurations.  Keeping up with every minor alteration to a product can be difficult, but using a PLM system like PTC Windchill can help you stay organized.  Configuration...

Five Major Downsides of Changing Software Tools

Five Major Downsides of Changing Software Tools

Switching to new software tools can often seem like an exciting opportunity to streamline processes, increase efficiency, and modernize operations. Some executives seem to think that simply buying a new software tool will solve many problems at once. However, with...