3 ms·
If it can't be measured, it can't be managed. Remember that your manager is accountable to someone else higher up the chain. They don't know how dev works, but
by bitwize 10y ago
If it can't be measured, it can't be managed.
Remember that your manager is accountable to someone else higher up the chain. They don't know how dev works, but they want to see quantifiable progress. Statistics, spreadsheets, and tools like Jira are how that progress gets communicated. Like it or not, this is an essential part of the business.
- Aqueous 10y agoYes, it is important. However, some project managers obsess over it. Instead of focusing on delivering something the client wants and finds valuable they obsess over estimates, minimizing change orders, and time spent, to the point where it becomes the single determining factor in what we do and don't do. It's important to be on time. I've found that it's more important to solve the client's problem. And if you solve the client's problem well enough, the client will give you flexibility on the time.
- quantumhobbit 10y agoThe best measure of how a project is going is using the software it is producing. Instead of using questionable data from Jira and the like, just try to use the software. Ask for a demo, or run the code yourself, or look through unit and acceptance tests.
- bitwize 10y agoDirect supervisors can do that and get a detailed feel for how it's going. But that's too touchy feely, too many variables. C-level execs want to know "are we on track to ship version 3.0 by the end of the quarter?" and they need a yes/no answer, justified by numbers and graphs. They don't know about unit tests, and can't be bothered to walk through the software itself.