ClearCase UCM deployment at Loto-Québec - Koserto 2005
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
ClearCase UCM deployment at
Loto-Québec
© Koserto 2005 .
www koserto.comContext
• Original Mandate
– Deploy ClearCase across all development
teams shipping on Tandem, Windows, QNX
• Initial state of affairs
– 200 developers, ~30 concurrent projects
– Access, VB, J2EE, C++, Tandem, QNX, …
• Deliveries calendar with no spare room
• Very varied degrees of SCM experience
• Some reluctance and skepticism
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 2Approach
Assess size & maturity of each group
Plan the implementation project
Devise global SCM plan
Consult, publish, validate, revise, prepare training material
Secure resources
Plan iterations
Execute iterations
Ongoi ng … imp rov eme nt … of … infrastructure
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 3Iteration details 1/2
• Identify core team of CM advocates
• Hold 6-8 workshops over 4-6 weeks
•Train core teams on SCM and FMO •Devise their own local SCMP
•Inventory users and components •Raise awareness
• Plan & hold training (tool and FMO)
• Hold tests sessions with all users
•Train & iron out quirks •Tests the infrastructure and the FMO
•Must be realistic •Setup test env. just like the real one
1 2 3 4 5 6 7 8 9 10 weeks
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 4Iteration details 2/2
• Converge and freeze components
• Migrate components into final P/VOBs
• Fix and deploy
• Start ongoing monitoring and adjustments
•Use reporting •Spot deviations and analyze constructively
• Consider lessons learned
– improve approach
…
1 2 3 4 5 6 7 8 9 10 weeks
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 5Actual deployment schedule
Titre
May-08
Aug-08
Sep-08
Nov-08
Dec-08
Feb-09
Mar-09
Jun-08
Jan-09
Oct-08
Apr-09
Jul-08
16 23 30 6 13 20 27 4 11 18 25 1 8 15 22 29 5 12 19 26 3 10 17 24 31 7 14 21 28 5 12 19 26 2 9 16 23 30 6 13 20 27 6 13 20 27 3 10 17 24
Gestion des données
préparation
iter 1
iter 2 - baseline
iter 2
iter 3 - baseline
iter 3
Systèmes administratifs
préparation - baseline
préparation
iter 1 - baseline
iter 1
iter 2 - baseline
iter 2 (LTM, ARS, PB, TFE (VB), …)
iter 3 - baseline
iter 3 (Safir, CPRH, EPRH, ATP)
Systèmes des jeux
préparation - baseline
préparation
iter 1 - baseline
iter 1 - (BOS, SDP)
iter 2 - baseline
iter 2 - (V3K, App Term.,) ?
iter 3 - (PES)
Projets
préparation - baseline
préparation
iter 1 - baseline
iter 1 - JEF
Gestion des jeux & AAL
préparation - baseline
préparation
iter 1 - baseline
iter 1 - 4ab (?) *
iter 2 - baseline
WEB *
préparation - baseline
préparation
iter 1 - baseline
iter 1 (toutes les applications WEB)
* Sujet à confirmation
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 6Key deliverables
• Global SCM plan
• Local SCM plan template
• CC SCM Procedures
& memory jogger
• FMO training slides
• FMO test plan template
• FMO setup in CC UCM
• Delivery slip mechanism in
ClearQuest
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 7Other useful tools
• The global calendar
• The users census worksheet
– For license provisioning & client installation
– Includes training requirements and budget
• The Organizational Breakdown Structure
• The component inventory
worksheet
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 8Key success factors
• Workshop based
– Encourages buy-in
• Adapt or fail
– No size fits all.
– Know where to trade-off
• Just-in-time training
• Buy-in, buy-in, buy-in
– Ongoing stakeholder analysis
• Stamina
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 9Service Oriented Management
• A tight-knit CM team
– Can be centralized or not
• Customer service oriented (ITIL-like)
– Agree on SLA
– Underpin SLA with vendors and suppliers
– Setup tiered support structure
• Setup a contingency
– with agreed upon parameters
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 10UCM terminology 1/2
Components
Composants Baselines
Baselines SystemSystèmes
configurations
(assemblages
(collection ofd’éléments
elements) ) (configurations de
(configurations ofcomposants )
components) (assemblages
(packagingde composant
(composite -baselines )
ofbaselines)
baselines)
C _GDD _compABC
Prog. c doc/
H elp.doc
Système RDD 2.0
Prog.h
Bdl_T04-0013 _mep1.txt
Nom du système :
Service responsable du système :
Intégrateur responsable :
B_P_GDJ_RDD_1.0_dev_blah2_PROD
Date de livraison :
Objectif de la livraison : mea _1
B_P_GDJ_RDD_2.0_dev_blah2_TA1
Nom du projet d 'origine :
Nom du projet destination :
B_P_GDJ_RDD_2.0_dev_blah2_TA2 Configuration TAP P :
C_ GDD_< composantABC > :
C_ GDD_< composantDEF > :
…
Baselines livrés :
élément
... C_ GDD_< composantABC > :
C_ GDD_< composantDEF > :
...
C_GD D_ compXYZ Instructions de build : ...
Instructions d’assemblage : ...
upref. doc Instructions d’installation : ...
Changements : ...
upref. c Readme. txt
Commentaires : ...
upref .h
version
Système JEF v 123
B_P_GDJ_RDD_1.0_dev_blah2_PROD
Bdl_T04-0164 _mea2.txt
...
B_P_GDJ_RDD_2.0_dev_blah2_TA1
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 11UCM terminology 2/2
project components
Prref baselines
stream Project
Ca
Cb Pd1
Pd1
foundation
Cc Pd1
v1v1v1
views
PD1v2dev
Integ
dev1 dev2
Ca
Cb
Cc CaC CaC
bCc C
b
c
Vinteg .
VD1 . VD2 .
Pd1
Pd1
Pd1
v1.1
v1.1
VD1 .
v1.1
VD2 .
Deliver
activités
Cc -B 1
rebase
rebase rebase
Prdev-B ti1 Deliver
activités PVOBs
(meta data)
VOBs
(data)
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 12SCM Plan
• Local plan builds on global one
• A well defined naming convention
– For components, projects, streams, baselines, …
– E.g. projects: P__
• Referential contains all production
assets
– What goes in the referential?
• Forced transition to controlled environment
– On the way to acceptance testing
or production
– Controlled by librarians
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 13UCM Mode of operation
See http://www.koserto.com/documents/public/lqcc/CC_UCM_Loto-Quebec_2.pdf for …
• The full mode of operation
– For complex development environments
• A simplified mode of operation
– For most simple development environments
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 14Delivery slip
SmithJ Smith John 555-1212 #222
\\pkgsrv\gdj\telephonie123
\\pkgsrv\gdj\telephonie123-…
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 15Build → Package → Install (BPI)
• SCM FMO says nothing about BPI
– To do so would lead to pointless resistance
• BPI is post SCM delivery but …
• BPI post delivery must be
controlled by librarian
– Or else opportunity to slip bugs or hacks
• Access to production strictly controlled
• BPI should be automated
– So librarians can do it or better yet, fully automated
• BPI must be tested prior to hand off
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 16ClearCase Projects Organization
…
…
…
…
…
…
…
…
…
…
ABC …
BCD …
CDE …
DEF …
…
…
…
…
…
…
…
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 17In the drawing board …
• Automated code delivery (CC & CQ)
• Use of composite baselines
• Better use of derived objects
• Reporting
• SLAs
• Continuous monitoring
• Monitoring dashboard
– For usage, performance & compliance,
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 18PM consideration
• A charter to secure commitment
• Understand change management
- Know
Be honest
Do
Get
Encourage
not
users
when
fearinvolved
feedback
not
to draw
knowing
the line
• Commitment falters. Nourish it.
• Plan ahead and give warning
• Communicate
- Setup
Monthly
Broadcast
Coordination
antribune
intranet
periodic
committee
withbulletins
execsmeets monthly
• Manage risks aggressively
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 19Resistance to change
Resistances Matrix
FOUNDED RESISTANCE UNFOUNDED RESISTANCE
Apprehension
Genuine
Resistance AWARENESS OF LOSSES IGNORANCE
Strategy: Reassurance Strategy : Information, clarification
Pretext
Non genuine
Resistance CREATION OF A
MALICE - STUBBORNNESS.
NEGOTIATION SPACE
Strategy : Negociation Strategy : Neutralisation, isolation
© TURBO
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 20Lessons learned
• Setup an intranet early on
• Setup service infrastructure early on
• Spend more time instilling customer
orientation in SCM organization
• Spend more effort upfront on backup &
recovery plan and test it.
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 21A team
• A project manager to deploy it
– With no ties helps setting politic aside
– Call us: www.koserto.com
• A lead to operate it once deployed (you provide)
• A good CC admin (call us here again)
• A good HW admin (you provide)
• A good trainer (call us here again)
• Ambassadors (you provide)
– Enlist the hardest opponents with the most clout
• Committed execs (you definitely provide but we can help with the business case)
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 22Resources
• Rational CC community
http://www-128.ibm.com/developerworks/forums/dw_forum.jsp?forum=333&cat=24
• Books & Articles
– Spectrum of Functionality in Configuration Management Systems
http://www.sei.cmu.edu/legacy/scm/tech_rep/TR11_90/TOC_TR11_90.html
– CM Plans : The beginning to your CM solution
http://www.sei.cmu.edu/legacy/scm/papers/CM_Plans/CMPlans.MasterToC.html
– Achieving CMMI Level 2 in the Configuration Management Process
Area Using IBM Rational Software Solutions
http://www-128.ibm.com/developerworks/rational/library/content/RationalEdge/mar03/CMMI_TheRationalEdge_Mar2003.pdf
– Software Configuration Management Patterns
http://www.amazon.ca/exec/obidos/ASIN/0201741172/qid=1112041520/702-3116675-6252844
– Software Configuration Management Strategies and Rational
ClearCase(R): A Practical Introduction
http://www.amazon.ca/exec/obidos/ASIN/0201604787/qid=1112041594/702-3116675-6252844
© Koserto 2005 Deploying ClearCase UCM at Loto-Québec 11/17/05 23You can also read
