What started off as a trial-and-error approach to improve the state of software development by a bunch of tinkerers, is today dominated by management consultants, "Thou-Shall" codified frameworks and rigid, expensive tools. Over the last 20 years, we've gone from, "I'm not sure, let's try this in a small-safe environment" to "you/your-team sucks; you guys have a very poor agile maturity because you are not doing _x_y_z_ (not conforming to the standards)." Along the way, we've lost the purpose of being agile .i.e. to embrace uncertainty and simplicity. Instead we've been forced to believe that consistency via top-down standardisation and predictability by increasing the rigour on process is our eternal quest. Anything that sounds simple and works 80% of the cases is discarded as being naive. What once drove thought-leader into agile, is now driving them insane. This is the unfortunate fate of Agile.

Luckily there has been some fresh perspectives from Nassim Taleb, author of Antifragile. His work explains how some things benefit from shocks; they thrive and grow when exposed to volatility, randomness, disorder, and stressors and love adventure, risk, and uncertainty. More importantly why antifragility is beyond resilience or robustness.

In this talk, I'll use some of Nassim's thoughts (and some of my own) to explain what is wrong with our current approach to Agile and how we can bring life back into Agile. Particularly how we can leverage Volatility, Uncertainty, Complexity, and Ambiguity to make product development more antifragile.

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. Typical problems teams/orgs face today and how we deal with them 
    1. Problem
    2. Typical "Agile Response"
    3. Problem with the typical "Agile Response"
    4. Antifragile way to dealing with that problem
  2. We'll address the following problems: (5 mins each)
    1. Lack of requirements & complexity coming up with the right priorities 
    2. Difficultly breaking down work and putting together a realistic plan 
    3. Poor predictability and quality inspite of all the rigour in the process
    4. Lack of innovation
    5. Team members getting burnt-out
    6. Unhappy employees due to performance appraisal 
    7. Complex Polices
    8. Difficultly in scaling/sustaining good practices
  3. Q & A

Learning Outcome

  1. Understand how we can leverage Volatility, Uncertainty, Complexity, and Ambiguity to make product development more antifragile
  2. Appreciate the importance of trial-and-error / safe-fail experimentation
  3. Importance of Polar strategies
  4. Why layers of redundancy are the central risk management property
  5. Understand how simple, clear purpose and principles gives rise to complex and intelligent behaviour vs. complex rules and regulations give rise to simple and stupid behaviour
  6. Appreciate the #NoEstimation movement (any system based on prediction will blow up)
  7. Use procrastination to free you from the hassles of backlog management (#NoBacklog movement)
  8. How being metrics obsessed (micro-management) can hurt you
  9. Some ideas on how to make Performance appraisal a more meaningful afair

Target Audience

Agile Experts, Management Consultants, Leaders, Companies struggling with Agile

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal