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: Principle Number Four – Organizational Cohesion

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

The AI Maturity Playbook for Product and Engineering Teams

The AI Maturity Playbook for Product and Engineering Teams

Knowing how to integrate AI into your workflows can be the difference between risky, inefficient implementation and successful performance that brings lower costs and a faster time-to-market. This eBook explores how your teams can effectively utilize AI.What You Will...

Related Resources

Why PLM Is Critical for Managing the Entire Product Lifecycle

Why PLM Is Critical for Managing the Entire Product Lifecycle

Bringing a successful product to market takes much more than a strong design.  Companies must manage a plethora of information.  This includes requirements, data, revisions, manufacturing processes, quality controls, supplier collaboration, service information, and...

Achieving Regulatory Compliance through Connected ALM and PLM Systems

Achieving Regulatory Compliance through Connected ALM and PLM Systems

Compliance is not always about having the right documentation.  In regulated industries, compliance is about proving that requirements are defined, changes are controlled, risks are addressed, tests are completed, and approvals are captured in a traceable, audit-ready...