CRM 18 IBM Rational Software Development Conference 2008 © 2007 IBM Corporation ® Introducing Application Lifecycle Management on IBM ® Rational ® ClearQuest

CRM 18

IBM Rational SoftwareDevelopment ConferenceIBM Rational SoftwareDevelopment Conference

2008

© 2007 IBM Corporation

®

Introducing Application Lifecycle Management on IBM® Rational® ClearQuest®

Carolyn PampinoSolution Architect, IBM [email protected]

http://www.ibm.com/software/rational

IBM Rational Software Development Conference 2008

CRM 18 2

Disclaimer and Non-Disclosure

This solution is available from Devworks for CQ 7.0.1 users; http://www.ibm.com/developerworks/rational/downloads/08/cq_almpackage/index.html

included in ClearQuest 7.1

IBM Rational Plans are subject to change

Nothing in this document is intended to create any representations or warranties

IBM Rational warranties are contained in the applicable license agreements

Ouch!


CRM 18 3

Agenda

The What and Why of this Solution

Core Concepts Projects

Work

System-wide Settings

Customization options and examples

Integrations Themes

UCM

Build Forge

RequisitePro

Pow!


CRM 18 4

What is Application Lifecycle Management on CQ?

Tester•Test changes in baselines

Developer•Work on activities•Develop and deliver changes

Release Engineer•Integrate and build delivered changes•Create baselines

Test Lead•Ensure quality ProjectProject

CategoryCategory

ReleaseRelease

Team Lead•Assigns activities to complete tasks

Change Control Mgr•Triage requests•Assigns tasks to projects

Change performed in the context of

Out-of-box ALM Solution for ClearQuest (schema and packages)

Process model focused on work completed in the context of a Project

Requests are planned as Tasks and performed as Activities

Workload can be balanced across Phases and Iterations of a Project

Each project team can customize the configuration

Request

Task

Activity

Project and Plan definition

Work and

Delivery definition

Submitter•Submits request for change•(Validate release)


CRM 18 5

CQALM Out-Of-The-Box Schema - Objectives

Useful to 100% of new and existing ClearQuest customers Provide at least 70% of functionality out-of-the box

Scalable ALM model from Small teams to Enterprise Programs and Projects

Multisite and UCM enabled, but not required

Available as a download for CQ 7.0.1 users

Delivered with ClearQuest v7.1 as a set of packages and a schema

Reduce customer cost-of-ownership & improve ROI Reduce time to deployment by at least 50%

Remove the need for ‘one-size does not fit-all’ records with complex state transitions

Empower project managers & team leads to configure projects without impacting the schema

Reduce the amount of administrative changes needed to support enterprise users

Provide fundamental “building blocks” to get started Provide a secure Project Context with Role-based ‘allowed actions’

Govern projects using project and work tracking capabilities

Simplify the ability to support regulatory compliance initiatives

Out-of-box ALM Sample Database demonstrating OpenUP support

Gadzook

s!


CRM 18 6

Agenda



Work



Integrations Themes

UCM

Build Forge

RequisitePro

6

Ka-plow!


CRM 18 7

Core Concepts

Projects provide security, roles, and a context

Work is completed in the context of a project

There are system-wide settings that you can modify without having to change the schema

7

1

2

3


CRM 18 8

Introducing Projects

ProjectProject

CategoryCategory

RoleRole UserUser

super / sub

prev / next

ReleaseRelease

Project definition

Security-policySecurity-policy

GroupGroup

Existing ClearQuest

ALM System-wide settings

Work ConfigurationWork Configuration

Security Context

PhasePhase

IterationIteration

And others we’ll discuss later

Projects provide the context for doing work & are uniquely identified

Security determines visibility, Roles determine allowed actions for users

Phases and Iterations divide projects into time-boxed deliverables

Project definitions can change without modifying the schema

Projects provide the context for doing work & are uniquely identified

Security determines visibility, Roles determine allowed actions for users

Phases and Iterations divide projects into time-boxed deliverables

Project definitions can change without modifying the schema


CRM 18 9

Projects, Roles and Security

9

ProjectProject

RoleRoleUserUser

super / sub

prev / next

