3 ms·
> Is it so difficult to define deliverables and pay for completed and tested work It is? It's a problem as old as the hills — how do you measure the amount of
by 5e92cb50239222b 5y ago
> Is it so difficult to define deliverables and pay for completed and tested work
It is? It's a problem as old as the hills — how do you measure the amount of work done? I can churn out several new features in very short time, but then spend two days chasing a bug which results in a single-line fix. From the management POV this looks like I've been very productive for a few hours and then spent two days doing fuck all.
- mschuster91 5y agoIdeally you'd have a competent team lead that can evaluate whether people are bored out or overloaded with tasks and if their output quality matches expectations. JIRA, Trello or other tools are (usually) not used for the team's benefit, but as "actionable items" or whatever for clueless upper management.
- drran 5y agoThe manager then can look at data and think, "Hm, these bugs are costly. What we can use to reduce number of bugs to reduce costs?" Bugs are a waste. Number of bugs can be reduced with better practices: peer review, various tests; better software: linter, automatic verifier, compile time checkers (-Wall + -Werror, rust), code generators, libraries; or additional business process: quality assurance. To improve something, your manager need to measure it first. You can propose everyday reporting of spent time instead of spying tool, e.g. "2h working on #1234, 6h fixing bug #23456", which is much more valuable to your manager than raw data. In my previous company, we reduced the number of bugs and time to fix by an order of magnitude, because we were able to see the effect of changes in tooling and development process.