HACKER Q&A
📣 ss_y2n

Any tools for measuring engineering/development process?


Tools that may help Engineering Manager or CTO in small or mid size teams to build cadence around measuring delivery, output and align teams.

May be also help in onboarding and off-boarding new team members.


  👤 troydavis Accepted Answer ✓
Before implementation (and probably before choosing who does what), have the engineering team(s) estimate effort required for each granular work item in their upcoming release/sprint/month/whatever. Afterwards, you’ll have a measurement of velocity. Pivotal does this with Tracker so they’ve documented it: https://www.pivotaltracker.com/help/articles/planning_with_v..., https://www.pivotaltracker.com/blog/healthier-approach-estim...

Note that, as they say, “Velocity is a planning tool, not a goal or a competition. Quality is a much healthier and more useful goal.“ However much effort you spend caring about velocity, spend many times as much caring about quality - code/implementation choices, UX, resulting impact to the product/business, etc.


👤 PaulHoule
Read

https://www.amazon.com/Software-Estimation-Demystifying-Deve...

and

https://www.amazon.com/Rapid-Development-Taming-Software-Sch...

Also think: if the business does project A, how much money does that make for us or save for us? From a developer standpoint I have gotten the business people to tell me a value that is a fraction of the cost of the product. You fold that one and free up resources for project B which is the other way around.


👤 tzvsi
Pinpoint is solving for this

https://pinpoint.com