This seems like a stupid thing for me to be struggling with after a dozen years in software development.
I need to do a better job measuring performance, and I feel like I can't even describe performance right now.
I'm a software development manager in a small software development shop.
We have two challenges, like most organizations. First is how quickly we can get features implemented into a software application. Second is how easily we can deal with diversions like customer support issues, non-feature oriented software changes (like infrastructure, documentation and testing) and bugs
At the core of this I continue to think that we should focus on performance and results vs just following a procedure.
At the moment when I think of performance I think of a relatively quick response to customer needs while reducing churn spent on re-work and setting pace in feature development as is reasonable so that bugs and other defects don't creep into our process.
But I'm having a tough time communicating to my directs and to my manager what kinds of goals/objectives our team should have and how we can turn this into measurable results.