Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Doomed to Fail

Doomed to Fail

Doomed to Fail: Why the Enterprise Needs to Stop Writing Checks that Can’t Be Cashed

Presented at #Agile2014

From the marketing materials:
Departments and teams are told what to deliver and when it will be done. They are there to meet the expectations set upon them (including those they haven’t yet been told about). Unfortunately, they often miss their deliverables and it’s getting in the way of expanding agile across the enterprise. Is it any wonder why some agile implementations struggle? The existing culture sets us up for failure!

It does not have to be this way. The problem isn’t your lack of control over other work groups, it is how they are treated. There are big differences between what a group promises to deliver and when they are voluntold to deliver. Every one is committed at some level, so stop treating other groups like chickens.

Using interactive exercises, we will demonstrate common situations and discuss how these problems look from multiple sides. Additionally, we will discuss the tools needed to deal with others who have a low reputation and what it takes to improve your own track-record.

Come to “Doomed to Fail” and learn how to recognize critical difference between prescriptive processes and managing promises between different groups in an organization. Learn how to ask for explicit promises so you can navigate through the enterprise maze to success.

Aside... If you're really curious, I am taking the concept of [Promise Theory](http://en.wikipedia.org/wiki/Promise_theory) and applying it to anti-patterns for enterprise-wide agile.


July 30, 2014

More Decks by Jeffrey

Other Decks in Technology


  1. Doomed to Fail Why  the  Enterprise   Needs  to  Stop

      Wri1ng  Checks  that   Can’t  Be  Cashed  
  2. •  Mark  Burgess,  In  Search  of  Certainty     • 

    Kent  McDonald,  beyondrequirements.com     •  Jeff  Sussna,  blog.ingineeringit.com     Resources  are  gathered  at:   •  h[p://goodrequirements.com/pt   References