1	An organised roadmap for implementing process (RUP) Show them you’re flexible and in control by Charles Edwards 25 March 2003
2	Coming up Goal of the session Assumptions Process implementation challenges Discuss ‘Before’ versus ‘During’ What is the Roadmap model? Discuss the Roadmap model Show one Package of the Model in detail Discuss benefits of the approach
3	Goal Our goal is to: Explore better ways of process implementation Explore better ways of tool implementation Improve process in small meaningful chunks by: careful planning considering dependencies involving management in decisions monitoring long term return on investment
4	Assumptions Specifically addresses large or long projects > 1 year > 40 people large budgets complex software mission critical software In-house expertise will be built up for long term support for long term maintenance future enhancements to the systems This model still in the conceptual stage Not yet fully realized
5	Process implementation challenges Know how on projects Most teams concentrate on developing software, not process. Management want cost justification How much is it going to cost? How long will it take? What are the benefits? Are we getting value for money out of the tools? Do managers know process & tools potential? Projects are typically planned & kicked off before Process is considered
6	‘Before’ versus ‘During’ Scenarios: Process implemented late – Start project. Only implement process once ‘Pain’ too unbearable. Process implemented on project – implement tools & process as part of the project. Process implemented first - Get the process and tools working first – then start the project. Build an organisation process – each project is a fine tuned instance of some base process.
7	‘Before’ versus ‘During’ Process implemented late.
8	‘Before’ versus ‘During’ Process implemented late. Pro’s Certain Process & Tools are improved. People realise why they need the Tools & Process. People generally more motivated to implement changes. Con’s Re-active. Can sometimes be too late to save the project. Extra money has to be found over & above Project budget. Can hamper Project effort. Often don’t finalise process before the project is over.
9	‘Before’ versus ‘During’ Process implemented on project
10	‘Before’ versus ‘During’ Process implemented on project Pro’s Funds justified and available for project reasons. Process defined people who use them. Auto buy in. Tangible problem to work with and resolve. Con’s Usually too much to get right first time. Ends up being reactive and not proactive. Not enough time for proper training or guideline writing. People learn bad habits from having to make it work, which are difficult to change later. Individuals who know their stuff become overworked.
11	‘Before’ versus ‘During’ Process implemented first
12	‘Before’ versus ‘During’ Process implemented first Pro’s Get PC’s and tools organised, installed, rolled out. Processes defined for each discipline. Do things in a planned and orderly manner. Pro-active. Con’s People who weren’t involved arrive & do it their way Takes time up-front – many projects can’t wait. Budgets for process usually justified by Projects. Rather intangible if you’ve not done it before.
13	‘Before’ versus ‘During’ Build an organisation process
14	‘Before’ versus ‘During’ Build an organisation process Pros Projects will have a Process & Tools base to start from. Projects will refine their own processes from this base. Each subsequent Project will improve these processes. Each subsequent Project will be faster at starting. Over time more and more will be automated. The mistakes will be fed into the common base process. Build a common organisation knowledge of Tools & Process Cons Need to find a budget for a small team over time. First Project takes a hit with higher cost. First Project takes a hit with slower production. Process misunderstandings can become entrenched
15	What is the Roadmap model? The Roadmap Model is: A pre-defined model for implementing the Rational Unified Process and the Rational Tools It consists of <<Model>> A UML model that defines the roadmap. <<Artefacts>> A ready made set of Artefacts to aid you in your implementation efforts.
16	What is the Roadmap model? <<Model>> The UML Roadmap model consists of: A series of inter-related and inter-dependent packages Each package contains either further sub-packages or class diagrams or other diagrams
17	What is the Roadmap model? The Artefacts it contains consists of: Various documents containing information stereotyped as: <<Agenda>> <<Vision>> <<Guidelines>> <<Checklists>> <<Minutes>> <<Proposals>> <<Presentation>> <<Report>> MS plans Excel Costing spreadsheets Strawman Project Web
18	What is the Roadmap model? The Roadmap model can be enhanced for other methodology concepts i.e. Prince2, EUP, DSDM, XP, Agile modelling, FDD, etc. The Roadmap model can be configured for other tools such as: Non-Rational equivalents Open Source offerings
19	Roadmap model
20	Roadmap model
21	Understand the situation package
22	Manage implementation rollout
23	Manage implementation rollout
24	Manage implementation rollout
25	Manage implementation rollout
26	Understand the situation package
27	Plan the “Understand Situation” Investigation
28	Plan the “Understand Situation” Investigation
29	Plan the “Understand Situation” Investigation
30	Plan the “Understand Situation” Investigation
31	Plan the “Understand Situation” Investigation
32	Understand the situation package
33	Process Audit evaluation
34	Process Audit evaluation
35	Understand the situation package
36	Presentation of findings and recommendations
37	Benefits of the approach Project ‘Process’ know how enhanced People can see what Processes to address. People can see what Tools to address. A visual Roadmap for Process implementation Easier to plan improvements into Iterations Reduce the circular cycle of change where changing one process disrupts another
38	Benefits of the approach Cost Justification better defined People understand cost of each Process implementation. People understand the cost of each Tool implementation. Management can: eliminate what they are not prepared to spend on. have visibility on the implications of their decisions. do “what if’s” on the model to look at cost implications. see on the plan where their involvement is required. have a view on what is currently a “Black Art”
39	Benefits of the approach Return on Investment now has a more formal metric We spent X on implementing packages A,B & C. Also using Change Control & Defect tracking on Tools & Process We can measure how often Process & Tools change Monitor how this expense diminishes from project to project => How well it works and costs over time No silver bullet
40	In Summary We looked at Process implementation challenges ‘Before’ versus ‘During’ The Roadmap model and what it contains Showed one Package of the Model in detail Discussed benefits of the approach
41	Questions & Answers Thank you for your time. Questions?