Mixing
How to measure how many working days would need by other experienced programmer reproducing sourcecode? [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
-4
down vote
favorite
I have made a framework and for selling / pricing objective I need to estimate the required working days other, on the specific field experienced programmer would use to reproduce it.
I thought I will just trace back in version control system how many days I was working on that special code, but I made several refactoring, I dealt with code though several iteration, experimenting framework took me a long time, and I want to know time it requires to copy and not to create framework.
How would a CTO specify the amount of work to be done in one working day?
How would a CTO specify the amount of working days a feature, programming module requires?
What is the expected number of code lines / added number of method / function point CTO can expect to be done in one working day?
is it any accepted measurement for it or measuring is heuristic?
performance
asked Oct 9 '14 at 5:35
János
965
closed as too broad by Jim G., gnat, Garrison Neely, IDrinkandIKnowThings, David S. Oct 13 '14 at 7:15
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
suggest improvements |Â
up vote
-4
down vote
favorite
I have made a framework and for selling / pricing objective I need to estimate the required working days other, on the specific field experienced programmer would use to reproduce it.
I thought I will just trace back in version control system how many days I was working on that special code, but I made several refactoring, I dealt with code though several iteration, experimenting framework took me a long time, and I want to know time it requires to copy and not to create framework.
How would a CTO specify the amount of work to be done in one working day?
How would a CTO specify the amount of working days a feature, programming module requires?
What is the expected number of code lines / added number of method / function point CTO can expect to be done in one working day?
is it any accepted measurement for it or measuring is heuristic?
performance
asked Oct 9 '14 at 5:35
János
965
closed as too broad by Jim G., gnat, Garrison Neely, IDrinkandIKnowThings, David S. Oct 13 '14 at 7:15
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
3
This question appears to be off-topic because it is about programming.
– Jim G.
Oct 9 '14 at 6:31
1
in stackoverflow they said it is not programming but performance of employee
– János
Oct 9 '14 at 10:20
Work estimation is not programming, it's Workplace. You are right to post here.
– Ross Drew
Oct 9 '14 at 11:51
@RossDrew: Work estimation in the abstract is on-topic. Specific guidance about work estimation as it pertains to programming is not. Steve McConnell wrote an entire book on the work estimation for programming. It's that specialized. amazon.com/Software-Estimation-Demystifying-Developer-Practices/…
– Jim G.
Oct 9 '14 at 14:09
2
He wrote a book on Software Estimation. Software is made up of programming but software isn't programming. Software estimation is infrastructure, planning, design, programming and testing. He's asking for working days, not working days spent specifically on programming.
– Ross Drew
Oct 9 '14 at 14:37
suggest improvements |Â
up vote
-4
down vote
favorite
up vote
-4
down vote
favorite
I have made a framework and for selling / pricing objective I need to estimate the required working days other, on the specific field experienced programmer would use to reproduce it.
I thought I will just trace back in version control system how many days I was working on that special code, but I made several refactoring, I dealt with code though several iteration, experimenting framework took me a long time, and I want to know time it requires to copy and not to create framework.
How would a CTO specify the amount of work to be done in one working day?
How would a CTO specify the amount of working days a feature, programming module requires?
What is the expected number of code lines / added number of method / function point CTO can expect to be done in one working day?
is it any accepted measurement for it or measuring is heuristic?
performance
asked Oct 9 '14 at 5:35
János
965
I have made a framework and for selling / pricing objective I need to estimate the required working days other, on the specific field experienced programmer would use to reproduce it.
I thought I will just trace back in version control system how many days I was working on that special code, but I made several refactoring, I dealt with code though several iteration, experimenting framework took me a long time, and I want to know time it requires to copy and not to create framework.
How would a CTO specify the amount of work to be done in one working day?
How would a CTO specify the amount of working days a feature, programming module requires?
What is the expected number of code lines / added number of method / function point CTO can expect to be done in one working day?
is it any accepted measurement for it or measuring is heuristic?
performance
asked Oct 9 '14 at 5:35
János
965
asked Oct 9 '14 at 5:35
János
965
asked Oct 9 '14 at 5:35
János
965
asked Oct 9 '14 at 5:35
János
965
965
closed as too broad by Jim G., gnat, Garrison Neely, IDrinkandIKnowThings, David S. Oct 13 '14 at 7:15
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by Jim G., gnat, Garrison Neely, IDrinkandIKnowThings, David S. Oct 13 '14 at 7:15
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
3
This question appears to be off-topic because it is about programming.
– Jim G.
Oct 9 '14 at 6:31
1
in stackoverflow they said it is not programming but performance of employee
– János
Oct 9 '14 at 10:20
Work estimation is not programming, it's Workplace. You are right to post here.
– Ross Drew
Oct 9 '14 at 11:51
@RossDrew: Work estimation in the abstract is on-topic. Specific guidance about work estimation as it pertains to programming is not. Steve McConnell wrote an entire book on the work estimation for programming. It's that specialized. amazon.com/Software-Estimation-Demystifying-Developer-Practices/…
– Jim G.
Oct 9 '14 at 14:09
2
He wrote a book on Software Estimation. Software is made up of programming but software isn't programming. Software estimation is infrastructure, planning, design, programming and testing. He's asking for working days, not working days spent specifically on programming.
– Ross Drew
Oct 9 '14 at 14:37
suggest improvements |Â
3
This question appears to be off-topic because it is about programming.
– Jim G.
Oct 9 '14 at 6:31
1
in stackoverflow they said it is not programming but performance of employee
– János
Oct 9 '14 at 10:20
Work estimation is not programming, it's Workplace. You are right to post here.
– Ross Drew
Oct 9 '14 at 11:51
@RossDrew: Work estimation in the abstract is on-topic. Specific guidance about work estimation as it pertains to programming is not. Steve McConnell wrote an entire book on the work estimation for programming. It's that specialized. amazon.com/Software-Estimation-Demystifying-Developer-Practices/…
– Jim G.
Oct 9 '14 at 14:09
2
He wrote a book on Software Estimation. Software is made up of programming but software isn't programming. Software estimation is infrastructure, planning, design, programming and testing. He's asking for working days, not working days spent specifically on programming.
– Ross Drew
Oct 9 '14 at 14:37
3
3
This question appears to be off-topic because it is about programming.
– Jim G.
Oct 9 '14 at 6:31
This question appears to be off-topic because it is about programming.
– Jim G.
Oct 9 '14 at 6:31
1
1
in stackoverflow they said it is not programming but performance of employee
– János
Oct 9 '14 at 10:20
in stackoverflow they said it is not programming but performance of employee
– János
Oct 9 '14 at 10:20
Work estimation is not programming, it's Workplace. You are right to post here.
– Ross Drew
Oct 9 '14 at 11:51
Work estimation is not programming, it's Workplace. You are right to post here.
– Ross Drew
Oct 9 '14 at 11:51
@RossDrew: Work estimation in the abstract is on-topic. Specific guidance about work estimation as it pertains to programming is not. Steve McConnell wrote an entire book on the work estimation for programming. It's that specialized. amazon.com/Software-Estimation-Demystifying-Developer-Practices/…
– Jim G.
Oct 9 '14 at 14:09
@RossDrew: Work estimation in the abstract is on-topic. Specific guidance about work estimation as it pertains to programming is not. Steve McConnell wrote an entire book on the work estimation for programming. It's that specialized. amazon.com/Software-Estimation-Demystifying-Developer-Practices/…
– Jim G.
Oct 9 '14 at 14:09
2
2
He wrote a book on Software Estimation. Software is made up of programming but software isn't programming. Software estimation is infrastructure, planning, design, programming and testing. He's asking for working days, not working days spent specifically on programming.
– Ross Drew
Oct 9 '14 at 14:37
He wrote a book on Software Estimation. Software is made up of programming but software isn't programming. Software estimation is infrastructure, planning, design, programming and testing. He's asking for working days, not working days spent specifically on programming.
– Ross Drew
Oct 9 '14 at 14:37
suggest improvements |Â
1 Answer
1
active
oldest
votes
up vote
4
down vote
accepted
Good managers never specify what has to be done in a day or how many days can be used for a feature. They ask their developers what can be done in a day or how long they need for a feature. Normally, developers err on the optimistic side, so for good measaure, assume they will be 20% late.
The framework is in the state it's currently in because you put in the time you did. That's what it did cost.
Someone selling it would take your cost, add a factor to make some profit and price it that way.
If you think you are not as experienced as someone earning x$ an hour, it may be a lot easier to keep to the facts (the hours you worked) and instead adjust the price of an hour of work.
If you really want to know what it's worth, write up what it provides as requirements and ask other companies what it would cost if you wanted to buy something like it from them. That's a good measurement for market value.
answered Oct 9 '14 at 6:02
nvoigt
42.6k18105147
suggest improvements |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
Good managers never specify what has to be done in a day or how many days can be used for a feature. They ask their developers what can be done in a day or how long they need for a feature. Normally, developers err on the optimistic side, so for good measaure, assume they will be 20% late.
The framework is in the state it's currently in because you put in the time you did. That's what it did cost.
Someone selling it would take your cost, add a factor to make some profit and price it that way.
If you think you are not as experienced as someone earning x$ an hour, it may be a lot easier to keep to the facts (the hours you worked) and instead adjust the price of an hour of work.
If you really want to know what it's worth, write up what it provides as requirements and ask other companies what it would cost if you wanted to buy something like it from them. That's a good measurement for market value.
answered Oct 9 '14 at 6:02
nvoigt
42.6k18105147
suggest improvements |Â
up vote
4
down vote
accepted
Good managers never specify what has to be done in a day or how many days can be used for a feature. They ask their developers what can be done in a day or how long they need for a feature. Normally, developers err on the optimistic side, so for good measaure, assume they will be 20% late.
The framework is in the state it's currently in because you put in the time you did. That's what it did cost.
Someone selling it would take your cost, add a factor to make some profit and price it that way.
If you think you are not as experienced as someone earning x$ an hour, it may be a lot easier to keep to the facts (the hours you worked) and instead adjust the price of an hour of work.
If you really want to know what it's worth, write up what it provides as requirements and ask other companies what it would cost if you wanted to buy something like it from them. That's a good measurement for market value.
answered Oct 9 '14 at 6:02
nvoigt
42.6k18105147
suggest improvements |Â
up vote
4
down vote
accepted
up vote
4
down vote
accepted
Good managers never specify what has to be done in a day or how many days can be used for a feature. They ask their developers what can be done in a day or how long they need for a feature. Normally, developers err on the optimistic side, so for good measaure, assume they will be 20% late.
The framework is in the state it's currently in because you put in the time you did. That's what it did cost.
Someone selling it would take your cost, add a factor to make some profit and price it that way.
If you think you are not as experienced as someone earning x$ an hour, it may be a lot easier to keep to the facts (the hours you worked) and instead adjust the price of an hour of work.
If you really want to know what it's worth, write up what it provides as requirements and ask other companies what it would cost if you wanted to buy something like it from them. That's a good measurement for market value.
answered Oct 9 '14 at 6:02
nvoigt
42.6k18105147
Good managers never specify what has to be done in a day or how many days can be used for a feature. They ask their developers what can be done in a day or how long they need for a feature. Normally, developers err on the optimistic side, so for good measaure, assume they will be 20% late.
The framework is in the state it's currently in because you put in the time you did. That's what it did cost.
Someone selling it would take your cost, add a factor to make some profit and price it that way.
If you think you are not as experienced as someone earning x$ an hour, it may be a lot easier to keep to the facts (the hours you worked) and instead adjust the price of an hour of work.
If you really want to know what it's worth, write up what it provides as requirements and ask other companies what it would cost if you wanted to buy something like it from them. That's a good measurement for market value.
answered Oct 9 '14 at 6:02
nvoigt
42.6k18105147
answered Oct 9 '14 at 6:02
nvoigt
42.6k18105147
answered Oct 9 '14 at 6:02
nvoigt
42.6k18105147
answered Oct 9 '14 at 6:02
nvoigt
42.6k18105147
42.6k18105147
suggest improvements |Â
suggest improvements |Â
3
This question appears to be off-topic because it is about programming.
– Jim G.
Oct 9 '14 at 6:31
1
in stackoverflow they said it is not programming but performance of employee
– János
Oct 9 '14 at 10:20
Work estimation is not programming, it's Workplace. You are right to post here.
– Ross Drew
Oct 9 '14 at 11:51
@RossDrew: Work estimation in the abstract is on-topic. Specific guidance about work estimation as it pertains to programming is not. Steve McConnell wrote an entire book on the work estimation for programming. It's that specialized. amazon.com/Software-Estimation-Demystifying-Developer-Practices/…
– Jim G.
Oct 9 '14 at 14:09
2
He wrote a book on Software Estimation. Software is made up of programming but software isn't programming. Software estimation is infrastructure, planning, design, programming and testing. He's asking for working days, not working days spent specifically on programming.
– Ross Drew
Oct 9 '14 at 14:37