The Reality Dysfunction - Presentation at Stop Starting, Start Finishing

The nice people running the Stop Starting, Start Finishing conference in Stockholm the 12-13 of Mars 2013 asked me if I was interested in holding a presentation.

Of course I am.

I am hard at work on my presentation. Here is what I am going to talk about:


Tempo!: The Reality Dysfunction
Henrik Mårtensson

Henrik Mårtensson
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 percent or more, while increasing quality. And, you will have fun!
Henrik Mårtensson is a business strategy coach, process developer, and project leader. He is also an author and presenter. Henrik began working with Extreme Programming, an agile software development method, in 2001. His interest in methodology quickly brought him to Lean, Theory Of Constraints, Statistical Process Control and Systems Thinking. Several years ago, Henrik got into contact with Strategic Navigation and a military strategic framework, Maneuver Conflict. Suddenly, all the pieces fit together.
Tempo!, Henrik's first book on business strategy, was published in 2010. His second book, LESS!, published in 2012, is a collaboration between twelve thought leaders in Agile, Lean, Beyond Budgeting, Strategic Navigation, Systems Thinking, and Complexity Science. 

Comments

Tobias Fors said…
Henrik, by the sound of it, this will be an awesome presentation. I won't be there to hear it, so I'm hoping there will be a recording made!
January 16, 2013 8:03 PM
Kallokain said…
Hi Tobias,

I will either make a video at the conference, or make a video of the same presentation later. Depends on which solution works best. :-)
January 20, 2013 11:26 PM
Tobias Fors said…
How did the talk go? Is there a video? /T
March 20, 2013 4:02 PM
Kallokain said…
The presentation went very well. I haven't done a video yet. I will probably have to reshoot the whole thing, because I didn't have a camera operator available at the conference.
March 22, 2013 12:32 AM
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