If the time between the last milestone and end date is not too long, you could put in some sort of 'handover' mini project, I.E. getting everything to a recognisable clean edge for somebody (who could be you if it renews) to take over the project.
HTH.
-
Project Schedule
Looking for some comments / advice on project schedules. After some negotiation with the agency (with a lot of help from B&C) I've finally managed to get a proper project-based contract issued. All well and good.
However, along with the contract, the agency attached a default project schedule which simply had deliverables listed as "software engineer" and milestones as "N/A". Now that strikes me as being the square root of useless and anyway that doesn't reflect the contract as it is very definately project-based. I have drafted a new schedule (with the client's blessing) listing (non-confidential) project details and milestones which occur before the end date of my current contract.
So far so good. However what I'm currently uncertain of is how to account for the remainder of my time after the last milestone. There are further project milestones on the client's plan however these fall after my contract end date. I'm uncomfortable about putting these on the schedule as it seems to suggest ongoing work and hence an extension. Equally leaving a gap between the last milestone and the contract end date also feels wrong. I don't want to seed my own minefield, what would you do?
Leave a comment: