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

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

6 Secrets To A Successful Atlassian Migration At Scale

6 Secrets To A Successful Atlassian Migration At Scale

With large scale migrations, large user bases, multiple Atlassian tools, plenty of apps, and lots of data, moving to Atlassian Cloud may feel like a steep mountain to climb. But, it doesn't have to be. In fact, we've already helped many customers make the move. Plus,...

Related Resources

How To Restore The Data Card And BOM Tab In SolidWorks

How To Restore The Data Card And BOM Tab In SolidWorks

Hi everyone, I am Daniela and I am the SolidWorks and SolidWorks PDM SME for SPK and Associates. Today I wanted explain a setting that I actually had a tough time finding while working with a user. That is how to restore the Data Card And BOM Tab In SolidWorks. So,...

Do I Need An MSP (Managed Services Provider)?

Do I Need An MSP (Managed Services Provider)?

I’m Chris McHale, CEO and co-founder of SPK and Associates. Over the years, I’ve watched businesses grow. And as they do, they sometimes begin to wonder, “do I still need an MSP?”  Today, I want you to discover why businesses, regardless of size, need an MSP. You see,...

What is SOLIDWORKS PDM and How Does It Benefit Me?

What is SOLIDWORKS PDM and How Does It Benefit Me?

SolidWorks Corporations was founded in 1993. In 1997 it was acquired by Dassault Systèmes. Today, it has amassed over six million ecosystem users from designers to drafters. It has become globally accredited as an industry-leading parametric Computer Aided Design...