Return to Answer

Tell them about technical debt and the value of unit testing

Look at this post from some nice idea's on technical debt. Following through from that post you can get to the following pdf

I like this post on the value of unit testing (there are probably more to find)

The hope is not to get them out of your development process but get them involved and committed in the right way.

IMHO you need to write your original planning down, add chapters 1 and 2 (not in an appendix) in which you explain technical debt and the value of unit testing. Give them alternatives:

• less hours (not the entire 150, that sounds ridiculous) where every change (during development phase and during maintenance) on average will take:
  • small 4 hours
  • medium 16 hours
  • large 40 hours
• your estimated hours where every change (development phase and during maintenance) on average will take:
  • small 2 hours
  • medium 8 hours
  • large 20 hours

(hours are an indication, you are way better equipped to give better estimations)

Don't forget to include your track record for on-time on-budget deliveries.

Write it down and discuss this with them. They might have some valuable points in features the don't actually need right now or some technical debt they are willing to take in order to deliver on time. Just make sure these are conscious choices.

Hope this helps and good luck.

Tell them about technical debt and the value of unit testing

Look at this post from some nice idea's on technical debt. Following through from that post you can get to the following pdf

I like this post on the value of unit testing (there are probably more to find)

The hope is not to get them out of your development process but get them involved and committed in the right way.

IMHO you need to write your original planning down, add chapters 1 and 2 (not in an appendix) in which you explain technical debt and the value of unit testing. Give them alternatives:

• less hours (not the entire 150, that sounds ridiculous) where every change (during development phase and during maintenance) on average will take:
  • small 4 hours
  • medium 16 hours
  • large 40 hours
• your estimated hours where every change (development phase and during maintenance) on average will take:
  • small 2 hours
  • medium 8 hours
  • large 20 hours

(The hours are just indicative. You are way better equipped to give proper estimates.)

Don't forget to include your track record for on-time on-budget deliveries.

Write it down and discuss this with them. They might have some valuable points in features the don't actually need right now or some technical debt they are willing to take in order to deliver on time. Just make sure these are conscious choices.

Hope this helps and good luck.

Tell them about technical debt and the value of unit testing

Look at this post from some nice idea's on technical dept. Following through from that post you can get to the following pdf

I like this post on the value of unit testing (there are probably more to find)

The hope is not to get them out of your development process but get them involved and committed in the right way.

IMHO you need to write your original planning down, add chapters 1 and 2 (not in an appendix) in which you explain technical dept and the value of unit testing. Give them alternatives:

• less hours (not the entire 150, that sounds ridiculous) where every change (during development phase and during maintenance) on average will take:
  • small 4 hours
  • medium 16 hours
  • large 40 hours
• your estimated hours where every change (development phase and during maintenance) on average will take:
  • small 2 hours
  • medium 8 hours
  • large 20 hours

(hours are an indication, you are way better equipped to give better estimations)

Don't forget to include your track record for on-time on-budget deliveries.

Write it down and discuss this with them. They might have some valuable points in features the don't actually need right now or some technical dept they are willing to take in order to deliver on time. Just make sure these are conscious choices.

Hope this helps and good luck.

Tell them about technical debt and the value of unit testing

Look at this post from some nice idea's on technical debt. Following through from that post you can get to the following pdf

I like this post on the value of unit testing (there are probably more to find)

The hope is not to get them out of your development process but get them involved and committed in the right way.

IMHO you need to write your original planning down, add chapters 1 and 2 (not in an appendix) in which you explain technical debt and the value of unit testing. Give them alternatives:

• less hours (not the entire 150, that sounds ridiculous) where every change (during development phase and during maintenance) on average will take:
  • small 4 hours
  • medium 16 hours
  • large 40 hours
• your estimated hours where every change (development phase and during maintenance) on average will take:
  • small 2 hours
  • medium 8 hours
  • large 20 hours

(hours are an indication, you are way better equipped to give better estimations)

Don't forget to include your track record for on-time on-budget deliveries.

Write it down and discuss this with them. They might have some valuable points in features the don't actually need right now or some technical debt they are willing to take in order to deliver on time. Just make sure these are conscious choices.

Hope this helps and good luck.

Tell them about technical dept and the value of unit testing

Look at this post from some nice idea's on technical dept. Following through from that post you can get to the following pdf

I like this post on the value of unit testing (there are probably more to find)

The hope is not to get them out of your development process but get them involved and committed in the right way.

IMHO you need to write your original planning down, add chapters 1 and 2 (not in an appendix) in which you explain technical dept and the value of unit testing. Give them alternatives:

• less hours (not the entire 150, that sounds ridiculous) where every change (during development phase and during maintenance) on average will take:
  • small 4 hours
  • medium 16 hours
  • large 40 hours
• your estimated hours where every change (development phase and during maintenance) on average will take:
  • small 2 hours
  • medium 8 hours
  • large 20 hours

(hours are an indication, you are way better equipped to give better estimations)

Don't forget to include your track record for on-time on-budget deliveries.

Write it down and discuss this with them. They might have some valuable points in features the don't actually need right now or some technical dept they are willing to take in order to deliver on time. Just make sure these are conscious choices.

Hope this helps and good luck.

Tell them about technical debt and the value of unit testing

Look at this post from some nice idea's on technical dept. Following through from that post you can get to the following pdf

I like this post on the value of unit testing (there are probably more to find)

The hope is not to get them out of your development process but get them involved and committed in the right way.

IMHO you need to write your original planning down, add chapters 1 and 2 (not in an appendix) in which you explain technical dept and the value of unit testing. Give them alternatives:

• less hours (not the entire 150, that sounds ridiculous) where every change (during development phase and during maintenance) on average will take:
  • small 4 hours
  • medium 16 hours
  • large 40 hours
• your estimated hours where every change (development phase and during maintenance) on average will take:
  • small 2 hours
  • medium 8 hours
  • large 20 hours

(hours are an indication, you are way better equipped to give better estimations)

Don't forget to include your track record for on-time on-budget deliveries.

Write it down and discuss this with them. They might have some valuable points in features the don't actually need right now or some technical dept they are willing to take in order to deliver on time. Just make sure these are conscious choices.

Hope this helps and good luck.