On the Wrong End of the Camera

I was sitting quietly, in my favorite book café, working on my Strategic Navigation book (, only a few chapters left,) when a TV team from the Swedish Television burst in. It was a small team, but it jostled me out of describing how to create a Future Reality Tree.

Oh, gosh, I thought, they've heard of me! Finally, someone with the power of TV has decided to talk to me about management, TOC, John Boyd, Strategic Navigation, Systems Thinking, and How To Improve Life For Everyone. What a chance!

Turned out they were more interested in filming books than in filming an author. The camera remained firmly pointed in the opposite direction from me throughout their visit.

On the other hand, I think they did get some nice footage of the book café, and of the very nice people who work here. If you live in Sweden, you can see it all (except me of course) on Carin 21:30 at 21:30 on September 17th.

I did take a couple of photos with my iPhone. It's true what they say. The iPhone isn't the best camera in the world. Most of the pictures turned out a bit shaky.

I must confess, I was mostly interested in the camera setup. I guess its natural when you do webcasts.

Speaking of being on the wrong end of the camera: I have promised to help film pair-programming tomorrow. Will tell you more about it in a couple of days.

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

Are Nash Equilibriums Killing Agile Initiatives?

Image
Over the past two years I have seen a lot of debate about the success of Agile software development. Agile methodologies can produce great results. This is well documented. Yet, in many companies, they don't. This has lead many people to question Agile. Some reject it altogether. However, the root cause of the problem isn't in the Agile methodologies. The root cause that makes Agile fail is in the companies adopting Agile methodologies. Let's look back about ten years, when Agile was beginning to gather momentum. It was believed that if a company was functionally organized, like this: Introducing an Agile software development method in part of the organization like this: would cause everyone in the organization to reevaluate their strategies, so that the organization could reorganize into a flow organization, like this: It turned out not to be that simple. An important reason is that most business organizations are designed to be in a stable state. All major playe...
Read more