views:

306

answers:

8

During past years, my company has successfully used client-server technology, with a now very old programming language.

A large percentage of our income is based on maintenance projects.

All of our developers are good software engineers, but most don't have experience with new technologies.

Now, every new project sold is developed using current technology, but quality is lacking. We have best-of-breed tools and languages, but still the quality is below standards and best practices, as old, not OO practices are ported to the new development environment.

My idea is that training should fix this problem.

What is your opinion on this, and if you agree that training is the solution, how would you propose that to upper management, taking into account that we are in the middle of an economic crisis?

Any advice would be greatly appreciated.

A: 

Show them your bug count.

JaredPar
I suspect that some managers will interpret bugs as personal failings, rather than indications of a lack of specific skills.
Steven Sudit
@Steven, I agree, I mainly meant this answer to be humorous instead of serious (hence the WIKI)
JaredPar
+6  A: 

Management's main interest is going to be how this training is going to make you a better employee -- how the knowledge you gain will bring additional value to the department. Work from that angle. How will training actually save them money in the long term (or even better, in the short term).

Enjoy,

Robert C. Cartaino

Robert Cartaino
+3  A: 

One idea is that each team member go do research on a topic and then meet for a few hours a week to have them present that topic. Every week another team member presents.

This way all you have to get from management is the time and a space to do it. You can even get them to provide you with lunch and do it over lunch for 2 to 3 hours.

jvanderh
This will also help by allowing management to _see_ how much time training is taking away from development; to counter that, be certain they can see the improvements (bug count).
John Saunders
+1  A: 

Research on how much was spent due to bugs worldwide, find some information on the return of investment brought from training. If you can find a case from another company, it would be even better. I think this is a better aproach considering their way to think (finantial result).

Depending on the circumstances, you could also try to convince other people to join you, and spread this idea around the company, try to find cheap training in the area of interest.

If even this way, they won't be helpful because of spending money on trainings, you could organize a study group within your company, and ask them at least for a little more "free time" to spend on it.

Then share with us :)

Samuel Carrijo
+2  A: 

When talking to anyone, it's important to try to see the situation from their perspective and talk in a language that they understand, which for managers is money. If you can calculate a rough return on investment of the training that will go a long way to convincing your manager that it is worthwhile.

In fact even better than rough, make it as detailed as possible with solid numbers and percentages and man hours.

mR_fr0g
+4  A: 

Heard about 5 whys technique? Take a sample of bugs that you have in your project and ask 5 Whys on why this happened?

Example: Why is it so slow? SQL queries not optimized. Why did it happen? Insufficient technical exposure. Why? Insufficient training..

Produce some samples from your bugs which drill down to training.

Pradeep
+2  A: 

One thing I'd recommend is that you work on Management acquiring licenses for digital libraries, like Safari Books Online. See also http://www.safaribooksonline.com/atwork.

You can start with one license for one person for ten books, and let them see a few people reading over his shoulder. Then maybe upgrade to the Library for the one person, and let them see everyone reading over his shoulder.

I also suggest adding some sort of Wiki site for your developers to use. Encourage them to post what they learn (and quietly make sure they know why). Management, of course, would also have access to the site. Also post what is learned from the lunchtime meetings, forums, and even SO.

If they learn something from a new book, they should post the link to the book (or chapter), in the Wiki. That not only helps those who come after find the material, it also helps show management where the money was spent.

John Saunders
We've used the Wiki idea and its great for when you add new members to the team. They can poke around the group's common knowledge very easily.
jvanderh
Another good thing to do with new members and a wiki: make them write down what they learn! Free labor!
John Saunders
We'll be getting a license for a digital library (John, do you have experience with books24x7? If you do, would you still go for Safari?).The wiki idea is a very good one and we'll implement it. I think that, besides all the advantages you guys pointed, it will also reinforce the acquired knowledge.
julio.g
I've used Books 24x7. They're fairly comparable, depending on which collections your company buys from books 24x7. Be careful on the configuration of the latter. For a year, I couldn't use it because I was configured not to have access to the Development library. I thought it was all Office stuff. Compare offered books, but I think Safari has more, and more up to date.
John Saunders
A: 

Sounds like you are trying the sell the new Technology and Architecture designs to Management and possibly some developers. I think you have to convince everyone that the new Technology and design is better.

I would suggest building a prototype using the new design & Technology which replaces some common existing older design. Then Prepare a presentation of all the benefits and drawback of the two designs to all the developers. From there I think you could start to build a training plan that you and the developers can agree on, and then later have more info. to present to Upper management for sign-off.

eschneider
Actually, he said, "Now, every new project sold is developed using current technology", so being permitted to use the new technology isn't the issue - training to know _how_ to use it is the issue.
John Saunders
Yes but the design is not as expected, so you need to convince the developers first. A prototype and a presentation will help convince the developers to use the new design.
eschneider
I had the impression that they're using the new tools, but need training in order to use them well. Without training, they are using the new technologies poorly, resulting in the loss of quality.
John Saunders