Doctrinaire Agile

From a distance, most Agile approaches are characterized by

  • small batches of work that are processed quickly by
  • a relatively autonomous team of cross-functional practitioners and a customer representative,
  • frequent face-to-face communication between team members, and
  • fast feedback on progress.

Yet some implementations are ineffective because of an unquestioning belief in the chosen approach. This doctrinaire[1] interpretation is identified by a stated belief in the enduring efficacy of the current Agile approach, or the absence of practices to assess and improve it. In other words, the absence of second loop learning.

Even worse is when there is absence of an assessment whether Agile is the right approach in the first place. Agile is most effective for work where there is a plausible hypothesis for the investment, changeable requirements and priorities, and unknown but knowable resources. When there are ambiguous or conflicting hypotheses, parallel safe-to-fail experiments may be more effective than the typically linear iterative Agile approach. When the requirements and priorities are known and relatively stable but it is not yet known how much capacity is needed, a timeboxing approach may be better. Finally, when the requirements and priorities are known and stable, and there is also enough experience to predict how much capacity is required, a waterfall approach could be surprisingly effective.[2]

[1] Stubbornly or excessively devoted to a doctrine or theory without regard to practical considerations (Merriam-Webster dictionary)

[2] Dave Snowden, frequently posited at Agile conferences


要查看或添加评论,请登录

Mark Smalley的更多文章

  • Digital philosophical intersectionality

    Digital philosophical intersectionality

    This is probably my most pretentiously-titled framework yet. Its aim is to help understand digital products and…

    7 条评论
  • Putting a man on the moon

    Putting a man on the moon

    The story is well-known: In 1962, when President Kennedy visited NASA, he asked a janitor what he was doing. The…

    1 条评论
  • Project health check

    Project health check

    Last year I had occasion to suggest that an organization should reflect on the health of a project. I gave them these…

    5 条评论
  • Employing digital

    Employing digital

    The modern workplace is increasingly shaped by digital technology. Whether employees are engaging with enterprise…

    2 条评论
  • Design doubts

    Design doubts

    My most recent book is IT service by design, written with Catherine Zuim Florentino. It’s a lovely book.

    9 条评论
  • Two IT tribes – bridging the differences

    Two IT tribes – bridging the differences

    This article applies Core Quality International's useful Core Quadrant model for personal growth to examine how teams…

    10 条评论
  • Experience revisited, again

    Experience revisited, again

    Just as I keep revisiting "service" and becoming increasingly ignorant of what it actually is, I have now revisited…

    1 条评论
  • Selling XLA to C-level – practical steps

    Selling XLA to C-level – practical steps

    I recently gave a talk about my Selling XLA to C-level book for one of my favourite ITSM communities, ITSMF Belgium…

    4 条评论
  • Product is not the solution

    Product is not the solution

    Over the past decade, software providers have made significant strides in shifting from a "project" to a "product"…

    14 条评论
  • Making “product” more productive

    Making “product” more productive

    In the world of IT, the term "product" is often confusing and therefore unproductive. From software applications to IT…

    36 条评论

社区洞察

其他会员也浏览了