Hacker News new | past | comments | ask | show | jobs | submit login

Let's say you have 2 developers:

- developer A wants to get promoted as quickly as possible. developer A will try to "ship" as many features as possible.

- developer B wants features to actually work, not just be "shipped". developer B volunteers to fix the problems developer A created by rushing to close as many tickets as possible.

Now, guess which developer contributes more to the team "velocity"? developer A. But in reality, developer A is just gaming the system and making everyone else slower. This is how agile distorts development.

Using velocity as KPI is the same as evaluating leaflet distributors by amount of leaflets distributed. Some will just throw them away in the garbage and claim their money.




Or do developer A and developer B make a good team? Looks like you've got a starter and a closer there to me.


Sometimes that is indeed the case.

In other cases you need a full rewrite, and that is not good.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: