Always and unequivocally we achieve exactly the number of milestones my project manager of the month thinks I should be achieving. Luckily he/she/it doesn't have any way of measuring completion, nor do they usually have an understanding of what the milestone actually means. In fact on occassion when my PM changes I will make up a few milestones that were already complete and set those as my goals (when the PM actually lets us set our own goals/milestones). This gives me the time to go back and fix some rushed code. Luckily there is no actual plan for the project so there are no "real" milestones, the powers that be just seem to like knowing that milestones (real or imagined) are being reached.
btw I am being facetious and nothing in this indicates any real situation that exists (or in the past has existed) for me. I am always a dilligent worker, always climbing towards a well defined goal and never ever ever ever do I do any that would affect my PM's mental well being.
Although humorous, unfortunately I believe this is the real truth. The other extreme is the current project that I am working on, which has a single milestone - project complete. As one would expect, we have push that date around a few times.
If you could give a single piece of advice to your PM what would it be?
Regeretably, I have found that it is usually not the PM's fault. The fault usually lays in faulty requirements. Most PMs actually do the best they can with what they have. Also most of my PMs have been brought into the project late and usually aren't overly familiar with the project and most of the information was undocumented word-of-mouth.
My one piece of advice is simply either go back to programming or learn how to program. Most of my PMs have had very little programming experience and can only judge a project's progress on visible UI attributes (of course this also applies to their bosses). They then make the assumption that programmers are incredibly lazy because the front end progresses slower than the back end.
Is not innovation, really, incremental developments or revisions upon an idea? Innovation is a perception, the lightbulb, microwave, of the public. I, as a consumer, am not aware of the similar ideas that naturally point to the exisitance of the lightbulb; therefore, I precive a leap in knowlage -- Innovation.
Consquently, computers are awesome iteritive machines - if program to improve ideas existed, would they not come close to the innovative quality of humans?
You can only be young once. But you can always be immature.
- Dave Barry