There is usually a long story behind a successful product. This applies for Merlin and my first visions about it in 2003.
Was Merlin a project manager? (part four)
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?