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 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

Performance Evaluations, Business Strategy, and Agile Methodologies

Image
It is performance evaluation time in many companies. This can be stressful, both to the people being evaluated, and the people doing the evaluation. In companies adopting agile software development methods, the tension can be extraordinary. Individual performance evaluations run counter to agile philosophy, which emphasizes team performance over individual performance. However, managers and corporate leaders need to take a few steps back, and consider the impact performance evaluations have on the organization as a whole. Especially now, in the midst of a recession, it is important to look at a companies current policies to see if they can be improved, or if they are actually holding the company back. So, how can a manager evaluate policy? Performance evaluation policies can serve as an excellent example. I'll confine myself to discussing the so-called ‘rank and yank’ methods. These are performance reviews were employees are ranked using a forced ranking system. It usually looks so...
Read more

Agile Requirements Structures, Part 1

Image
If you have worked in large Agile projects or programs, you may have noticed that there is often quite a bit of confusion about requirements, what the requirement types are, their purpose, how to write them, how to use them, and above all, what not to do with them. There are many causes for this confusion. Here are some of the more common I have seen: Nobody in the organization has read up on the requirements model it is using, so everyone makes their own interpretation. The organization deviates from a standard requirements model, but nobody knows which standard model the organization is deviating from, and/or there is no agreement about how they deviate from it. The organization has not documented its own requirements model very well. The organization mixes two or more different requirements models, often without realizing it. The organization has documented its requirements model, but finding the documentation is an epic project in itself, on par with when Henry Sta...
Read more