Timeline for What would a piecework-based payment system for software development look like?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 12, 2011 at 23:44 | comment | added | Michael Brown | The idea of story points is that over time you can measure a team's velocity in terms of story points. Taking the idea of gaming the system out of the conversation, it is possible to make a good estimate of how much work can be done within a consistent time box. Again if you know your velocity from trends, and you have honestly assigned points to more features, you can estimate to some degree of accuracy how much work can be completed in an upcoming equal timebox. | |
| Dec 12, 2011 at 22:45 | comment | added | user7519 | It has nothing to do with trust or the lack thereof, Story points were never designed for this application, there is absolutely no relation between stories of different points only stories of the same point values should be compared. Basing a compensation plan on this would just make all the stories 100000 point stories so the developers could pad the estimates and not lose out or game the system, it would be a disaster! | |
| Dec 12, 2011 at 21:34 | vote | accept | Stephen Gross | ||
| Dec 12, 2011 at 21:23 | comment | added | Michael Brown | Funny story, I was working with a group who wanted me to do some development for them. After a lot of foot shuffling, I said "Hey I can just work for equity on this project". Even then, there was a bunch of hemming and hawing and I just said forget it. After a year of prepping for the project and trying to convince them that I was in it to win it for them, there was still some fundamental mistrust that I just couldn't deal with anymore. | |
| Dec 12, 2011 at 21:20 | comment | added | Michael Brown | Yes there are difficulties in that arena. It all boils down to trust and partnership. It's a difficult situation here in America where the prevailing assumption is that the other guy is trying to screw you over. In the end, you end up going back to T&M or Waterfall development where everything has to be cemented before a line of code is written. | |
| Dec 12, 2011 at 21:01 | comment | added | user7519 | this is a slipperly slope, because Story Points are estimates and can be wildly off when more details come to light as implemenation happens. 5 point stories can become 30 point stories over night, this is expected. Tying compenensation to the number of points will only cause big stories to get short changed and implemented in the quickest amount of time with quality suffering. | |
| Dec 12, 2011 at 20:56 | history | answered | Michael Brown | CC BY-SA 3.0 |