View
212
Download
0
Category
Preview:
Citation preview
techtrans17b 1
Software Technology Transfer
Why don’t organizations use new ideas?
techtrans17b 2
Why is Software Technology Transfer So Hard?
Reifer
text pp502-507
techtrans17b 3
Negative Conditions (1)
No clear need or opportunity Risk taking not tolerated
– management must encourage risk taking Lack of sponsorship
– champion must build consensus– can not be driven from top or bottom
techtrans17b 4
Negative Conditions (2)
Organization isn’t ready– revamp processes to make it an integral part of
the process Knowhow lacking
– transferring the skills, knowledge, and abilities needed for the new technology
techtrans17b 5
Mechanisms (1)
“Technically astute managers, supportive executives, and champions responsible for technology transition;”
“High-quality prototypes, scalable demonstrations, and measured results from a successful application of the technology;”
techtrans17b 6
Mechanisms (2)
“Promotional materials that communicate the capabilities and benefits of the technology;”
“A trained and committed staff ready to lead the use of the technology on another application.”
techtrans17b 7
3 approaches to quicken transfer
Make technology transfer part of the process improvement
Incorporate tools into development environment
Use training and trial use to develop people who are familiar with the technology
techtrans17b 8
Succeeding as a Clandestine Change Agent
C. Dennis Allen
C. ACM May95
text pp518-523
techtrans17b 9
Dennis Allen
What did he do?
Why did it work?
Recommended