Have We Reached Peak Agile?

TL; DR: Have we reached Peak Agile?

There has never been a shortage of articles claiming that Agile is either dead, failing, disrespectful, or useless, with authors ranging from respected signatories of the Agile Manifesto to click baiters to people who never experienced the real thing in the first thus lacking a standard for comparison. (See the links below.)

The question from my perspective, though, is: Have we finally have reached peak agile?

Have We Reached Peak Agile? Age-of-Product.com

Share your opinion and join the discussion on LinkedIn.

Continue reading Have We Reached Peak Agile?

Faking Agile Metrics or Cooking the Agile Books

TL; DR: Faking Agile Metrics — An Eye-Opening Exercise

Imagine you’re a Scrum Master and the line manager of your team believes that the best sign for a successful agile transformation is a steady increase in the Scrum Team’s velocity. Moreover, if the team fails to deliver on that metric something is wrong with the Scrum Team. Alternatively, something is wrong with you as you are the Scrum Master and hence responsible for the team’s performance. (Apparently, not faking agile metrics, or being transparent in this case, does not seem to be valued here.)

Learn more about how to coach these kinds of line managers and help them overcome their preference for the industrial past with a simple exercise on how to cook the agile books.

Faking Agile Metrics or Cooking the Agile Books — Age-of-Product.com

Do you want to get this article in your inbox? You can sign up here and join 24k other subscribers.

Continue reading Faking Agile Metrics or Cooking the Agile Books

Speaking Truth to Power — Taking A Stand as an Agile Practitioner

TL;DR: Speaking Truth to Power

Do you need an emergency fund as a change agent—whether you are acting as Scrum Master, Product Owner or agile coach—because conflict is inevitable, but change is not?

In my experience, speaking truth to power, pointing at the emperor’s new clothes and the reality in the trenches, is necessary a trait for every change agent — including Scrum Masters and agile coaches — in organizations that lack strong leadership.

Learn more, how this form of professional honesty can backfire when the incumbents, privileged by the existing system, strike back.

Speaking Truth to Power — When the System Strikes back

Continue reading Speaking Truth to Power — Taking A Stand as an Agile Practitioner

Webinar #4: Agile Failure Patterns 2.0 [Video]

TL;DR: Webinar Agile Failure Patterns 2.0

The fourth Hands-on Agile webinar agile failure patterns 2.0 addressed why ‘agile’ is not the quick fix for dysfunctional organizations.

Hands-on Agile Webinar Agile Failure Patterns 2.0 — May 22nd, 2018

Continue reading Webinar #4: Agile Failure Patterns 2.0 [Video]

Ebookmakr Failure: The Fallacy of Knowing What to Build – The Post Mortem

Executive Summary – Lessons Learned from Ebookmakr's Failure:

  1. Love the problem more than your solution.
  2. Don’t push too far your dreams of China in your hand.
  3. Use prototyping tools such as Marvel when running user interviews. (More here: Four Lessons Learned From Making Customer Value Your Priority.)
  4. Be careful with the selection process for user interviews: You might end up picking those that will support your vision – it’s a self-fulfilling prophecy trap.
  5. Beware of false positives in user interviews.
  6. Never start writing a single line of code before an appropriate number of customers signed up. (For clarification: Customers are paying users.)
  7. Never spend money on developing a prototype when you’re not working full-time on growing the user-base and increasing customer value.
  8. Be patient and give your product the time it needs.
  9. Always make branded t-shirts and wear them later regularly to preserve the recollection of the disaster. (See below.)
Continue reading Ebookmakr Failure: The Fallacy of Knowing What to Build – The Post Mortem