Hello 2010, bye bye 2009!

One lays a bit longer in bed at Christmas, and finds the new year already in full swing when awaking. But wait. Our hibernation was not that deep, we simply granted ourselves a short break. 2009 was after all the most active year in our young history.

Directly on its begin, January 2009, we were in the Macworld and presented Merlin iPhone to the interested visitors.

In February 2009 the beta test of Merlin 2.7 started containing the new version of Merlin Web. A Merlin Twitter presence was also created, with over 750 followers meanwhile.

Continue reading

Was Merlin a project manager? (part four)

There is usually a long story behind a successful product. This applies for Merlin and my first visions about it in 2003.

Here is how the drama started. Here and here how it continued.

Was Merlin a project manager? (part four)

By the way, the product name “Merlin” was defined even before the first code line was written. We were ProjectWizards; our software simply had to bear a name of a magician. We have many names from the Arthurian legend in use, so the decision was not very far-fetched.
Exactly like the legendary figure Merlin, Arthur’s magician advisor, should our Merlin be a wizard and advisor for project management. There was no necessity in finding a good name considering marketing aspects. Merlin was meant to be sold only to selected partners. Pretty naive…
Frank Illenberger and I held our first kick-off-meeting on November 9th 2004 in Frankfurt. We had talked about the concept, answered questions and mentioned ideas. Frank intended to work two days per week on programming Merlin. We defined a vague target date, as none of us had ever worked on a similar project. At that time Frank had experience on only small programs. Have I mentioned how naive we both were?
Anyway, thanks to Frank’s analytical and meticulous way of working, Merlin’s development took form really quickly. Small and major crises got handled as they appeared.
July 2004 was a watershed event. Apple sent me an invitation to the Apple Expo in Paris. I should present Merlin. Fine, I thought, I would be delighted, but how did Apple come to know about Merlin’s existence? Our Merlin project team had grown meanwhile to 20 persons. Some more involved than others. All of them had signed an NDA but one of them had definitely “blabbed”.
So I flew to Paris to hold a Merlin presentation. Michel Suter greeted me with “I have no more than 20 minutes time”. I started my well-prepared presentation. Michel interrupted me after ten minutes and asked with enthusiasm for the scheduled release date. I tried to explain that we are not planning to release Merlin. His reaction was pretty direct: “I would deserve to get beaten if I would not make such a great program available to all Mac users”. Okay, the message was clear enough. During my flight back to Germany I setup a business plan. The decision was taken: Merlin should be available for the public. The rest, as they say, is history… I do not regret my decision, not for a moment.
Merlin 1.0 was released on November 9th 2004. It was the starting point of the currently most successful project management software. So it seems, we managed to do more things the right way than wrong.

The product name Merlin was defined even before the first code line was written. We were ProjectWizards; our software simply had to bear a name of a magician. We have many names from the Arthurian legend in use, so the decision was not very far-fetched.

Exactly like the legendary figure Merlin, Arthur’s magician advisor, should our Merlin be a wizard and advisor for project management. There was no necessity in finding a good name considering marketing aspects. Merlin was meant to be sold only to selected partners. Pretty naive…

Frank Illenberger and I held our first kick-off-meeting on April 9th 2004 in Frankfurt. We had talked about the concept, answered questions and mentioned ideas. Frank intended to work two days per week on programming Merlin. We defined a vague target date, as none of us had ever worked on a similar project. At that time Frank had experience on only small programs. Have I mentioned how naive we both were?

Continue reading

Was Merlin a project manager? (part three)

There is usually a long story behind a successful product. This applies for Merlin and my first visions about it in 2003.

Here is how the drama started.

And this is how it continued.

Was Merlin a project manager? (part three)

…It was decided, we would get someone to write a piece of software just for us. As mentioned before, we were not developers so could not do it on our own. The creation of a first concept was quickly completed. Our own partners and customers helped us on its definition. My intention was to refinance the project through the sale of software licenses to selected customers. I was even thinking, that with a bit of luck, our own license could even be free. Pretty naive…

Continue reading

Was Merlin a project manager? (part two)

There is usually a long story behind a successful product. This applies for Merlin and my first visions about it in 2003.

Here is how the drama started.

Was Merlin a project manager? (part two)

….We were looking for alternatives. Someone in the company started to [ab]use MS Excel as a project management tool. In the beginning I found this to be a good idea, and followed willingly. Some weeks later we had scripted a great amount of data sheets with innumerable charts. It was fine for separate projects but made our overview on all running projects smaller day by day. When colleagues began again to do their job manually, bypassing the scripts and their automations, it became clear to me that we needed yet again another, better solution.

Continue reading

Was Merlin a project manager? (part one)

There is usually a long story behind a successful product. This applies for Merlin and my first visions about it in 2003.

But first things first. Back in 2002, founding ProjectWizards, I decided to switch to Mac OS X. It was a relatively new operating system based on NeXTSTEP, which Apple bought and developed further. The excellent quality that Apple machines had, and still have, was one of the main reasons for switching. With MS Office X, we had a good basic software package for daily work. And even though Word, Excel and PowerPoint on Mac were always a step behind their Windows versions, they contained the functions we needed. Last but not least they offered a relatively good compatibility to Windows files. All this was necessary for our job at ProjectWizards; Project management. And here is where the drama starts.

We tried at first FastTrack Schedule by AEC. It was the only Mac OS X application for project management available, with all limitations and problems of a classic OS 9 application. The software had some inconsistencies making its professional use by ProjectWizards impossible.

The next step wasn’t any easier. Virtual machines were not performing well on PowerPC based Macs, so MS Project on MacOS X was not an option. We had tested Windows machines with terminal server, accessed by “remote desktop”. But this was not really a better solution either…

– To be continued –