Global Development and Delivery Scenarios

by

In 2006-2008 I developed scenarios for the IBM Rational Global Development and Delivery offering 

The Global Development and Delivery Scenario

The GDD scenarios outline the steps for a client that is transforming from a single-site development team to a global delivery organization. This scenario was chosen based on its business importance to our sponsors and to the overall design of the DGG solution.

The design scenario covered the following acts

  • Setup the Distributed Environment (Unique to GDD)
  • Develop a new application release (Business Driven Development Green Thread)
  • Fix a problem in the first release (System in Trouble Green Thread)
Scenario Synopsis

The GDD scenario is a branch of the JK Enterprise scenario developed by the IBM Rational Green Threads team. The scenario is using a  financial banking context and an new Account Opening application.  

The GDD storyline starts with the delivery of the first release of the Account Opening application. The development team of 11+ has been local to a single site in US with a Central tool deployment topology. The team is preparing for a the second release with a larger team. JKE has acquired a company in EU of 5 developers that will join the Account Opening team. Also, a team of 10+ developers contracted though GSI in India, will take over the support for the first Account Opening application release while the US and EU teams starts developing the second release.

The teams need to

  • Bring up a multisite backbone with the new development sites in EU and with GSI.
  • Hand-off the Account Opening first release code to GSI.
  • Establish a change management process with the JKE and GSI teams for the support of the first release
  • Establish a requirement management process with the JKE US and EU teams for the second release.

The scenario assesses the gaps and drives the design for improvements in the GDD solution.

  • The need to quickly deploy the development infrastructure to new teams to make them producing from day one. 
  • The need for WAN tools that can support all key developer use-cases in CC, CQ and UCM.
  • The needs for centralised builds
  • The needs for distribution of central builds for local testing
  • The need to run change management for a maintenance release and for new development  
  • The need to ensure asset security and isolation of maintenance new new development project
  • The need for secure connections over remove connections
Scenario Personas

US

  • Overall Project Manager
  • Business Analyst
  • Architect
  • Developer
  • Test Engineer
  • Integration Developer
  • Build Engineer
  • Enterprise Architect
  • IT Administrator
  • Development Tools Administrator

EU

  • Business Analyst
    (for EU market)
  • Architect / Lead Developer
  • Test Engineer
  • Build Engineer
  • IT Administrator

GSI

  • Project Manager
  • Architect / Developer
  • Test Engineer
  • Integration Developer
  • Build Engineer
  • Enterprise Architect
  • IT Administrator
  • Development Tools Administrator
The GDD Scenario As-Is State

The JKE development team is using a single side local topology deployment of the IBM Rational GDD solution

  • Rational Portfolio Manager for project management
  • ClearCase for source code management
  • ClearQuest for change management
  • BuildForge for software builds
  • SystemTest for quality management
  • Client tools for modelling and test execution

 

 

GddAsIs-1024x727

The GDD Scenario To-Be State

The JKE development team is targeting a centralised hub topology deployment of the IBM Rational GDD solution and WAN access for EU and GSI team members.

  • Rational Portfolio Manager for project management in US
  • ClearCase Web for source code management in EU and GSI
  • ClearQuest Web for change management in EU and GSI
  • BuildForge for central software builds in US
  • SystemTest for quality management in US
  • Client tools for modelling and test execution in US, EU and GSI. Test artefacts under SCM control.

 

GddToBe-1024x634

Major ‘Setup’ Thread Steps
  • Organise IT infrastructure and development tools for GDD
    • Connectivity, workspaces, access rights, tools deployment
  • Establish distributed development process
    • Internal and with GSI
    • Workflow, governance, metrics
  • Establish project plans
  • Provision artifacts to practitioners
  • Implement key practical/functional distributed workflows and verify
PageLines