In a big org, and gov't is one of the biggest, people are very process focused. I'm okay with that. I love some processes: issue tracking, unit tests, continuous integration, one click deployments, automated quality metrics, etc. The thing that I get frustrated with is process without an apparent positive ROI.
One term that's been mentioned at work lately is "appropriate process" and I really like that. Process can be the best of things if it's appropriate. Filling out forms that are not checked against the actual product you are creating is not something that I would call "appropriate". That would fall into the "process for the sake of process" category. I think that is worse than no process at all because it's taking time / money away from actually doing something positive for the org.
Management is always asking for feedback. That's what they say at least, I'm still not sure if they actually mean it. What I would like them to do is come up with a business case for every "stage gate", "go / no-go decision point" and what ever buzz words of they day is being used.
Part of that business process would help you cost out all the parts of bringing something to prod. I wonder what percentage would be attributed to "process". 10%? 50%? 80%?
I want everyone that I work with, from the top to the bottom, to be "adding value". If you're not, well then at least get out of my critical path. I just want to route around the damage.
No comments:
Post a Comment