Project definition

Security-policySecurity-policy

GroupGroup

Existing ClearQuest


Security Context

1 Create Users and Groups

2 Create ALM Security Policy

3

5

Role LabelRole Label

4 Create ALM Role Label

Choose Security Policy

Create ALM Role

Security Policy determines who can see which projects

Role determines who can do what (Allowed Actions)

Security Policy determines who can see which projects

Role determines who can do what (Allowed Actions)


CRM 18 10

Creating a Security Policy

10

1 Provide a name and description

2 Add one or more CQ Groups

Note: Everyone group opens access

to all users


CRM 18 11

Creating a Role

11

1 Set the Project

2 Choose a Role Label

or Create a New one

3 Add users

4 Refine the Approved Actions


CRM 18 12

Projects Uniqueness

12

ProjectProject

CategoryCategory

super / sub

prev / next

super /

sub


1 Create ALM Categories

2 Create ALM Release Label(s)

3 Choose Category

4 Choose Release

Category Type Label

Category Type Label

Release LabelRelease Label

Category provides a classification

Release defines the version

Category provides a classification

Release defines the version

Project definition


CRM 18 13

Categories Classify Projects

13

Product AProduct A

ProductProduct Category Type LabelCategory Type Label

Category Category

Feature AFeature A CategoryCategory

Feature BFeature B CategoryCategory

Product BProduct B CategoryCategory



Service AService A

ServiceService Category Type LabelCategory Type Label

CategoryCategory

FeatureFeature CategoryCategory

FeatureFeature CategoryCategory

Service BService B CategoryCategory




CRM 18 14

Projects Planning & Work Configuration

14

ProjectProject

super / sub

prev / next



1 Create Phase & Iteration Label(s)

Create ALM Type(s)

Work TypeWork Type

3 Create Phase(s)

Phases & Iterations create time-boxed deliverables

Work Types define the ‘nature’ of the work

Work Configuration defines a recommended process

Phases & Iterations create time-boxed deliverables

Work Types define the ‘nature’ of the work

Work Configuration defines a recommended process

Project definition

RoleRole

2

PhasePhase

IterationIteration

Work Type LabelWork Type Label

Phase LabelPhase Label

Iteration LabelIteration Label4 Create Iteration(s)

5 Create Work Configuration(s)


CRM 18 15

Managing “Work”

15

RequestRequest

TaskTask ActivityActivity

UserUser

relatedrelated

Defect

Enhancement

New Feature

…

Defect

Enhancement

New Feature

…

Work and Delivery definition

Assess

Plan

Design

Implement

Test

Deploy

…

Assess

Plan

Design

Implement

Test

Deploy

…

Work TypeWork Type


Requests define the ‘need’ & where it was ‘found’

Tasks define the work needed to complete the request for a project

Activities are assigned to individuals & collectively complete the Task

Work Type identifies the ‘nature’ of the work

Requests define the ‘need’ & where it was ‘found’

Tasks define the work needed to complete the request for a project

Activities are assigned to individuals & collectively complete the Task

Work Type identifies the ‘nature’ of the work

related

ActivityActivity

ActivityActivity


CRM 18 16

Simple State Transitions

RequestRequest ActivityActivity

Opened

Withdrawn

Completed

Rejected

Open

Withdraw

Re-Open

AcceptAccept

Re-Open

ReOpen

Reject

Opened

Completed

Activated

Open

Complete

Activate

Complete

Re-Open

Activate

ReOpen

TaskTask

Submitted

Opened

Completed

Activated

Submit

Open

Complete

ReadyToWaiting

Activate

Activate

CompleteReOpen


CRM 18 17

CQ ALM Approach

Current Approach

Understanding the Context Switch

17

Replace one-size fits-all state transitions with Project defined activity setsReplace one-size fits-all state transitions with Project defined activity sets

Submit Develop Validate Close

Project Team A

Task (Defect)Task (Defect) Activity (Develop)Activity (Develop)

Activity (Validate)Activity (Validate)

Project Team B

Task (Defect)Task (Defect) Activity (Develop)Activity (Develop)

Activity (Review)Activity (Review)

Activity (Validate)Activity (Validate)

