Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I suppose there's no straight answer to this, but what ideas come to mind for determining how much each programmer would get for participation in a collaborative project if it were to be sold?

share|improve this question
add comment

closed as not constructive by pdr, Walter, Ryathal, gnat, psr Aug 17 '12 at 23:05

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

4 Answers

up vote 7 down vote accepted

I think there is only one good answer: What you agreed upon before you started the work. If such things are clear from the start and people know what to expect there will be much less bad blood then if you make up some arbitrary rules when the product launches and you suddenly find out you have a pile of money to divide.

share|improve this answer
add comment

I think there is only one good answer: the same share. Of course you can try to differentiate it by the effort that each programmer has put into creating the application, by the number of hours, by their skills and experience, etc. But you won't be able to measure it reliably and you won't be able to define such rules that all team members will be happy with them. So try to get guys who have similar experience and will spend similar amount of time of the project. If some of them decide to quit before the project is finished, they just don't get their share.

share|improve this answer
    
I think there would be problems with this approach if some people are putting in a lot more effort than others. –  Bob Horn Aug 9 '12 at 13:03
    
This will be an open invitation to dirty games, ditching developers or getting friends on board close to launch. –  Pieter B Aug 9 '12 at 13:06
    
In theory yes, but in practice it never works this way. All the team members put similar effort in the project, and if someone cannot keep up, he just leaves. It looks like this both for the programming teams and for rock bands. ;-) –  rmaruszewski Aug 9 '12 at 13:16
    
In practice the teamlead will bring his underperforming girlfriend on board being blinded by love. Been there, done that, it wasn't pretty. –  Pieter B Aug 9 '12 at 13:29
add comment

It is basically depend on task(s) complexity, assigned to each developers.

Each task has difference or similarity in terms of completion time and complexity. Thus, you may need to have a complexity level determined for each task with some rough hours of expected completion. That will guide you over the process to determine the input of each project participant.

Who may determine the complexity level? - Well there should be at least Team Lead and PM in that group who defines task complexity and timing.

share|improve this answer
add comment

I think it's important to define the roles and percentages before the project starts. Since I don't know what those roles are on the project, I can only make up my own here.

Scenario 1: Everyone puts in the same amount of effort and has the same skill level.
Answer: Divide the share equally.

Scenario 2: Some developers don't spend all of their time on the project, and some developers perform easy/simple tasks:
Answer:
Team Lead: n%
Full-time developers: n%
Part-time developers: n minus x%
Part-time QA: n minus y%
Part-time documentation writers: n minus z%

This could continue for all of the different scenarios available. You (and/or the team) will need to make your decisions as to what n, x, y, and z represent. The important part is to define all of this up front, and agree on relative percentages based on the role.

share|improve this answer
1  
Rather than a n%, which can be awkward and change as one brings more people on the project, what about shares? For example, team lead makes 11/day. Developers make 10/day. QA makes 9/day. Documentation makes 5/day. At the end calculate the total number of shares allocated and divide it up that way. –  MichaelT Aug 9 '12 at 13:41
    
I like that. The main point is still that those who deserve more, get more. I guess that's really my whole point. –  Bob Horn Aug 9 '12 at 13:47
    
I don't like "deserving" it's too often a can of worms: "everyone who spends the same amount of time 'deserves' the same share" vs "I'm twice as good as my co-worker I 'deserve' twice his pay". 'Deserve' is highly subjective and therefor a bad measurement. –  Pieter B Aug 9 '12 at 13:55
    
So a senior developer, making architectural and major design decisions, should get the same amount as a junior developer? –  Bob Horn Aug 9 '12 at 14:00
    
I listed those two uses of deserves to describe a conflic, not as a desired situation. –  Pieter B Aug 9 '12 at 14:03
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.