This is the second article of series of two dedicated to Enterprise tooling adoption. In the first article, we’ve discussed some core concepts and results borrowed from social psychology field. We’ve noted how familiarity with a new tool is important to minimize resistance to adoption.
In this second article, we provide some supporting material depicting how to keep the right focus when adopting some new Enterprise tooling. First from a general stand-point and then for the specific adoption of:
These latter ones should be seen as extra layers coming on top of the initial layer of Enterprise tooling adoption.
Choice of a radar screen presentation…
The radar screen format is self-explanatory and introduces the intuitive idea of refining cycles and continuous improvement. Which is exactly how adoption should be conducted, i.e. each of the points on the radar should be reviewed on a regular basis.
Intent for me is not to comment on each item of these charts (*) but rather let them “as is”. For now, this rather comes as a “big picture” that you may find of a good support when either discussing with your local IBM team or business partner or when preparing the next steps for making adoption at your company progress.
(*): that would be done in a live meeting between yourself and a subject matter expert (from IBM or a Business Partner).
Note: If you’re looking for something more prescriptive on how to deploy RTC/CLM, please check the Reference links below.
… and how to use it.
Before deployment, you should wonder if there is an action plan against each of the points on your radar. If yes, what will be the impact of each action plan on the resistance to change (R.T.C) ? If no, what will be the impact of this lack on the R.T.C. ?
During deployment, you can make a retrospective of the impact of your actions plans on the R.T.C.
At the end of each deployment iteration, you should perform a retrospective to identify what actions were the most effective for reducing R.T.C.
1. Adoption of Enterprise tooling: radar screen for success
Order of adoption: RTC or RTC EE first ?
Shall you start adopting RTC in your distributed or in your mainframe teams ?–> A sound approach is to start with the most critical to you !
2. Adoption of RTC: radar screen for success
3. Adoption of RTC EE: radar screen for success
- [Jazz.net article] Considerations for deploying Rational Team Concert 4.0 and Rational Solution for Collaborative Lifecycle Management (slide-based presentation) a.k.a. “Deploy RTC / CLM in 16+ Steps“
- [Jazz.net Deployment wiki] Accelerating adoption of software tools and practices
- [devWorks] Developing Change: Learning Strategies for Enterprise Modernization
Acknowledgement: Thanks to Simon Washbrook for his review and always useful remarks.