Date post: | 01-Nov-2014 |
Category: |
Technology |
Upload: | koserto |
View: | 1,501 times |
Download: | 2 times |
© Koserto 2005
ClearCase UCM deployment at
Loto-Québec
www.koserto.com
Deploying ClearCase UCM at Loto-Québec 2© Koserto 2005 04/08/23
Context
• 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
Deploying ClearCase UCM at Loto-Québec 3© Koserto 2005 04/08/23
Approach
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
Ongoing … improvement … of … infrastructure
Deploying ClearCase UCM at Loto-Québec 4© Koserto 2005 04/08/23
Iteration details 1/2
• Identify core team of CM advocates• Hold 6-8 workshops over 4-6 weeks
• Plan & hold training (tool and FMO)• Hold tests sessions with all users
•Train core teams on SCM and FMO •Devise their own local SCMP
•Inventory users and components •Raise awareness
•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
Deploying ClearCase UCM at Loto-Québec 5© Koserto 2005 04/08/23
Iteration 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
Deploying ClearCase UCM at Loto-Québec 6© Koserto 2005 04/08/23
Actual deployment scheduleTitre
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
Nov-08 Mar-09Dec-08 Jan-09 Feb-09Sep-08 Apr-09Oct-08Jul-08 Aug-08May-08 Jun-08
Deploying ClearCase UCM at Loto-Québec 7© Koserto 2005 04/08/23
Key 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
Deploying ClearCase UCM at Loto-Québec 8© Koserto 2005 04/08/23
Other 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
Deploying ClearCase UCM at Loto-Québec 9© Koserto 2005 04/08/23
Key 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
Deploying ClearCase UCM at Loto-Québec 10© Koserto 2005 04/08/23
Service 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
Deploying ClearCase UCM at Loto-Québec 11© Koserto 2005 04/08/23
UCM terminology 1/2
C _ G D D _ c o m p A B C
P r o g . c
H e l p . d o c
d o c /
P r o g . h
B _ P _ G D J _ R D D _ 1 . 0 _ d e v _ b l a h 2 _ P R O D
B _ P _ G D J _ R D D _ 2 . 0 _ d e v _ b l a h 2 _ T A 1
B _ P _ G D J _ R D D _ 2 . 0 _ d e v _ b l a h 2 _ T A 2
C _ G D D _ c o m p X Y Z
u p r e f . c
u p r e f. d o c
R e a d m e . tx t
u p r e f .h
B _ P _ G D J _ R D D _ 1 . 0 _ d e v _ b l a h 2 _ P R O D
B _ P _ G D J _ R D D _ 2 . 0 _ d e v _ b l a h 2 _ T A 1
. . .
S y s t è m e R D D 2 . 0
B d l _ T 0 4 - 0 0 1 3 _ m e p 1 . t x t
S y s t è m e J E F v 1 2 3
B d l _ T 0 4 - 0 1 6 4 _ m e a 2 . t x t
. . .
C o m p o s a n t s
( a s s e m b l a g e s d ’ é l é m e n t s )
B a s e l i n e s
( c o n f i g u r a t i o n s d e c o m p o s a n t s )
S y s t è m e s
( a s s e m b l a g e s d e c o m p o s a n t - b a s e l i n e s )
é l é m e n t
v e r s i o n
N o m d u s y s t è m e :
S e r v i c e r e s p o n s a b l e d u s y s t è m e :
I n t é g r a t e u r r e s p o n s a b l e :
D a t e d e l i v r a i s o n : < 2 0 0 4 - 0 7 - 2 7 >
O b j e c t i f d e l a l i v r a i s o n : m e a _ 1
N o m d u p r o j e t d ' o r i g i n e : < P _ G D D _ d e v _ 6 4 9 a 2 _ J E F _ b l a h 1 >
N o m d u p r o j e t d e s t i n a t i o n : < P _ G D D _ t a p p _ 6 4 9 a 2 _ J E F _ b l a h 1 >
C o n f i g u r a t i o n T A P P :
C _ G D D _ < c o m p o s a n t A B C > : < P _ G D D _ r e f _ T D M _ d m e p 1 2 3 4 _ l i v 2 >
C _ G D D _ < c o m p o s a n t D E F > : < P _ G D D _ r e f _ T D M _ d m e p 1 2 3 4 _ l i v 2 >
…
B a s e l i n e s l i v r é s :
C _ G D D _ < c o m p o s a n t A B C > : < P _ G D D _ d e v _ 6 4 9 a 2 _ J E F _ b a s e l i n e 1 2 3 >
C _ G D D _ < c o m p o s a n t D E F > : < P _ G D D _ d e v _ 6 4 9 a 2 _ J E F _ b a s e l i n e 2 3 4 >
. . .
I n s t r u c t i o n s d e b u i l d : . . .
I n s t r u c t i o n s d ’ a s s e m b l a g e : . . .
I n s t r u c t i o n s d ’ i n s t a l l a t i o n : . . .
C h a n g e m e n t s : . . .
C o m m e n t a i r e s : . . .
Components(collection of elements)
Baselines(configurations of components)
System configurations(packaging of baselines)(composite baselines)
Deploying ClearCase UCM at Loto-Québec 12© Koserto 2005 04/08/23
UCM terminology 2/2
PD1v2dev
Integ
Cc
Cb
Ca
rebaserebase
Deliveractivités
Pd1v1Pd1
v1Pd1v1
Pd1v1.1Pd1v1.1
Pd1v1.1
Cc
Cb
Ca
Cc-B1
Prdev-Bti1
Deliveractivités
VD1 . VD2 .
Vinteg .
VD1 .
VD2 .
project
stream
componentsbaselines
rebase
Project foundation
views
VOBs(data)
PVOBs(meta data)
Deploying ClearCase UCM at Loto-Québec 13© Koserto 2005 04/08/23
SCM Plan
• Local plan builds on global one
• A well defined naming convention
– For components, projects, streams, baselines, …
– E.g. projects: P_<svc>_<dev|tapp|ref>
• Referential contains all production assets
– What goes in the referential?
• Forced transition to controlled environment
– On the way to acceptance testingor production
– Controlled by librarians
Deploying ClearCase UCM at Loto-Québec 14© Koserto 2005 04/08/23
UCM Mode of operation
• The full mode of operation – For complex development environments
• A simplified mode of operation– For most simple development environments
Deploying ClearCase UCM at Loto-Québec 15© Koserto 2005 04/08/23
Delivery slip
Smith JohnSmithJ 555-1212 #222
\\pkgsrv\gdj\telephonie123
\\pkgsrv\gdj\telephonie123-…
Deploying ClearCase UCM at Loto-Québec 16© Koserto 2005 04/08/23
Build 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
Deploying ClearCase UCM at Loto-Québec 17© Koserto 2005 04/08/23
ClearCase Projects Organization
ABC
BCD
CDE
DEF
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
Deploying ClearCase UCM at Loto-Québec 18© Koserto 2005 04/08/23
In 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,
Deploying ClearCase UCM at Loto-Québec 19© Koserto 2005 04/08/23
PM consideration
• A charter to secure commitment
• Understand change management
• Commitment falters. Nourish it.
• Plan ahead and give warning
• Communicate
• Manage risks aggressively
- Be honest- Do not fear not knowing- Get users involved- Encourage feedback- Know when to draw the line
- Coordination committee meets monthly- Monthly tribune with execs- Broadcast periodic bulletins- Setup an intranet
Deploying ClearCase UCM at Loto-Québec 20© Koserto 2005 04/08/23
Resistance to change
UNFOUNDED RESISTANCEFOUNDED RESISTANCE
Resistances Matrix
GenuineResistance
Apprehension
IGNORANCEStrategy : Information, clarification
AWARENESS OF LOSSESStrategy: Reassurance
Non genuine Resistance
Pretext
MALICE - STUBBORNNESS.Strategy : Neutralisation, isolation
CREATION OF ANEGOTIATION SPACEStrategy : Negociation
© TURBO
Deploying ClearCase UCM at Loto-Québec 21© Koserto 2005 04/08/23
Lessons 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.
Deploying ClearCase UCM at Loto-Québec 22© Koserto 2005 04/08/23
A team
• A project manager to deploy it– With no ties helps setting politic aside– <shameless plug>Call us: www.koserto.com</shameless plug>
• 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)
Deploying ClearCase UCM at Loto-Québec 23© Koserto 2005 04/08/23
Resources
• Rational CC communityhttp://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 Solutionshttp://www-128.ibm.com/developerworks/rational/library/content/RationalEdge/mar03/CMMI_TheRationalEdge_Mar2003.pdf
– Software Configuration Management Patternshttp://www.amazon.ca/exec/obidos/ASIN/0201741172/qid=1112041520/702-3116675-6252844
– Software Configuration Management Strategies and Rational ClearCase(R): A Practical Introductionhttp://www.amazon.ca/exec/obidos/ASIN/0201604787/qid=1112041594/702-3116675-6252844