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

The 12 Principles Behind the Agile Manifesto: Principle Number Four – Organizational Cohesion

windchill features best plm software
Written by SPK Blog Post
Published on May 15, 2018

In this discussion of the 12 principles behind the Agile Manifesto, we will address organizational cohesion. Since Agile is closely associated with software development, it can be easy to forget development takes place in the context of the whole business entity. Agile’s concern is not just for development teams, but rather the entire business of producing software.

The fourth principle behind the Agile Manifesto reads:

“Business people and developers must work together daily throughout the project.”

The two parties identified in this statement are developers — which shouldn’t be a surprise given the context — and “business people.” In this context a “business person” would be a product owner or any proxy between the customer and the development team. They’re people who have a vested interest in providing the product to the customer and who play a part in directing its development.

Agile’s mission breaks down the silos of expertise within an organization, encouraging active collaboration between departments. The point of this goes back to the importance of rapidly responding to change in the marketplace. If departments have close relationships, information will travel faster and the organization as a whole can respond in a coordinated way.

Occasional sync-up meetings are not enough. Collaboration needs to happen daily. For some that might seem like overkill. Course-altering decisions are not made with each terrestrial rotation, so it might feel like there isn’t much to share between departments each day. However, cultivating the habit of regular communication ensures that when situations arise, the channels are well established and information flows quickly.

Read more from post three in the series “The 12 principles Behind the Agile Manifesto: Principle Number Three – Deliver Frequently.

Keep your eyes on the SPK and Associates blog for more articles unpacking Agile Methodology.

David Hubbell
Senior Software Engineer
SPK & Associates

Latest White Papers

A Field Guide to Threat Vectors in the Software Supply Chain

A Field Guide to Threat Vectors in the Software Supply Chain

The software supply chain is made up of many integrated parts, people, and processes. The components range from tools and configurations to code libraries and systems. These components’ goals are developing and delivering software. Unfortunately, risks are high due to...

Related Resources

The Business Case for Moving from ENOVIA to Windchill PLM

The Business Case for Moving from ENOVIA to Windchill PLM

With many PLM solutions on the market, it can be difficult to know which is best for your business needs. Dassault Systèmes’ ENOVIA is a popular choice as it is part of their 3DExperience platform. ENOVIA has the same goal as every PLM software which is to manage a...

A Detailed Comparison of PTC Windchill and Siemens Teamcenter

A Detailed Comparison of PTC Windchill and Siemens Teamcenter

Two of the most common enterprise PLM software on the market are PTC Windchill and Siemens Teamcenter  These product lifecycle management solutions have many similarities, but there are a few key differences that may be deciding factors in choosing one. At SPK, we...

The Role of PLM in Orchestrating the Product Digital Thread

The Role of PLM in Orchestrating the Product Digital Thread

Product Lifecycle Management (PLM) plays an important role in the manufacturing industry. Ensuring all factors of a product are well-documented is a priority for every business.  Keeping this information organized is not just a good business practice, but it...