|
|
|
|
|
by fleitz
5724 days ago
|
|
The one thing about large enterprise projects is though, you can usually convince the mismanagers that it's good for their career, and the mismanagers end up disliking the competent programmers. If you're a vulture or a hyena a large IT project can become like a elephant corpse, easy pickings. Convince the mismanagers to move competent people to your team in exchange for your yes men. Then find a piece of infrastructure you need for your project and offer to build it for the larger project. This is basically an excuse to use their infrastructure, db servers, test servers, etc. Use this to get buy in to slip your own schedule so you have time to deal with the inevitable feature creep. Go to the design and planning meetings and suggest new and exciting technologies that they can figure out. When it doesn't work, take the hardware they req'd off their hands for the infrastructure you offered to build them. Make sure you integrate your project to the infrastructure first (you can always pitch it as reducing risk to the large project) so they can't make any changes to it with out breaking production code. |
|