Request (Defect)Request (Defect)


CRM 18 18

The Flow

18

Requests are triaged, Tasks are created for projects

Activities complete the task

A completed task is reviewed and the request is closed.

Requests are triaged, Tasks are created for projects

Activities complete the task

A completed task is reviewed and the request is closed.

Initiate Request

Process Request

Process Task

Process Activities

Problem information Close or Withdraw Request

Submit Request

Accept or Reject Request

Create Task

Create Activities

Accept or Reject Task

Complete Activities


CRM 18 19

About Types & Work Configurations

19

A type of request may need a special type of task

A type of task may have its own set of activities

Work configurations define these ‘process policies’ for a project

A type of request may need a special type of task

A type of task may have its own set of activities

Work configurations define these ‘process policies’ for a project

RequestRequest

Defect

Enhancement

New Feature

…

Defect

Enhancement

New Feature

…

TaskTask

Defect

Plan Project

Design Architecture

Refine Requirements

…

Defect

Plan Project

Design Architecture

Refine Requirements

…

Develop DevelopActivityActivity

ActivityActivity

ActivityActivity

Review Review

Validate Validate


Request = Defect

Task = Defect

Request = Defect

Task = Defect


Task= Defect

Activites=Develop, Review, Test

Task= Defect

Activites=Develop, Review, Test


CRM 18 20

Builds and Baselines

20

BaselineBaseline

ActivityActivityActivityActivity

ActivityActivity

BuildBuild

ProjectProject

Baselines capture the set of completed activities

Builds track the status of the build

Testers use these to determine what to test

Baselines capture the set of completed activities

Builds track the status of the build

Testers use these to determine what to test


CRM 18 21

Baseline

21

1 Choose Project

2 Identify UCM stream

3 Identify PVOB or Location

4 List completed activities

(Diff Baselines)

Automate the creation of the Baseline and Build records as part of your build processAutomate the creation of the Baseline and Build records as part of your build process


CRM 18 22

Build

22

1

2 Set Build Type

and Build Status

Choose Project

3 Choose Baseline

Automate the creation of the Baseline and Build records as part of your build processAutomate the creation of the Baseline and Build records as part of your build process


CRM 18 23

System-wide settings

23

Type LabelType Label

Security PolicySecurity PolicyCategory Type LabelCategory Type Label

CategoryCategory

Role LabelRole Label

Release LabelRelease Label Work TypeWork Type

Iteration LabelIteration Label

Phase LabelPhase Label

Resolution Code LabelResolution Code Label

Status LabelStatus Label

System-wide labels

AdminAdmin

System-wide records

Labels let you use your vocabulary across the enterprise

System-wide records facilitate re-use & consistency across projects

Labels let you use your vocabulary across the enterprise

System-wide records facilitate re-use & consistency across projects


CRM 18 24

Agenda



Work



Integrations Themes

UCM

Build Forge

RequisitePro

24

BAM!


CRM 18 25

An Agile Iteration Example

25

Request (General)Request (General)

Task (General)Task (General) Activity (Implement)Activity (Implement)

related

Agile Work and Delivery definition

Activity (Test)Activity (Test)

Activity (Document)Activity (Document)

My ProjectMy Project

Activity (Document)Activity (Document)Activity (Document)Activity (Document)

Activity (Document)Activity (Document)Activity (Document)Activity (Document)

Activity (Implement)Activity (Implement)Activity (Implement)Activity (Implement)

Activity (Implement)Activity (Implement)

Activity (Test)Activity (Test)Activity (Test)Activity (Test)

Activity (Test)Activity (Test)Activity (Test)Activity (Test)

Activity (Implement)Activity (Implement)Activity (Implement)Activity (Implement)

Phase (Iteration)Phase (Iteration)

Iteration (1)Iteration (1)

Assign “Activities”

Manage by “Iterations”

Set a default Request for the project

Set a default Task for the Request

Activities automatically associated to Task

Assign “Activities”

Manage by “Iterations”

Set a default Request for the project

Set a default Task for the Request

Activities automatically associated to Task


CRM 18 26

Adaptive Workflow – OpenUP example

