logo
  • About
    • Management
    • World Wide Technology
  • Case Studies
  • Capabilities
    • Mobility
    • Software Development
    • Architecture and Integration
    • Agile Transformation and Training
    • UX and Design
    • Tactical Collaboration
  • News
    • Company Blog
  • Careers
  • Contact
Menu

Were Pirates Agile?

  • October 31, 2016
  • /
  • Comments Off on Were Pirates Agile?
  • /
  • Uncategorized
agile-pirates-halloween

A good friend of mine has been watching Black Sails (for those of you who don’t know, Black Sails is a prequel to Treasure Island and is being aired on the Starz Network) and he commented at how similar the pirate structure was to a Scrum team. Of course, being the Agile Coach that I am (Agile 24/7), this got me thinking and so I decided to do a little research just to see what parallels can be drawn from a band of pirates and an Agile team.


They were Self-organizing and Self-managing

A pirate crew was very much a self-organizing structure, all crew members got an equal say in decisions. Officers were generally elected including the captain and the officers. Almost all decisions were made by election or the crew voted to delegate decisions to an individual.  The crews were generally cross-functional, but some specialist skills were in short supply and those crew members with technical skills were highly valued, but generally crews were expected to pitch in and perform multiple roles.


They had a Product Owner

A captain was elected and his role was to set vision and direction. The captain would typically be a single voice and he ultimately became responsible for the success or failure of the project. He would choose the next target or destination and would decide how to respond to navigation hazards that could plan around. There were some perks associated with the job but generally loot was divided equally amongst the crew.  A captain may get 1.5 or 2 shares. Successful captains would likely be re-elected to their position but unsuccessful ones may not be so fortunate. There was a distinct lack of authority in this role outside of navigation and strategic decisions.


They had a Scrum Master or Team Coach

Crews would also elect a quartermaster. Their job was to ensure the ship ran well. He understood the process and would do his best to coach the crew into keeping the ship running at its optimal performance. But the quartermaster did not have authority over the crew beyond this.  Pirate crews were made up of runaway slaves, deserters from armies and ships or fortune seekers, but many were not skilled sailors or fighters and most had a very strong aversion to authority and discipline.  Quartermasters were first and foremost coaches. They would encourage the crew to learn the necessary skills and to keep the workflow effective.  Quartermasters were likely seasoned sailors with lots of experience and the ability to understand how a ship works and how to coach the crew to do it. However, unlike a formal Navy, where discipline could be used to enforce order, a pirate crew didn’t do this. If a quartermaster struck a sailor, they risked being marooned as a consequence.


The Crew had Individual Responsibilities

All crew members had responsibilities and were held accountable by their peers, and all understood that the crew stood or fell on its own, so anyone not pulling their weight or letting the crew down was a liability. While there were officers, the officers were organizational necessities not authority figures, and their role was more about communication than control. Discipline was most definitely not enforced by officers.


But the Best Parallel is…. They had Working Agreements

The pirate code: Is this perhaps the earliest documented team-working agreement?  Each crew had and documented their code and held the other members of their crew accountable to it. The code contained how decisions were made and what decisions were delegated. For example, they decided how loot was divided or how the team interacted with each other. It was clear that in most cases, it was a flat structure and that roles were temporary and were elected.


Definition of “Done”

This one in particular amused me, but the pirate code contained a definition of “done” for being a pirate.  If a pirate earned 1000 pounds, then he may retire. If the pirate lost a limb they could leave the crew and would be given 800 pounds (400 pounds if it was just a hand).


Rules to Abide By

Pirates also had a code of “honor” – at least among pirates. Pirates were generally forbidden from stealing, destruction, sexual assault, fighting, desertion, gambling or breaking up the pirate band. Some pirate ships even mandated an early bed time!


So, the answer to the question posed… were pirate crews Agile?  Aye they were me bucko. Aye they were.

About the Author

This author has not added a biography. Meanwhile john.yorke has contributed 5 posts. Click here to view them.

Recent Posts
  • An Interview with Kate Chadha, User Experience Practice Lead, WWT Asynchrony Labs St. Louis
  • An Interview with Kartik Patel, Office Lead, WWT Asynchrony Labs New York
  • Starting Your Tech Career? Consider WWT Asynchrony Labs in Springfield, Missouri
  • Re:Lax in Action
  • Make Risks Visible with “RAID bingo”
Recent Comments
  • Johan Brodin on Forecasting: Asking Why and Discovering What’s Behind the When (Part 3)
  • Bill on WWT Asynchrony Labs Participates in First-Ever “Longest Day Hack Alzheimer’s” Event
  • Liz Hall on WWT Asynchrony Labs Participates in First-Ever “Longest Day Hack Alzheimer’s” Event
  • Mayada H on Apache JMeter & Integrated Windows Authentication
  • Irudaya Raj on Using TLS with Self-Signed Certificates or Custom Root Certificates in iOS
Archives
  • March 2018
  • February 2018
  • January 2018
  • April 2017
  • March 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • August 2016
  • July 2016
  • February 2016
  • October 2015
  • September 2015
  • August 2015
  • June 2015
  • April 2015
  • March 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • May 2014
  • April 2014
  • March 2014
  • January 2014
  • December 2013
  • November 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • April 2012
  • February 2012
  • November 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
Categories
  • Agile
  • Asynchrony
  • Change
  • creativity
  • Design
  • Development
  • Enterprise Architecture
  • Hackathon
  • Healthcare
  • Quality Assurance
  • Uncategorized
  • Visual Thinking
async-logo-footer
info@asynchrony.com
314.678.2200
900 Spruce Street, Suite 700 St. Louis, MO 63102
Menu
  • About
    • Management
    • World Wide Technology
  • Case Studies
  • Capabilities
    • Mobility
    • Software Development
    • Architecture and Integration
    • Agile Transformation and Training
    • UX and Design
    • Tactical Collaboration
  • News
    • Company Blog
  • Careers
  • Contact