Proof of Concept - The orca agile manifesto
The orca agile manifestoIssue 153: How these apex predators practice great software development ritualsToday is a special day; the beginning of Shark Week—Holy Week for lovers of sea animals. As a kid who grew up binge-watching every show on The History Channel and Discovery, Shark Week was one of my favorites. Despite that, the buzz these days is about orcas, also known as the killer whale. They say bad guys wear black, and these large dolphins aesthetic are often branded as anti-heroes—the Michael Morbius, Punisher, and Oakland Raiders of the ocean. See this article, “Killer Whales Are Not Our Friends.” This past June, there have been reports and sightings of Orcas disabling ships in the Straight of Gibraltar. One theory is the ship rudders resemble fins of dolphins and they're playing with them. Another theory is these highly intelligent creatures are frustrated by the presence of boats in their territory and attacking the ships to establish dominance. I’m not going to politicize orcas. It's been reported that the orcas are teaching other pods how to use these strategies to disable boats. I’ll leave it to you to decide if they’re terrorists or freedom fighters. What we’ll discuss today is orcas as they pertain to software development. Yes, I’m completely serious. Orcas are team players, patient, highly communicative, and strategic, which is why I believe they're the gold standard of agile software development teams. Culture and structureOrcas are highly social animals and live in pods of about 40 individuals, with the largest pod recorded being 80 (definitely an infrastructure team). They have strong social bonds and communicate for hunting, socializing, and caring for their young. They have various communication methods including clicks for echolocation (standup), whistles (incidents), and pulsed calls (meetings and rituals). Software teams have groups that communicate with groups and groups of groups to stay connected. Perhaps for us, building software is the hunt, but that's only one aspect of it. Teams require social connection to understand each other and grow newer team members. TeamworkOrcas are one of the most sophisticated hunters. It's incredible reading all the various tactics they use around the world to achieve their goal—extremely outcome-oriented. User Story: As an orca, I'd like to maximize the hunting sessions of animals so I can feed my pod. Depending on the pod and region, orcas have different team tactics they use, especially for hunting. Here are three examples that blew my mind in research:
Whether you’re a pod of orcas or a pod of designers, engineers, and product managers, great teamwork requires strategy, communication, and excellent technique. Great companies build software based on the optimal path for their company and customers. The purpose of agile development is to adapt it to these environments and factors. For example, the beaching technique is often attributed to the orca pod in Patagonia. Developing best practicesOrcas have been known to teach their young how to hunt, and these hunting skills are passed down from generation to generation. Orca pods are also known to share their hunting techniques and knowledge with other pods. This is done through a process called cultural transmission. Cultural transmission is the process by which information is passed from one generation to the next. In the case of orcas, cultural transmission is thought to be facilitated by their complex social structure and their use of vocalizations. It’s the number one reason I remain working in tech; the human version of cultural transmission. I wish I could do it like an orca, but I’ll have to settle on sharing learnings, best practices, and mentorship. The tech equivalent of culture transmission is demos and best practices between teams and companies. Flexibility, patience, and persistenceAgile software development is about planning and iterating on that plan based on new developments. Orcas are constantly adapting and changing their hunting tactics to adapt to the environment, and we should as the landscape of software drastically changes. They are flexible and open to different perspectives in problem-solving. Patience is also key to agility. The tasks are small, but the journey is long. It's important to develop flexibility and improvement. And finally, patience and persistence are important to build great software and launch it. Orcas are patient and strategic hunters. They would not rush everything to production and then deal with bug-ridden software. They would use carousel feeding with bugs and leverage their work to make things easier. Agile is about teamwork and relationshipsAgile software development is not the enemy. Many designers perceive it as being forced into incremental improvements, estimating at the mercy of engineering, but that's far from the truth. They are either uneducated about agile or unfortunately worked on teams who don't know how to practice it properly. Agility is personified by orcas, and we have much to learn from them. Hype linksLinks of what I read and interesting ones from NetNewsWire
Job opportunities
|
Older messages
The four types of software in the future
Sunday, July 16, 2023
Issue 152: The different classes and classifications of what we use (and make)
Burning the ships
Sunday, July 9, 2023
Issue 151: Embarking on your new world of dreams and ambitions
Design methods and value delivery
Sunday, July 2, 2023
Issue 150: Rightsizing how you get design work done
The rise of the design founder
Sunday, June 25, 2023
Issue 149: On entering an era of designers building companies (and it's exciting)
The value of continuous research
Tuesday, June 20, 2023
Issue 148: Momentum and rolling research is the key to customer empathy
You Might Also Like
🐺 How to kick start your PR efforts.
Wednesday, March 5, 2025
Lessons from a veteran publicist. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
How Rita Konig Gets Clients to Take Risks
Tuesday, March 4, 2025
View in your browser | Update your preferences ADPro It has been a career-defining few years for Rita Konig. First there was the British interior designer and author's Create Academy course, which
#497: Color Palettes and Generators
Tuesday, March 4, 2025
How to fix a broken color palette, accessible color combinations, color names and palette generators. Issue #497 • Feb 28, 2025 • View in the browser Smashing Newsletter Pryvit! Smashing Friends, How
180 / Make your everyday browsing ridiculously beautiful
Monday, March 3, 2025
Product Disrupt Logo Product Disrupt Half-Monthly Feb 2025 • Part 2 View in browser Welcome to Issue 180 Last year I teamed up with two of my close friends on a side project we're all obsessed with
Accessibility Weekly #438: When to Use Lists
Monday, March 3, 2025
March 3, 2025 • Issue #438 View this issue online or browse the full issue archive. Featured: When to use lists for better accessibility "When creating HTML content, using lists appropriately is
High touch recruiting
Sunday, March 2, 2025
Issue 235: Long-lasting candidate experiences ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
All Compute Must Flow
Sunday, March 2, 2025
“If I don't have that kind of compute on Day 1, I can't breathe." ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
🐺 Is a trade show is your right next step?
Friday, February 28, 2025
Q&A with Shoppe Objects' founders ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
AD100 Designers on Battling Burnout
Thursday, February 27, 2025
View in your browser | Update your preferences ADPro Get Your Groove Back Most days, working in the design field is creatively fulfilling. But occasionally, in the throes of tight project timelines,
Accessibility Weekly #436: Evaluating Overlay-adjacent Accessibility Products
Thursday, February 27, 2025
February 17, 2025 • Issue #436 View this issue online or browse the full issue archive. Featured: Evaluating overlay-adjacent accessibility products "There's a category of third party products