Enabling Globally Distributed Development with IBM Rational Tools

Enabling Globally Distributed Development with IBM Rational Tools Julian Holmes, Capgemini John Evans, Lamri

Geographically Distributed Teams Drive Global Development § Global Development Strategy • Shifting from localized development to one that is distributed – across town, across the border or overseas • Executed through multiple sites or through outsource companies • Model touches all development disciplines § Gartner predicts, IT outsourcing will reach $232. 1 B in 2007. Gartner “Gartner Dataquest Alert – Forecast for IT Outsourcing Segments Shows Strong Growth” March 10, 2004 In collaboration with IBM Rational User Group UK 2

What Type of Content is Typically Distributed? Outsourced/Offshore Projects: § Legacy application support and maintenance § Enhancements to existing systems § Re-engineering/modernizing legacy applications and systems § Greenfield / new application development – this is done, but not as common § Outsourced project may be complete system or subset, i. e. , components of larger system § Outsourced testing In collaboration with IBM Rational User Group UK 3

Outsourced/Offshore Development Project Models § Usually have a combination of on-site and off-shore development resources § On-site roles and tasks: High level of client-facing activities ú ú Business Modeling/Planning Requirements Definition Analysis and Design/Architecture Deployment Software Engineering Process § Offshore roles and tasks: ú Implementation ú Test ú Evaluation § At both sites: • Project Management • Testing/Integration • Configuration/Change Management In collaboration with IBM Rational User Group UK 4

Distribution of effort § But is this RUP? In collaboration with IBM Rational User Group UK 5

Poor Distributed Development – Root Causes § Communications issues – time lag, cultural, political, project visibility, work transfer mistakes, security, and ownership § Requirements not well defined up front § Requirements management process does not provide feedback loop, or method for communicating changing / evolving requirements § Requirements well defined, but not well communicated § Organizational issues – lack of team motivation § Process (handoff, delivery, change management) not well understood – time spent trying to figure out who does what § Additional project management overhead § Mismatched and unsynchronized configuration management processes and systems In collaboration with IBM Rational User Group UK 6

Rework Increase - Root Causes: § End product not the right product (requirements mis-match) § End product has high defect density § Offshore testing process not aligned with onsite needs § Requirements changes not reflected in product § Enhancement requests not reflected in product § Poorly defined deliverables § Wrong versions delivered for integration and deployment § Typical localized project rework is 20%-30 § Distributed development: 50%-100% rework in initial projects In collaboration with IBM Rational User Group UK 7

Solution Approach § Formal Software Development Processes • Defines roles, responsibilities, activities and artifacts • Enable workflow Focus of today's Presentation § Toolset Automations using Rational Suites and Multisite products • Enable process • Facilitate communication • Capture and manage important project information In collaboration with IBM Rational User Group UK 8

Rational Tools Solution Req. Pro Appl Reqts So. DA Iteration Plan Req. Pro Test Reqts Issue/Defect Tracking RSA Model Rose 3 rd Party IDE Code Team. Test. Factory Perf. Studio Test Scripts Performance Studio Diagnostic Testing Team. Test Perf. Studio Appl Testing Clear. Case Iteration Baselining Clear. Quest Multi. Site Configuration Management Clear. Case/Multi. Site Process/Tool Guidance In collaboration with Rational Unified Process IBM Rational User Group UK 9

Objectives of the integrations (why integrate? ) § Enable communication among the team § Single repository for information § Enforce process § Enable metrics collection § Traceability § Key integrations within Rational Suites • • Change Requests (CR) tied to Requirements CR tied to source code or other project artifacts CR tied to Test Cases tied to Requirements In collaboration with IBM Rational User Group UK 10

Rational Suites for Distributed Development § Clear. Case Multisite and Clear. Quest Multisite natively support distributed development § Toolset Integrations (Clear. Case, Clear. Quest, Requisite. Pro, Test. Manager) operate well at a common development site on a common LAN • Full integration between all tools can only be accomplished on a common LAN. • Web clients are good for accessing their respective point product, but they lack support to set integrations In collaboration with IBM Rational User Group UK 11

The Ideal Rational Tools Integration Model? Site A Integration Site B Requisite. Pro Replication Requisite. Pro Clear. Quest MS Site A Clear. Quest MS Site B Clear. Case MS Site A Clear. Case MS Site B Test. Manager § This model is the ideal but is not practical to realize. • Test Manager and Requisite. Pro do not have native support for data replication In collaboration with IBM Rational User Group UK 12

Globally Distributed Development Our Experiences Julian Holmes, Capgemini John Evans, Lamri

Capgemini and Rightshore™ What is Rightshore™? § Distributing our clients' work globally and making the best use of our Delivery Centres and of our Distributed Delivery infastructure § A stage beyond the simple offshore idea. Having the right reason, the right place, the right language and the right price. § Rightshore™ is a key differentiator for Capgemini in the marketplace. In collaboration with IBM Rational User Group UK 14

IBM Rational in Capgemini Globally § Over 1, 600 IBM Rational Suite licenses in concurrent use § Many thousands of RUP users across 30 countries § Driven by a global network of 23 Accelerated Delivery Centres § Strong and active IBM Rational Software Alliance Global Team In collaboration with IBM Rational User Group UK 15

Right-Shore™ Delivery with IBM Rational § Enabled by IBM Rational’s common language (RUP) and toolset § Delivered through a network of ADCs with specialist expertise § Only possible with a mature and consistent global approach In collaboration with IBM Rational User Group UK 16

It’s working for us. . . § But it’s been a long hard road. § Getting the process right is one thing. § Having the tools in place to support the approach is even harder § But what are your experiences? In collaboration with IBM Rational User Group UK 17

Case Study – 1 The Situation § Development distributed across 3 continents § Gained technology by acquisition • Rapid Expansion • Had a product (team/site centric approach) § They had always marketed a developed product not a complete solution § Investment in Clearcase only! In collaboration with IBM Rational User Group UK 18

Case Study 1 – The change in direction § Got the first customer who wanted to define the requirements • Customer defined a solution view of the world. § A new management team provided a new set of requirements to be able to inter work between the disparate teams. • A desire to be able to re-allocate staff quickly to other parts of the solution § A desire to leverage the existing products and re-use parts of products. In collaboration with IBM Rational User Group UK 19

The Challenges § How to manage a set of solution requirements? • How do these relate to products § How to manage change control at the solution level and the product level? § How could the solution be configured across all of the locations? In collaboration with IBM Rational User Group UK 20

The current use of tools Site B Site A Product B Product C Clear. Case Site A Product B Product A Product C Clear. Case Site B Site C Product A Product B Clear. Case Site C Copy In collaboration with IBM Rational User Group UK 21

The big picture how do the tools and RUP help? Solution RUP Requisite Pro Clearquest Clearcase with UCM The “how to” Requirements Baselines Provides change control Provides the repository and version management In collaboration with IBM Rational User Group UK 22

Proposed solution - 1 Integration Site B Site C Clear. Quest MS Site A Clear. Quest MS Site B Clear. Quest MS Site C Clear. Case MS Site A Clear. Case MS Site B Clear. Case MS Site C Site A Replication In collaboration with IBM Rational User Group UK 23

Proposed solution - 2. Requisite Pro Solution Requirements Product A Product B Product C Clear. Quest MS Site A Clear. Quest MS Site B Clear. Quest MS Site C Clear. Case MS Site A Clear. Case MS Site B Clear. Case MS Site C Replication In collaboration with IBM Rational User Group UK 24

Thank you julian. holmes@capgemini. com www. capgemini. com