OpenUP (Open Unified Process)

An exemplary process in the Eclipse Process Framework project.

OpenUP is very similar the Rational Unified process and is scaled for Agile teams.

OpenUP downloads are available from the following URL: http://www.eclipse.org/epf/downloads/openup/openup_downloads.php nts


CRM 18 27


27

Role Label(s)Role Label(s)

1 Create Role Labels

Phase Label(s)Phase Label(s)

2 Create Phase Labels. Alternatively add Iteration labels

OpenUP (Open Unified Process)

An exemplary process in the Eclipse Process Framework project.

OpenUP downloads are available from the following URL: http://www.eclipse.org/epf/downloads/openup/openup_downloads.php nts


CRM 18 28


28

Task Type= Initiate ProjectTask Type= Initiate Project

Activity Type= Define Vision, Role = Analyst

Activity Type= Define Vision, Role = Analyst

Activity Type= Plan Project, Role= Project Manager

Activity Type= Plan Project, Role= Project Manager

Work Configuration for Task= Initiate Project,

include the above Activities & Roles

Work Configuration for Task= Initiate Project,

include the above Activities & Roles

3 Task Types Map to the Lifecycle

Activity Type Maps to lifecycle step4

Work Configuration binds them5


CRM 18 29

OpenUP Example – Inception Phase

Task (Initiate Project)Task (Initiate Project)

Activity (Detail Reqs)

Activity (Detail Reqs)

Activity (Outline Reqs)

Activity (Outline Reqs)

Act. (Manage Iteration)

Act. (Manage Iteration)Act. (Plan Iteration)Act. (Plan Iteration)

Activity (Outline Architecture)

Activity (Outline Architecture)

Act. (Plan Project)Act. (Plan Project)Act. (Define Vision)Act. (Define Vision)

Task (Manage Iteration)Task (Manage Iteration)

Task (Identify Reqs)Task (Identify Reqs)

Task (Technical Approach)Task (Technical Approach)

Act. (Assess Results)

Act. (Assess Results)

Request (Run Project)Request (Run Project)


CRM 18 30

Defect handling Options

Task (Fix)Task (Fix)

Request (Defect)Request (Defect)

Task (Implement)Task (Implement)

Request (Feature)Request (Feature)

Task (Defect)Task (Defect)

Act. (Test)Act. (Test)

Act. (Develop)Act. (Develop)





Task (Implement)Task (Implement)

Request (Feature)Request (Feature)



Act. (Defect)Act. (Defect)

Defect = Request Defect = Task Defect = Activity

Multi-projects

Reports where request=defect

Trace Defects to Feature on Request record

Trace Defects to Feature on Task record


CRM 18 31

Agenda



Work



Integrations Themes

UCM

Build Forge

RequisitePro

31

Kowabu

nga!


CRM 18 32

GDALM Integration Themes

Alignment of Work Ability to turn release requirements into project and component iteration plans

and provide visibility into those plans for health tracking through the lifecycle.

Requirements Driven Development and Testing Ability for test cases to align with requirements for validation.

Defect Management The flow of a defect and how it impacts development, test, and iteration plans.

The visibility and ability to report defects back from testing, allowing leads and developers can act upon them

Build Clarity & Quality Ability to determine when Requirements are implemented in the build and what

Defects are fixed. Ability to trace from builds to coverage, result and quality metrics.


CRM 18 33

Integration Use Cases

Create SketchManage Requirements

Plan Iteration w/ WorkItem

Reuse*, Develop, Test, Build and Deliver changes

Integrate and Build

QM

Plan Tests w/ WorkItem

Alternate UCM workflow

Test integration buildWatchFire AppScan integrated

Submit defect

Rational Analyzer, ClearQuest and ClearCase integrated

IBM Rational Build Forge

IBM Rational Team Concert

IBM Rational RequisitePro IBM Rational RequisitePro Composer

IBM Rational ClearQuest

IBM Rational Quality Manager

Triage RequestsPlan Iterations w/ Task & Activities


CRM 18 34

Putting it all together

34

ProjectProject IterationIteration

RequestRequest TaskTask ActivityActivity

CategoryCategory

RoleRole

