3 ms·
There was some Mixergy interview where the guy at IMVU or somewhere was saying that it was trendy to measure progress the Agile way, by lines of code written, w
by lsb 16y ago
There was some Mixergy interview where the guy at IMVU or somewhere was saying that it was trendy to measure progress the Agile way, by lines of code written, whereas it was more accurate a metric to measure progress by learning.
- dmoney 16y agoI used to work at a company where they did Scrum. We never measured progress by lines of code. The way they measured progress was: 1. Start with "User Stories", or things you want the software to do for your users. 2. Assign each story a difficulty ("Story Points"). 3. Work in iterations ("Sprints") of two weeks or so. 4. Your total accomplishment is the Story Points of the User Stories you complete, and your productivity ("Velocity") is story points completed per sprint. I didn't think this was a good system, as difficulty varies with experience and tools, and so if you're more productive new stories will be assigned smaller story point values. So you're really only measuring how hard you work, rather than the value you create. Maybe they use lines of code in other forms of agile.
- derefr 16y agoI think a decent analogue of "lines of code written" would be "number of public methods with unit tests" (i.e. the size of your stable API.)