1 / 12

Two good reasons why new software processes are not adopted

This article discusses two primary reasons why new software processes are often not adopted, including the traditional characteristics of innovation and the complexities of managing change. It also provides practical solutions and examples to overcome these challenges.

Patman
Download Presentation

Two good reasons why new software processes are not adopted

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Two good reasons why new software processes are not adopted Stan Rifkin Master Systems Inc. 2604B El Camino Real Carlsbad, California 92008 USA +1 760 729 3388 sr@Master-Systems.com

  2. Traditional explanation of adoption • Characteristics of • Innovation • Adopters • Organization • Environment

  3. Traditional characteristics of the innovation 1.Relative advantage is the degree to which an innovation is perceived to be better than the idea or product or process it supersedes. 2.Compatibility is the degree to which an innovation is perceived to be consistent with the existing culture and needs. 3.Complexity is the degree to which the innovation is difficult, or at least more difficult than its competitors. 4.Trialability and divisibility are measures of the degree to which an innovation may be taken apart and only a part tried. A thick, monolithic innovation has a lower trialability than one that has separable components, each of which adds some value. 5.Observability is the degree to which the results of the implementation will be visible.

  4. (Exhaustive) list of factors -- from Lopata

  5. Factors might interact in messy ways

  6. Usual problems with factors • Linear combination • No interaction or connection • No timing • No dominance … and a practical solution • Embrace the logic of opposition • Force and counterforce • Transformation and persistence • Change and restoration

  7. Better answer 1

  8. Better answer 2

  9. Examples • COTS in the organization • Competency destroying: need new skills of assessment & assimilation, architecture matching, and adaptation (“Just because you know how to create it does not mean you know how to buy it.”) • In-house corporate re-use vs. open source model • Social & economic forces dominate “logic” of control & ownership • Transition of research software to industrial settings • Each is trying to optimize a different thing • Need a transition organization

  10. Archetype transition organization Technology receptors: There is a focal point inside organizations to scan the technology landscape and tailor the solutions there to the organization’s particular problems & environment.

  11. Path dependence & creation • Things happen for a reason, even a bad one. • In order to get things to happen Your Way you have to change the climate from inside: • Creative destruction; mindful deviation • Values - quality, economics, time to market, security • Tension between patience and impatience • Do not forget: you are both a technology creator and a change agent!

  12. Implications • Power & politics dominate technical content • (Linear) checklists (of factors) are limited in predictive ability • Technical content is a hygiene factor, a dissatisfier, something to be overcome

More Related