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