Appendix: Rational® Solution for Collaborative …...Lifecycle Management Architect Analyst Developer Quality professional Deployment engineer The Rational solution for Collaborative

© Copyright IBM Corporation 2011

Appendix: Rational® Solution for Collaborative Lifecycle Management

2 © Copyright IBM Corporation 2011

Module objectives

After completing this module, you will know this

information:

The concepts behind the Rational® solution for Collaborative

Lifecycle Management (CLM)

The benefits of the CLM approach

How to access CLM resources


What’s next?

> = Current topic

>Explain the Rational® solution for

Collaborative Lifecycle Management

(CLM)

Express the benefits of the CLM

approach

Access CLM resources


Silos create barriers to software delivery

Silos can cause these kinds of issues:

Lack of communication and collaboration

Deliverables “thrown over the wall” to the next team

Lack of accountability and information transparency

Difficulty understanding dependencies and managing change

Analysts Quality professionals

Release engineersDevelopers

Architects

Project managers


CLM means a whole-team, whole-view approach

Analysts Quality professionals

Release engineersDevelopers

Architects

Project managers

Collaborative Lifecycle Management (CLM) coordinates the lifecycle activities of software development, and helps answers questions like these:

• What requirements and defect fixes are in this release?

• Are we getting better at managing requirements scope?

• What has changed that I have to test?


The Rational solution for Collaborative Lifecycle Management

RationalRequirements

Composer

RationalTeam

Concert

RationalQuality

Manager

The Rational solution for Collaborative

Lifecycle Management

Architect

Analyst Developer

Qualityprofessional

Deploymentengineer

The Rational solution for

CLM is a turnkey CLM

solution that is built on

the Jazz platform that

provides key software

development lifecycle

capabilities through

three applications.



Composer

RationalTeam

Concert

RationalQuality

Manager



Architect

Analyst Developer

Qualityprofessional

Deploymentengineer

The Rational solution for Collaborative Lifecycle Management

The Rational solution for CLM

provides these values:

Real-time planning

Lifecycle traceability

In-context collaboration

Development intelligence

Continuous improvement


CLM and your process

Scrum TraditionalIterative

Lighter

process

Heavier

process

The Rational solution for CLM supports many processes.

The solution provides ready templates for agile, iterative, and

traditional workflows. You can customize these templates, and

with them you can complete these tasks:

Change processes quickly, as part of a continuous feedback loop

Allow team leads to determine how strict or loose the rules should be

Modify process enforcement over the life of a project, to encourage early-

stage experimentation and end-game stability


The Money that Matters™ lifecycle project sample

The project sample comes as part of the Rational solution for CLM.

The sample includes a rich set of requirements, plans, work items, source code, build definitions, test plans, test cases, and test scripts.

The sample is easily deployed from the Rational solution for CLM Lifecycle Project Administrationuser interface.


Optional demonstration

The instructor will complete these steps:

Log into a CLM application as Bob the analyst, using the indicated ID and password

Log into a CLM application as Marco the developer and quality professional, using the indicated ID and password


What’s next?

> = Current topic

Explain the Rational® solution for


(CLM)

>Express the benefits of the CLM

approach

Access CLM resources


Let’s return to the value that CLM brings


Composer

RationalTeam

Concert

RationalQuality

Manager



Architect

Analyst Developer

Qualityprofessional

Deploymentengineer

1. Real-time planning

2. Lifecycle traceability

3. In-context collaboration

4. Development intelligence

5. Continuous improvement


Tasks

completed

Tasks

planned


Real-time planning is project planning that is directly linked to

execution.

Real-time planning helps you

to avoid these problems :

Plans that are disconnected

and managed separately

Plans with manual, error-

prone updates

Plans that are separate from

team activities and

assignments


Real-time planning improves time to delivery

Architect

AnalystDeveloper

Qualityprofessional

Deploymentengineer

Project lead

Provides a single plan that spans requirements, development, and testing, ensuring that a team understands the overall scope of a project

Enables everyone to participate in keeping the plan current and accurate

Integrates planning with execution, ensuring that the entire team understands actual project status

Helps teams respond to the unexpected in a timely manner,ensuring that teams stay on schedule


Multiple plan views facilitate continuous planning

2

1

3


Developers

understand the

business needs and

test effort.

Testers understand plans and business

expectations.

Requirements owners clarify the business

needs in a collection.

Align plans to improve predictability, value, and quality

Aligned plans means no wasted effort. Development can focus on quality. Efforts align with the agreed upon requirements at the right time.

Aligned plans means higher quality. Test teams know exactly what requirements and functions have and have not been tested.

Aligned plans means whole-team buy-in. Team trust, efficiency, and focus are improved

http://pokgsa.ibm.com/home/j/i/jinli/web/public/html/arch_ken.html


Plans consider the entire team, including requirements and testing

Linked to requirements collection

Linked to a test plan


Requirements collections focus teams on release goals

Collections focus the team:

On reviews

On snapshots

On implementation


Rankings improve clarity

