I did a quick Google search on \u201cteamwork.\u201d A mere 11.6 million links came up in the search window for my consideration.<\/p>\n
This leads me to believe that \u201cteamwork\u201d has been discussed, analyzed, critiqued, and commented on in more ways than I can imagine. This also suggests that there is not much that I\u2019m going to say here that would be different than what at least one or two of those other 11.6 million posts has suggested.<\/p>\n
So, I\u2019ll leave the clich\u00e9s and admonishments about teamwork to those that have studied for longer and in more detail than I.<\/p>\n
In this discussion, we will use many of those comments about teamwork to consider the similarities between teams that work the sails and those that do it the \u201cAgile\u201d way.<\/p>\n
![\"\"](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2018\/07\/Agile-Sailing-fb-blog3-1024x535.png\")
<\/p>\n
We\u2019re in this together<\/h3>\n
First, let\u2019s look at the concept of a team. When sailing, the team consists of the people that are physically on the boat. There are many others that support the crew onshore and help with preparations, food, and logistics, but when the starting gun goes off, the team is made up of the people that are physically on the boat.<\/p>\n
An agile team mirrors this concept. While there isn\u2019t a body of water that separates the agile team from the rest of humanity, there are constraints such as budget that keep others from joining the team. The people in the team\u2019s seats at the beginning of the sprint are the people that need to get the job done.<\/p>\n
We now have a group of people that are focused on achieving an objective. The racing crew knows the course and they have the equipment (boat, sails, lines, GPS, etc.) to successfully complete the race. How they perform is a function of the equipment they are using and<\/i> how well the team performs. A description of a sailing team working well together can be found in this Sailing World<\/a> article.<\/p>\n Agile teams operate under the same principles. Each person has their role and the expectations of what they should be contributing to the team. There are developers, business analysts, testers, product owners, and scrum masters. The tools of the team include whiteboards, computers, programming languages, and knowledge of the business.<\/p>\n The backlog provides the course and the heading for the agile team. A high performing agile team will deliver working code that achieves a business benefit with each sprint. A team that does not work well will struggle to deliver working solutions. Instead of fantastic boat crashes and sinking ships, there will be budget overruns, low morale, and frustrated stakeholders.<\/p>\n When talking about teams, I\u2019m reminded of the Principles behind the Agile Manifesto<\/a>, especially the following quotes:<\/p>\n Business people and developers must work together daily throughout the project.<\/em><\/p>\n Build projects around motivated individuals.<\/em><\/p>\n Give them the environment and support they need,<\/em><\/p>\n And trust them to get the job done.<\/em><\/p>\n As with all teams, the individuals that make up the team must have the skills required for the roles they are playing. Those are the table stakes to get a seat on the team. Which team achieves the greatest result (whether this is in competition, in impact, in mission, or in revenue) is directly correlated to how well that team works together.<\/p>\n One of the keys to successful teamwork is how well the team communicates.<\/p>\n In the sailing community, there are many discussions about the communication (or lack thereof) between the back of the boat (helm) and the front of the boat (bow). This is evident in the amount of yelling (or enthusiastic discussion) that often takes place during a race. When rounding a mark, the pressure mounts, given that many things need to happen in a very short amount of time to ensure that sails remain above the water (not in the water), the boat doesn\u2019t take on water, and the boat maintains speed so as not to allow competitors to get in front.<\/p>\n For the agile team, the stakes are equally as high or higher and hopefully, no one resorts to enthusiastic discussions (or yelling). Features need to be defined, the code needs to be developed, bugs identified, and working code produced.<\/p>\n In both of these situations, the ability of the individuals on the team to effectively communicate what is going on, what needs to be done, and who will do what at what point is key to a successful result.<\/p>\n Achieving effective communication takes time, consistent interaction, and a willingness of each team member to personally sacrifice for the best team result.<\/b><\/p>\nTeam Performance<\/h3>\n
Communication<\/h3>\n
Conclusion<\/h3>\n