[A lack of] Project Management

Suddenly this weekend, a project at work, which had been back-burnered for all of Q3 2004, became a screaming hot topic to be completed ASAP.
This is not much of an issue, as the code that needs to be written will consist of re-using a group of functions that I have already developed and refined. What is curious is that they decided to expose the document used to define this specification to more than one customer. At the time of the initial scope definition for the project, this was to be for a partner who we had developed a contractual relationship with, including and SLA. Now management has decided that exposing this document to other customers, who can then also hold us to the same SLA, is a good idea.
Sometimes I wonder what I have gotten myself into.

Leave a Reply

Your email address will not be published. Required fields are marked *