Last Tempo! Appendix Written

Long time, no blogging. I have been writing though. I finished the last appendices in my business strategy book Tempo! today. There is still some work to do:
  • Some editing. Shouldn't be any major changes. Mostly fixing spelling.
  • Index the whole thing. This will take a bit of work. The book weighs in at about 350 pages. Not too difficult though, just a bit tedious.
  • Write a glossary
  • Make some cover prototypes. A real artist should do the final cover, but I wan't to sketch out some ideas.
  • Translate more chapters for my American and English proofreaders. I wrote Tempo! in Swedish. (In hindsight this was probably a mistake.)
You might be wondering what Tempo! is about. It is about a business strategy method known as Constraints Management, or Strategic Navigation. The method was created by Bill Dettmer and is an adaptation of John Boyd's Maneuver Conflict, with The Logical Thinking Process used as the primary planning tool. It is a dynamite package, especially for companies that are serious about turning the financial crisis to their advantage.

The book is meant to be a bit more than just a business strategy book. It is meant to serve as the foundation for a business version of IOHAI leadership training.

Sorry about the short and cryptic posting, but it is late. Just had to write a few lines about the book.

Comments

Anonymous said…
Hi Henrik!

The subject matter sounds really interesting! Will you release a public draft on the net, in order to get feedback? When will it be available in the book stores?
March 05, 2009 8:09 AM
Kallokain said…
Hi Staffan,
There won't be a public draft, but I will gladly send you and anyone else who asks for it a review copy.

Don't know when the book will be published. The Way these things go, there may well be an English edition before the Swedish one is out.

The book will get published though, even if it means self publishing.
March 05, 2009 10:01 AM
Anonymous said…
Henrik,

I am difinitely interested in getting a review copy and if needed, will provide payment in advance for the final published version. Please let me know the best way to arrange this.

Thanks,
Steve
March 05, 2009 5:19 PM
Kallokain said…
Hi Steve,
Sorry for not replying sooner.

No payment in advance necessary. Why not proofread instead? Cheaper, more fun, and you get your name in the book.

I do need your contact information though.
March 17, 2009 10:24 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