3 ms·
It sounds like they want to control something that works so they can claim credit, or at least reap the rewards. I went through this a couple years ago. It's p
by roedog 16y ago
It sounds like they want to control something that works so they can claim credit, or at least reap the rewards. I went through this a couple years ago. It's painful.
I worked on a system that we had deployed and that was working. A competing group, highly process oriented, who were was still generating requirements paperwork, but not a single line of code. Their objective was to take over our project. They played mean politics. Eventually they took charge.
- matwood 16y agoYeah, taking credit is definitely a big part of it, but it's more than that. By simply doing what we do we keep making other groups in the company look horrible. I don't think we're all-stars, but in big corporations it seems that just doing your job with a results minded attitude easily sets you above the rest. Also, don't think we anti-process :) I'm a stickler for SCM and testing, but we operate in an agile manner. Most projects start out with a 'hey, this would be cool' and then we iterate based on user feedback. Early on code changes can roll out daily, while the new process wants us to bundle our code and hand it to a 'deployment team' who might take 2 weeks to get around to deploying. How this is acceptable is beyond my comprehension, but it might explain why other groups never seem to deliver anything (or put 6 months on any timeline). I told my boss today that if this goes through that it will likely destroy what makes us so successful and he agreed. I'll just look at it as motivation to work harder on my own ideas and maybe once and for all escape ;)