The Reality Dysfunction


I was asked to submit a presentation proposal to Stop Starting, Start Finishing, the Lean Kanban Nordic conference, 12-13 Mars, 2013, so I did:


If the proposal gets enough votes, I'll get to hold the presentation.

Here is the proposal:

Tempo!: The reality Dysfunction puts the fun back in dysFUNctional. 
How did we end up with so many dysfunctional companies? To fix the problems we face today, we must understand the causes. 
Tempo!: The Reality Dysfunction is a romp through the wild side of management history: It starts with a bang, a train crash the 5th of October 1841, with consequences that cause companies to fail in 2013. 
You will meet the unbeatable fighter pilot, who also figured out how to build an unbeatable organization. You will see what managers must know to lead an Agile development team. 
You will see how most companies are applying fundamental principles of strategy, psychology, and physics backwards, and hurt and disable themselves in the process. You will also find out what to do about it, and who has already succeeded. 
There will be a practical demonstration, with members of the audience, showing how a simple restructuring of work can reduce lead times by 60% or more, while increasing quality. 
And, you will have fun!
Serious enough to get your vote? You should of course check out the other proposals before you vote, so you can pick the ones you are most interested in. (You get 10 votes, and you can put up to 3 votes on any one proposal.)

Comments

Post a Comment

Popular posts from this blog

Waterfall - The Dark Age of Software Development Has Returned!

Image
  I honestly beleave it iz better tew know nothing than two know what ain’t so. — Everybody’s Friend, 1874, by Josh Billings To my horror, more and more often the past few years, I have seen people advocating for using the Waterfall method of software development. I have also seen it in job descriptions, for example “we use a mix of Agile and Waterfall”. Why am I horrified? Because Waterfall was never intended to become a software development method. Waterfall is now, as it was from the beginning, a way to describe why many large software development projects fail. There is no scenario where Waterfall is a good approach to software development ! To back up that statement, let’s go back to the origin of Waterfall, a whitepaper by Dr. Winston Royce, Managing the Development of Large Software Systems from 1970. The Origin of Waterfall Note : The origin of Waterfall goes back quite a bit further than 1970. In another, later article, Waterfall vs. Agile: Battle of the Dunces or a Rac
Read more

Waterfall vs. Agile: Battle of the Dunces or A Race to the Bottom?

Image
The major software methodology wars since the mid 1950’s. Someone was wrong on the Internet, so here we go… In a recent HBR article, It’s Time to End the Battle Between Waterfall and Agile , the author sets up a false premise: There is a war between Waterfall methodology and Agile. The war must end. And finally, you can combine the approaches to get the best of both worlds. This sounds good, but the article is based on a misunderstanding of both Waterfall and Agile. Also, there is no war between Waterfall methodology and Agile. There can’t be, because Waterfall methodology does not exist! Waterfall is a name for large projects that failed in the 1960’s. Waterfall was never a methodology, but a failure to apply the methodologies that existed back then. As I will show towards the end of this article, at least one of the “successful” Waterfall projects mentioned in the HBR article was neither successful, nor a Waterfall project. I got invaluable help from Alistair Cockburn. He fact che
Read more

Interlude: The Cost of Agile

Image
  Agile software development requires significant long term investments in developer skill. Most “Agilists” choose not to talk about it. I had just begun working on part four in my three part blog post series Are You Still Using the Wrong Control Levers in your Agile projects? , when I found myself writing a section about agile project economics. The section was rather long, and didn’t quite fit with the rest of part four, so I decided to break it out, and make it a separate blog post instead. This is it! I do hope you enjoy reading it. In case you wonder why there are four parts (five if you count this interlude) in a three part blog post series, well, requirements changed, and the scope increased… Agile methods have great benefits, both in human, and economic terms. There are also costs. Thus, going agile, if it is done seriously, requires thinking a bit about the trade-offs that must be made. Most companies don’t consider the trade-offs. What they do is they set up an “Agile tr
Read more