With rankings, teams can clearly and visually understand the

goals.Priorities are good to

use, but rankings are

better.


Plan at the right level of detail, and tie plans to execution

Everyone participates in planning. Deliverables and work

products show results.

Plans include

all types of work and all

team members.

Stories are decomposed

into the right set of

tasks.

Progress and status are good

indicators of execution. Change

sets and attachments are better

indicators.



Lifecycle traceability: The ability to gain end-to-end insight into

your project lifecycle and to identify meaningful connections

between software development and delivery activities.

What defects are reported against which requirements?

What tradeoffs can we make

to release on time?

Project managerAnalyst

Quality professionalRelease engineerDeveloper

What has changed

that I have to test?

How can I accelerate my builds?

What testuncovered this defect,on which environment,

and what build?


The benefits of lifecycle traceability

Lifecycle traceability establishes relationships

between software artifacts. This relationship has

compelling benefits :

Helps you identify and close artifact gaps, ensuring

coverage across disciplines

Provides information about the completeness of planned

items by enabling teams to inspect all related artifacts

Provides easy access to related artifacts, ensuring

everyone shares the same view

Delivers transparency, which enables everyone to make fully

informed decisions that are based on business priorities


Lifecycle projects provides traceability

When you create a lifecycle project, the solution creates three

project areas for you and associates them.

This association enables you to link artifacts across the project

areas.


Lifecycle project artifacts can link to each other

In a lifecycle project, these types of artifact links are predefined

for you. Note that some are work-item artifacts.


Artifact linking enables alignment throughout the lifecycle

Requirements

collection: What to

develop

Release plan: When it

will be developed

Test plan: How to test

the implementation and

validate that the

requirements are met

The product owner: Wants to ensure that a requirements collection has relationships to a release

plan and a test plan.

Wants to create a traceability view on a requirements collection

The development lead: Wants to ensure that a release plan has relationships to a requirements

collection and test plan

Wants to synchronize collections and release plans

Wants to create a traceability view to the release plan

The test lead: Wants to ensure that a test plan has relationships to a requirements collection

and release plan

Wants to synchronize collections and test plans


Developers understand the requirements,

test results, and test criteria.

Testers define and execute test

cases with a clear understanding of

requirements.Teams collaborate and clarify the details of

requirements.

Plan-item traceability improves quality and predictability

Everyone's work aligns with the requirements and goals of the customer

Team members have access to and can see each others’ most up to date work

All work is linked and visible, giving the team insight into when all work is done



Linked data is visible on all artifacts

All roles can view the links on

their artifacts.

All users have their own

perspectives and user

interfaces for viewing links.

All users can create, delete,

and navigate links on artifacts.

All defects have traceability

links created automatically

All roles can view the links on their

artifacts.

All users have their own perspectives

and user interfaces for viewing links.

All users can create, delete, and

navigate links on artifacts.

All defects have traceability links

created automatically


Developers can see and

remediate the exact test

failure without having to ask.

Testers execute tests and submit to

Rational Team Concert defects.

Automated defect traceability reduces costs and improves quality

Four clicks to submit a defect that is automatically linked to impacted artifacts.

Test results are recorded and linked to test cases and associated requirements.

Test results can be linked to software builds.

Everyone can see defects, their impact, and the action taken to resolve them.


Developers have full access to the requirement that they are implementing

Rich hover

information

provides insight at

your finger tips

and reduces time

to value.

Links provide

valuable

information on

requirements


Team leads can view coverage and completeness

Tailor the traceability view to highlight planning gaps



In-context collaboration is the ability to collaborate in real-time on projects in

the context of the work being done.

This collaboration helps you avoid

these issues:

Silo teams and disconnected data

Chat and discussion threads that

are disconnected from project activity

or lost in archives

Project records that are missing the

real reasons for decisions

Difficulty in fully informing new team

members

31

www


In-context collaboration always shows the most recent…

…discussions highlighted on requirements

….unread work items bolded for developers

…threaded

discussions on

requirements


Viewlets focus the team on recent comments and changes

Feeds for all changes inform project leads about all requirements changes so they know exactly what is being changed and by whom. They can immediately assess the impact on the team.

Feeds focused on requirements comments focus stakeholders on changes and strip out the noise of attribute changes and so on.


Glossaries provide a common vocabulary for teams

Glossaries can provide a

common vocabulary for teams

to refer to and share.


Comments on requirements details are in-context

You can click a comment in a discussion to highlight

the requirements text under discussion.


Formal reviews drive agreement and prevent rework

Reviews and approvals are effective to :

Ensure artifacts are reviewed or approved by key team

members

Capture compliance requirements

Test artifact Requirement Work item



Development intelligence means using measurements to make

fact-based business decisions and to steer projects and

programs to be delivered on-time.


Use dashboards to provide a view of project health

This image shows reports on the development team within a

project dashboard.


DimensionsTeam

(In process)

Middle management

(Development mgmt.)

Development executive

(VP development)

Time-to-value

(Schedule)

User-story points and use-case points