UserUser

related related related

prev / next

super / sub

prev / next

Defect

Enhancement

New Feature

Defect

Enhancement

New Feature

ReleaseRelease

super /

subProject definition

Work and Delivery definition

BuildBuild

BaselineBaseline

Failed_in

Validated_in

Fixed_in

Assess

Plan

Design

Implement

Test

Deploy

Assess

Plan

Design

Implement

Test

Deploy

Security-contextSecurity-context

Group Group

PhasePhase

prev / next

Delivered as a schema and as two packages (ALMProject, ALMWork)

Delivered as a schema and as two packages (ALMProject, ALMWork)



CRM 18 35

Improving ROI – early indicators

Cost savings on a “real” engagement 5 months duration, 30-42 days of billable time

Details: Schema Requirements

1 month duration: customer meetings, documentation and review.

5-7 days of billable time Schema Design

1 month duration: customer meetings, documentation, and review.

5-7 days of billable time Schema Implementation

3 Iterations over the course of 3 months 15-20 days billable time

Develop Custom Training for end users 5-8 days billable time Activities performed during the schema

implementation iterations

Design Time Reduced by 50%.

Requirements TimeReduced by 25%.

Implementation Time Reduced by 66%.

Training Time Reduced by 50%.

ALM schema Reduced to 2 months Duration

10-15 days billable time

CRUNCH!


CRM 18 36

Early Adopters & Other Opportunities ClearQuest early adopters

Several Rational field-driven early adopters

Providing design discussion & feedback

Internal IBM early adopters Information Management, Tivoli, RATLC, Collaboration with URMS team

ALM Redbook public draft Includes major sections CQALM and Team Concert, including interop scenarios

Available at the IBM Redbooks website

36


CRM 18 37

Provides Visibility to: RequisitePro for Requirements Management

and Trace Relationships Asset Manager (RAM) to Cooperatively

Develop & Reuse Assets ClearCase/UCM for Version Control of

Development Activities Team Concert for Small, Agile Teams

Partner Extensibility for Inclusion of Complementary Solutions

CQALM Provides an ALM Hub

37

Benefits:

Integrated with Rational Products Providing Full Development Lifecycle

Simplify Compliance Reporting

CQALM

ClearCase / UCM

Team Concert

Quality & Test Lab Manager

RequisitePro

RAM

Practitioner Tools

Portfolio Manager


CRM 18 38

Summary

Projects provide security, roles, and a context

Work is completed in the context of a project by using Requests, Tasks and Activities

There are system-wide settings that you can modify without having to change the schema

Reduce CQ Administration time

Empower Project teams to configure the project for their own needs

Tester•Test changes in baselines

Release Engineer•Integrate and build delivered changes•Create baselines

Test Lead•Ensure quality ProjectProject

CategoryCategory

ReleaseRelease

Change Control Mgr•Triage requests•Assigns tasks to projects

Change performed in the context of

Request

Task

Activity

Project and Plan definition

Work and

Delivery definition

Submitter•Submits request for change•(Validate release)


CRM 18 39

Additional Information

DeveloperWorks article 1: http://www.ibm.com/developerworks/rational/library/edge/08/mar08/pampino-

pierce/index.html

article 2:http://www.ibm.com/developerworks/rational/library/edge/08/apr08/pampino-pierce/index.html

ALM Redbook Public Draft


CRM 18 40

QUESTIONS


CRM 18 41

WANT MORE?


CRM 18 42

Come Talk to us!CRUN

CH!

Kowabu

nga!

BAM!

Ka-plow! Gadzook

s!

Pow!


CRM 18 43

© Copyright IBM Corporation 2008. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, the on-demand business logo, Rational, the Rational logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

Learn more at: IBM Rational software IBM Rational Software Delivery Platform Process and portfolio management Change and release management Quality management Architecture management

Rational trial downloads Leading Innovation Web site developerWorks Rational IBM Rational TV IBM Rational Business Partners

THANKYOU

ZOINK!

Documents

CRM 18 IBM Rational Software Development Conference 2008 © 2007 IBM Corporation ® Introducing Application Lifecycle Management on IBM ® Rational ® ClearQuest