![]() ![]() |
||
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
||
| Technology Transition Practices | |||||||||
| For many organizations that develop software, technology transition—the process of facilitating the acceptance and use of a new technology—is a challenging and often unmanaged activity. Researchers developing software-improvement technologies for software developers are realizing that the value or quality of their technologies alone does not ensure their acceptance and use. Software developers, who now more than ever recognize a mission-critical need to improve their software engineering practices, face a spectrum of adoption challenges as they seek to improve their skills, processes, products, and capabilities. And acquirers of software-intensive systems are seeking better, more cost-effective practices for deploying and fielding those systems so that risks to adoption and use are minimized and managed. Each of these is an example of the kinds of technology-transition problems that the SEI helps to solve. Purpose SEI staff members have developed methods to help those responsible for technology transition to answer these questions:
Many organizations do not ask these questions, do not know how to determine an answer, or do not know what to do next when the answer is “no.” SEI methods help organizations plan to overcome gaps and, ultimately, manage the transition to a successful completion. They are helping researchers, developers, and acquirers to better understand, evaluate, plan, and manage technology transition. As of FY2003 (beginning Oct. 1, 2002), Technology Transition Practices (TTP) was realigned at the SEI as part of the Technology Transition Services Directorate, which is charged with executing the SEI’s amplify strategy. Before this realignment, TTP was an SEI focus area called “Accelerating Software Technology Adoption.”
|
2002 Accomplishments Evolutionary Acquisition
Workshop Held Technology
Adoption The Technology Adoption Workshop helped us to evaluate
our behavior during a recent technology implementation project. We realized
that we
did not involve enough employees up front. We are doing a much better
job now. The workshop helped us to determine when to involve others,
helping us to save time and money. Technology Readiness Levels Study Conducted Technology Change Management Study Conducted |
||||||||
Home | About | Focus Areas | Special Programs | Conferences | Leadership and Oversight | Staff Information and Transition Activities |
|||
|
The Software Engineering Institute is a federally funded research and development center sponsored by the U.S. Department of Defense and operated by Carnegie Mellon University. |
URL: http://www.sei.cmu.edu/annual-report Copyright 2003 by Carnegie Mellon University Terms of Use |
||