Iteration burndown, blocking work item

Release burndown

Product value Iteration velocity

Stakeholder feedback, no. of enhancement requests, enhancement request age

Tested and delivered requirements, business value

velocity, customer satisfaction

Product cost Effort (man-hours)

Cost per unit of work

Development and

maintenance costs

Product quality Technical debt (defect trend, defect density)

Test status, test coverage of requirement, test execution status

Quality at ship

Predictability User-story Points and use-case points

Planned versus actual cost and velocity

Trend variance. Likelihood of on-time delivery

Use metrics appropriately at every level

Note: Boldface indicates that there is out of the box report provided by the Rational solution for CLM.


Example: Measuring product quality

The defect trends report

shows defect arrival and

closure rates,

determines the remaining

defect backlog, projects the

future defect arrival and close

rate up to and post-delivery.

The test execution status

report monitors test completion

and success.


Step 1Adopt

Scrum

Traditional

Iterative

Project C

Traditional

Project B

Project A

Agile

Iterative

Product owner

Scrum master

Team member

Analyst, manager

Architect, developer

Quality professional

Release engineer

Analyst, manager

Architect, developer

Quality professional

Release engineer

Step 2Enact

Step 3Measure

Step 4Improve

5. Continuous improvement

Continuous improvement is adopting, enacting, measuring, and then

improving your processes in a continuous cycle.


Continuous improvement reduces cost:

Promotes ongoing adoption of best practices and

automation to reduce manual, non-creative, and error prone

tasks

Promotes incremental improvement of a project when

needed

Enables breakthrough improvement by capturing best

practices and reusing them among teams

Encourages everyone to participate with easy-to-adopt best

practices at your fingertips.

Benefits of continuous improvement


Project : Retail

Project : Savings

Process Templates on Server: JKE.tools.com:9443/JTS

Scrum TraditionalIterative

Web banking

Team : Core

Team : UI

Team : Benefits

Using best practices from Rational software and other teams

Import and export templates provide

the ability to use best practices from

Rational software and other teams.

Servers support multiple templates,

and enable administrators to

support different processes.

Teams improve their process

independently.

Process updates can be shared

Teams can control when they want

to accept improvements.


Team retrospectives help identify areas for improvement

Retrospectives help team members to collaborate on

improvements. Teams can achieve these results :

Rank process improvements to focus on where they feel the biggest pain.

Use metrics where available to support process improvements and show

results.


Story

(work item)

Child items

Task

(work item 468)

Analyst

Complete feature

Task

(work item 469)

Developer

Estimate

Task

(work item 470)

Quality Professional

Plan test cases

Example problem: A story is completed without all work completed



Solution: Require detailed tasks be complete before a parent can be marked as complete


In this module, you have learned this information:

The importance of the Rational® solution for Collaborative

Lifecycle Management (CLM)

How the Rational solution for CLM provides these features:

– Lifecycle traceability

– Real-time planning

– In-context collaboration

– Development intelligence

– Continuous improvement

Module summary


Discussion

Working in small groups, explain to your group which of

these five values you would choose to implement

first and why?





5. Continuous process improvement


What’s next?

> = Current topic

Explain the Rational® solution for


(CLM)

Express the benefits of the CLM

approach

>Access CLM resources


Further enablement

IBM Rational training paths: Change and Control Management

– http://www-304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=page&c=N917813V88042E72

Requirements Definition and Management

– http://www-304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=page&c=B018408P55026H42

Quality management

– http://www-304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=page&c=F825709H30198F39

Jazz.net library: CLM 2011 Upgrade workshop - https://jazz.net/library/article/662

CLM 2011 Reporting workshop (coming soon)

CLM 2011 Installation workshop (coming soon)

Also search the Jazz.net library at https://jazz.net/library/ in the Collaborative Lifecycle Management project for more articles, tips, presentations and so on.

http://www-304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=page&c=N917813V88042E72

http://www-304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=page&c=B018408P55026H42

https://jazz.net/library/article/662

https://jazz.net/library/


“Money that Matters” sample application and usage scenario

Use the “Money that Matters” fictional scenario to learn and to develop ideas on how you can best apply the Rational solution for CLM to your benefit.

Home page: https://jazz.net/wiki/bin/view/Main/MTM_Lifecycle_Welcome

Scenario explanation and steps: https://jazz.net/wiki/bin/view/Main/MTM_Lifecycle_Scenario

Detailed tutorial based on Money that Matters lifecycle scenario:

http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=/com.ibm.rational.clm.tutorial.doc/topics/tut_alm_abstract.html

https://jazz.net/wiki/bin/view/Main/MTM_Lifecycle_Welcome

https://jazz.net/wiki/bin/view/Main/MTM_Lifecycle_Scenario

http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=/com.ibm.rational.clm.tutorial.doc/topics/tut_alm_abstract.html


Documents

Appendix: Rational® Solution for Collaborative …...Lifecycle Management Architect Analyst Developer Quality professional Deployment engineer The Rational solution for Collaborative