Stuck with the unending task of applying resources to fit deadlines of a project, what can you do other then beg for more resources (which will invariably be left with a negative response) or drop features from the project? Whilst some more resources have been given (two guys are starting within the next couple of weeks) one of the deadlines has been hastily moved forwards by the combined efforts of demands from customers, the result, a hastily re-drawn map of features and requriements diagrams alowing us to cancel features whilst still leaving us with enough product to move to the beta demoing stage.

The only thing to do now is move from the features based diagrams to the implementation diagrams. These cause me headaches - even though I know that no one diagram can succesfully describe the methods of displaying the code that will be written - class diagrams get horrendiously complicated when you start using more and more generic systems, and sequence diagrams begin to get horrendious when you have one per 'use' of the use diagrams. With seventy user features on the project, that leading to seventy diagrams is overkill, and it would be easier just to write the thing and write how it was written afterwards - but that would be bad now.