203 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
Latest 7 Posts
Git and GitHub for Scrum Masters
Tue, Aug 29th 2017 13
Don’t be the first to miss out on LAST Canberra!
Wed, Aug 23rd 2017 6
Get my Agile book for free – 24 hours only!
Thu, Aug 10th 2017 1
Five tips for passing the PMI Agile Certified Practitioner (PMI-ACP) exam
Sun, Jul 30th 2017 10
Inaugural Scrum Coach Retreat Sydney
Sun, Apr 2nd 2017 4
Agile Team Energiser: Rock,Paper,Scissors,Lizard,Spock
Thu, Mar 2nd 2017 6
Using graffiti to build high-performing teams.
Mon, Feb 27th 2017 2
Top 10
The Project Manager – conductor or one-man band?
Sat, Feb 6th 2016 21
Git and GitHub for Scrum Masters
Tue, Aug 29th 2017 13
Five tips for passing the PMI Agile Certified Practitioner (PMI-ACP) exam
Sun, Jul 30th 2017 10
Agile and The Black Swan
Fri, Jul 8th 2016 9
Four free Agile resources that you should know about (but probably don’t!)
Mon, Oct 17th 2016 9
Spice up the Monday morning stand-up
Sun, Jan 17th 2016 7
Highlights from Scrum Australia 2016
Mon, May 2nd 2016 7
Inaugural Sydney Agile Coach meetup
Thu, Apr 28th 2016 7
How popular are Agile Certifications with employers?
Mon, Aug 8th 2016 7
The Rubber Chicken and other ways to get Agile meetings started on time
Tue, Jul 26th 2016 6

Agile and The Black Swan
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
Ethann Castell    

The Black Swan

The Black Swan concept is based on an ancient saying which presumed black swans did not exist. People mistakenly thought that the fact that no-one had even seen a black swan, meant that they didn’t exist. (The saying was rewritten after black swans were discovered in the wild!) Nassim Nicholas Taleb popularized the term in his 2007 book The Black Swan: The Impact of the Highly Improbable. Taleb talks in his book about events or occurrences which that deviate beyond what is normally expected of a situation and that would be extremely difficult to predict.

What could possible go wrong?

The range of unexpected occurrences that can derail a sprint, or a project, is wide and varied.  From my own experience I’ve picked a few of the more exotic unexpected events that have impacted projects that I’ve worked on.

  • One of the software developer’s goes on holiday and his temporary replacement reports that much of the developer’s code, which he claimed to have written himself, actually came from another company (as determined by comments and digital signatures).
  • Volcanic ash grounds all international flights meaning that primary stakeholder is unavailable for meetings for several days
  • Developer has a stroke and is unavailable for an undetermined period of time
  • Lose access to all corporate computer systems for 3 days for never-completely-explained reasons.
  • Product owner violates employment contract by accepting job with competitor and is escorted off premises immediately after this is discovered.
  • Key stakeholder has nervous breakdown and ends up in psychiatric ward
  • Users at one office band together and refuse to pilot the new solution.
  • Vendor’s Project Manager catches Tuberculous.

This is just a sample of the types of unexpected things that regularly occur to derail even the best laid plans.  In traditional Waterfall models of development, such occurrences can have major negative consequences on a project.  And let’s be fair, these type of unexpected events will also have an impact on Agile projects as well.  But I’ll argue that Agile methodologies handle these unexpected events much better than traditional methods, enabling progress to continue in a much better fashion than traditional methodologies allow for.


Why does Agile handle Black Swans so well?

Agile almost expects the unexpected. There are a number of key parts to Agile that deal with unexpected Black Swan-type events most effectively.  I’ll  expand on some of the most powerful aspects below.

The Art of the Possible

A key part of the Agile mindset, and one that is often overlooked in my opinion, is that Agile is “the art of the possible”. In whatever situation, no matter what the circumstances or unexpected events, we focus on what we can do to move closer to delivering business value (rather than focusing on the obstacles).

Small Experiments

A key part of the Agile mindset is that the future is unknowable, and the best way to deal with this is to do small experiments and then empirically assess the results.

By doing small experiments /small bets/sprints we are effectively reducing our risk profile.  Should a significant unexpected event occur, then in many ways the worst it can do is derail our (two week) sprint/iteration.  And then we re-assess what we can do during the next sprint/iteration planning meeting – which is pretty much what we would be doing in any case.

Limited WIP

Small experiments and sprints are ways of limiting our Work In Progress (WIP).  Systems that don’t limit WIP can invest significant resources in having large amounts WIP, and the face high costs if all WIP has to be halted for some reason. One advantage of limiting WIP is that if something should contaminate the process, or causes the process to stop, then only the WIP is affected. All the remaining items in our backlog may be affected to some degree by the unexpected event, but since we haven’t invested any resources in them, we don’t incur the same large penalty costs.

Focus on Value

In Agile we prioritize based on business value (rather than speed, cost, ease etc). By focusing on completing the highest value items first, we ensure that should a Black Swan event happen then at least we have completed the most important work.

Potentially Shippable Product

Agile methods aim to produce a potentially shippable product at the end of every iteration. By delivering a potentially shippable product at the end of every iteration, we ensure that even in the case of a Black Swan event, we have something workable that we can potentially go live with and gain value from.

Embracing the Black Swan

Black Swan events have occurred throughout history and my guess is that they will continue to occur going into the future. I’ve given you a number of Black Swan examples from my own experience and I’m sure that you have some from your own experience as well. Due to their unexpected nature, it’s quite frivolous to try and predict when they will occur.  But we should have a plan for dealing with the unexpected. The approach I like to adopt is two-fold. First, monitor your activities diligently. Second, deal with what whatever happens.



The post Agile and The Black Swan appeared first on Ethann Castell.

Jul 08, 2016
10 hits

Recent Blog Posts
Git and GitHub for Scrum Masters
Tue, Aug 29th 2017 2:17a   Ethann Castell
Scrum Masters generally don’t need to have the same depth of technical skills as the software developers on their team.  However if your team is using Git for source code version control, then you as the Scrum Master or Iteration Manager, may find yourself bamboozled by terms such as HEAD, Master, Squash and Pull Request. This is the situation I found myself in recently, and even though I had previously used other version control systems such as CVS and SVN, I was still confused by discu
Don’t be the first to miss out on LAST Canberra!
Wed, Aug 23rd 2017 8:01a   Ethann Castell
The LAST Conference is taking place in Canberra on September 14th, and if you’re in the vicinity then I highly recommend that you attend. Tickets are selling fast but they tell me that at the time of publishing this post, there are still some spaces available. LAST Sydney was great LAST is an acronym for (Lean Agile and Systems Thinking) and as you might expect with a name like that, the topics covered tend to be somewhat broader in scope than the topics which feature at other Agile confer
Get my Agile book for free – 24 hours only!
Thu, Aug 10th 2017 2:57a   Ethann Castell
The Kindle edition of my book Awesome Agile Ceremonies – 104 techniques to energise your Agile teams is free to download for the next 24 hours. I wrote this book earlier this year to help Scrum Masters and Iteration Managers spice up their Agile ceremonies and energize their team. If you enjoy this book then please share with your friends and feel free to leave a review on Amazon. Enjoy! The post Get my Agile book for free – 24 hours only! appeared first on Ethann Castell.
Five tips for passing the PMI Agile Certified Practitioner (PMI-ACP) exam
Sun, Jul 30th 2017 10:00p   Ethann Castell
I recently passed the PMI Agile Certified Practitioner (PMI-ACP) exam and wanted to share some tips to help others with this exam. As with other PMI certifications, you’ll need in-depth knowledge of the subject matter to pass this exam.  You should not underestimate the difficulty of the PMI-ACP exam. If you’ve passed your Certified Scrum Master (CSM) exam, be aware that the PMI-ACP is a much more difficult exam – I would say that the PMI-ACP is in a different league than the
Inaugural Scrum Coach Retreat Sydney
Sun, Apr 2nd 2017 9:38p   Ethann Castell
The Scrum Alliance is hosting the inaugural Sydney Scrum Coach Retreat from May 5 – 7 in Coogee. It’s 2 1/2 days of deep-dive learning combined with many opportunities to extend professional relationships within the community. Sounds like a bargain at just over $500.  Register now and I’ll see you there. The post Inaugural Scrum Coach Retreat Sydney appeared first on Ethann Castell.
Agile Team Energiser: Rock,Paper,Scissors,Lizard,Spock
Thu, Mar 2nd 2017 5:35a   Ethann Castell
Most people are familiar with the game Rock, Paper, Scissors – a simple game where two participants compete with hand gestures representing each of the aforementioned objects, and a simple set of rules for determining which object beats the other. Recently I came across an extended version of the game called Rock,Paper,Scissors,Lizard,Spock which appears to have first appeared on The Big Bang Theory. As you might expect, this version of the game introduces two additional hand gestures;
Using graffiti to build high-performing teams.
Mon, Feb 27th 2017 8:11a   Ethann Castell
There’s one thing that strikes me about close-knit, high-performing teams. They seem to have an internal language that people outside of the group have trouble understanding. So how can the use of grafitti encourage the development of this internal language? Well-known author Steve McConnell wrote about this in his book Rapid Development:Taming Wild Software Schedules. Like a lot of other teams, we had a set of in-jokes and rituals that people outside the team had a hard time understand

Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition