75
IBM Rational solution for Collaborative Lifecycle Management

Collaborative Lifecycle Managmenent - an Introduction

Embed Size (px)

DESCRIPTION

An introduction to collaborative lifecycle management with Rational Team Concert

Citation preview

Page 1: Collaborative Lifecycle Managmenent - an Introduction

IBM Rational solution forCollaborative Lifecycle Management

Page 2: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Agenda

Current market situation

Proven results

1

44

Delivering the 5 ALM imperatives 3

IBM Rational Collaboration Lifecycle Management2

Page 3: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us3

Software is integral to business success– Software is woven through systems, products and services, helping companies bring new – smarter –

innovations to market.

Market realities are pushing organizations to innovate with less– The ability to innovate is impacted by market realities such as increasing complexity, tighter budgets and

a more demanding competitive landscape

Integrated Application Lifecycle Management (ALM) provides the ability to innovate while reducing overhead costs

– Improve time to delivery, quality, value, and predictability with integrated Application Lifecycle Management combined with best practices for scaling agility.

The IBM Rational Collaborative Lifecycle Management Solution provides capabilities that fully support an integrated ALM approach

– Allows organizations to coordinate people, processes, and tools for requirements management, development and quality management by providing traceability across lifecycle artifacts, process definition and enactment, and reporting.

Executive Summary

Page 4: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Software drives today’s innovation for a smarter planetTransforming the way we live, work, and play

Page 5: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

The defining challenge: Managing “systems of systems”From back-end software to customer facing portals, systems of systems drive your relationships with customers, suppliers and business partners

Software-drivenInnovation

COMPLEXITY

Service-oriented Architecture (SOA)

Cloud / SaaSEnd-userWeb Application

Mobile Device Access

Third-party IP

Partner Code

Commercial Off-the-shelf

In-house Development

Outsourcedand GloballyDistributed

Open Source

Legacy and

Re-use

Page 6: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us6

The convergence of physical assets and IT applications requires a new approach for integrating products and services

Unique Value is unleashed through an Ecosystem of Intelligent “Systems of Systems”

Page 7: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Forrester estimates that ongoing operations and maintenance consume 66% of IT budgets While new projects and software initiatives represent only 34%

66%

34%

Business and IT Agility: Balancing Resources to Support Business InnovationBalance IT investments to focus on new solutions.

7

Page 8: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Integrate, Instrument & ImproveHelp me oversee this entire value chain and incrementally improve

8

Key Software development lifecycles

DecideHelp me make strategic decisions

DevelopHelp me develop what I decide

DeployHelp me deploy what I develop

3 inter-related lifecycles of activity involving different goals, timelines, roles, processes and tools

8

Page 9: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Measured Improvement

9

Enterprise Architecture and Portfolio Planning

Application Lifecycle Management

Deployment Planning & Automation

9

Key Software development lifecycles

Page 10: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

ALM is about connecting the disciplines

Continuous Learning and Feedback

Requirements• Use Cases• Nonfunctional• Sign-off• Contract• Risk Assess• Threat Model• Test

Requirements

Project/Planning• Business

Drivers• Iterations• Sign-off• Contract• Risk Assess• User

Involvement

Development• TDD• Build

Management• Static

Analysis• BVT• Source

Management• Pair

Programming/Code Review

Testing• Scenario-

Driven Automation

• Exploratory Test

• User Involvement

• Contract Validation

Source: Gartner Application Architecture, Development & Integration Summit Presentation, The Future and Present of AD, Thomas E. Murphy, December 2008

10

Page 11: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Rational Application Lifecycle Management (ALM)Modular, open and extensible

Build & DeployManagement

RequirementsManagement

Software, Change & ConfigurationManagement

Quality Management

DesignManagement

11

Page 12: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Agenda

Current market situation

Proven results

1

44

Delivering the 5 ALM imperatives 3

IBM Rational Collaboration Lifecycle Management

2

12

Page 13: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Rational solution for Collaborative Lifecycle Management

An ALM solution powered by Jazz

*extensions

CREATE SOFTWARE

Real-time Planning, Lifecycle Traceability, Team Collaboration, Development Intelligence, Continuous Process Improvement

Requirements Management

Planning, Change, Configuration & Build

Management

Quality Management

Rational Requirements

Composer

Rational Team Concert

Rational Quality Manager

13

Page 14: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Jazz provides open collaboration across the software and systems lifecycle

PLATFORMOpen Services for Lifecycle Collaboration

Integration services

COMMUNITYTransparent collaboration and exchange of ideas

Application frameworks and toolkits

PRODUCTSApplication lifecycle tools that leverage the Jazz platform

14

Page 15: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

The Open Services initiative is Building a community of vendors, open source

projects, integrators and IT teams, at open-services.net

Creating public specifications of resources and services, like change requests, test cases, defects, requirements and user stories

Delivering loosely coupled resource formats and services with “just enough” standardization

An industry initiative for simplifying tool integration across the software lifecycle .

Open Services for Lifecycle Collaboration

Barriers to sharing resources across the software lifecycleMultiple vendors, open source

projects, and in-house toolsPrivate vocabularies, formats

and storesEntanglement of tools and data

15

Open interfaces. Open possibilities.

Page 16: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Team advisor for defining / refining “rules” and enabling continuous improvement

Process enactment and enforcement In-context collaboration enables team members

to communicate in context of their work

Single structure for project related artifacts World-class team on-boarding / offboarding

including team membership, sub-teams and project inheritance

Role-based operational control for flexible definition of process and capabilities

Jazz Team Server

Component based SCM enables reuse across projects

Change set based for easy addition or removal of features

Server-based sandboxes

Can also work with SVN, Git, ClearCase or Synergy

SCM Work Items Defects, enhancements

and conversations View and share query results Support for approvals and

discussions Query editor interface ClearQuest or Synergy Bridge

Automated Work item and change set traceability

Build definitions for team and personal builds

Local or remote build servers Multi-level continuous

integration Integration with Build Forge

Build

PlanningIntegrated release/iteration planningEffort estimation & progress tracking taskboards Out of the box process templates: formal or agile

Project Transparency Customizable web based dashboards Real time metrics and reports Project milestone tracking and status

Rational Team Concert: A Closer Look

Page 17: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Advanced source code management

Easily suspend and resume work

Reproduce the exact workspace of any build

Work in parallel without making branch copies

Page 18: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us18

Team of Team Stream

Team Streams

Developer Streams

Work on multiple product versions and teams while maintaining order

Page 19: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Simple, web-based, document versioning

Have technical writers who need to version documentation (Word docs or PDF files) using a web UI? Don’t want to know about streams or accept/deliver, just want to version and store documents? Easily manage locking to ensure exclusive write access

Page 20: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us20

Easily import Bugzilla, Jira*, or any other change tracking system with CSV file support into RTC Work Items

Easily import Subversion and CVS repositories into RTC SCM

Importers also available for ClearCase / ClearQuest for those moving to RTC

Connectors available to provide dynamic integrations with Subversion, ClearCase, ClearQuest, Synergy, Change

RTC works with your existing tools

Page 21: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Repository Workspace(Private Builds)

good buildfailed build

Weekly Integration Stream(Product Builds)

deliver/accept

Developers deal mainly with accepting and delivering to their team stream. Flowing changes to and from the product and weekly integration streams provides multi-level staged continuous integration support across a complex system.

Each build references a snapshot of the artifacts that were built. Reproducing a build or patching a build is as simple as creating a new stream from the snapshot.

RC2

RC2 Stabilization Stream

Team Stream(Team Builds)

deliver and accept change sets

Continuous Integration Stream(Product Builds)

deliver and accept baselines

suspend/resume

Continuous integration/buildsIncremental and flexible integration with a great reduction in complexity

Page 22: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us22

Build auditing

Page 23: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us23

From Team Concert Web UI:Request new buildRequest rebuild of existing build

Exposes build facilities to wider community

Provides access to build function from any desktop

Build when you need to, from anywhere to anyone

Page 24: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Enterprise build support…with flexible build engine typesThere are now multiple types of build engines: Jazz Build Engine, Rational Build Forge, and

Rational Build Agent

This allows the engine and its configuration to be shared across multiple definitions, and for definitions to support multiple engines. Different projects may now define their own engines.

Page 25: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Agenda

Current market situation

Proven results

1

44

Delivering the 5 ALM imperatives 3

IBM Rational Collaboration Lifecycle Management2

25

Page 26: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us26

What is required to deliver end-to-end visibility across teams, tools and projects?

Page 27: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Criteria for effective lifecycle management: ALM imperatives

1. Real-time planning

2. Lifecycle traceability

3. In-Context collaboration

4. Development intelligence

5. Continuous process improvement

27

Page 28: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Imperative 1: Real-time planning

Don’t Do

Have plans that live outside of ALM environment where requirements, development and test plans are disconnected and managed separately, or not at all.

Plan across the entire team, not silos, by linking and populating development and test plans from requirements.

Rely on manual, error-prone updates. Practice continuous planning using lifecycle queries and project dashboards to respond to changing events.

Have plans that are separate from team activities and assignments.

Use plans that are fully integrated with execution where updating time spent directly from the work item makes easy to keep accurate plans.

TasksComplete

TasksPlanned

28

Page 29: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

One plan - Multiple views facilitate detailed analysis

29

2

3

1

Page 30: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Insure alignment across the business, development and test teams

30

Page 31: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us31

Align Plans to improve predictability, value, and quality

Developers understand the business needs and test effort

Developers understand the business needs and test effort

Testers understand Sprint Plans and business expectations

Testers understand Sprint Plans and business expectations

Requirements owners clarify the business needs in a collection

Requirements owners clarify the business needs in a collection

No wasted effort – development is qualitative and aligned to the agreed upon requirements at the right time

Quality Assured – test teams know exactly what requirements and functionality have and haven’t been tested

Whole team buy-in improves team trust, efficiency and focus

Page 32: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Test your real-time planning capabilitiesCan your team…

Plan across the entire team?

Plan for waterfall, iterative and agile environments?

Integrate planning with execution?

Instantly see the impact of a change in project scope or resources?

32

Page 33: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Imperative 2: Lifecycle traceability

Don’t Do

Create silos of information with disconnected and incompatible tooling and terminology

Link deliverables and connect the dots so every deliverable has the proper upstream and downstream relationship

Email copies of deliverables to remote team members and break linkages

Share links to deliverables with related deliverables context including reviews and comments from other team members

Integrate by replicating data Link critical project deliverable so that the entire team have access to the latest version of the truth

Code

Test Scripts

DefectsStories

Builds

Sprint

33

Page 34: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us34

Team leads improve release quality & predictability

Proactively respond to gaps as they surface through out the project

Issues quickly highlighted and resolved

Issue

Incomplete

Complete

Page 35: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us35

Team leads can improves quality and predictability

Developers understand the requirements, test criteria and test results

Developers understand the requirements, test criteria and test results

Testers define and execute tests cases with a clear understanding of requirements

Testers define and execute tests cases with a clear understanding of requirements

Teams collaborate and clarify the details of requirements

Teams collaborate and clarify the details of requirements

Creating a shared vision delivers what the stakeholders want

Whole team buy-in improves team trust, efficiency and focus

Everyone knows what work is needed by whom and when.

Traceability provides insight to knowing when you are DONE!

Page 36: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Linked data is visible on all artifacts

All roles can view the links on their artifacts.

Each user has their own perspective and user interface for viewing links.

Create, delete, navigate links on artifacts

Example: Developer sees the relationships on a defect

Traceability links on defects are automatically created

36

Page 37: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us37

Automated defect traceability reduces costs and improves quality

4-clicks to submit a defect 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 has visibility into the defects, their impact, and the action taken to resolve them Developers can see

the exact test failure without having to ask and remediate it

Developers can see the exact test failure without having to ask and remediate it

Testers execute tests and submit defects

Testers execute tests and submit defects

Page 38: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Which requirements are addressed in this iteration?

Are all of therequirements tested?

What’s the quality of the high priority requirements?What defects are reported

against which requirements?

Are we ready to release?

What tradeoffs can we maketo release on time?

Can we passan audit?

What defects were resolved in this release?

Project ManagerAnalyst

Test your lifecycle traceability capabilitiesCan your team answer these questions…

Quality ProfessionalRelease EngineerDeveloper

What is the quality of the build? What

has changed that I need to test?

What defects have been addressed since the last build?

How can I standardize when teams use different tools?

Where are the bottlenecksin our processes?

How can I speed up my builds?

Are build timesgetting longer

or shorter?

What requirementsam I implementing? What test

uncovered this defect,on which environment

and what build?

What changes occurred overnight?

How can I recreate thelast version to do a patch?

38

Page 39: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Imperative 3: In-Context collaboration

39

Don’t Do

Create an environment of silo’d teams and disconnected data

Unified teams share linked data providing visibility into each others work.

Manually collect status reports or wait for status meetings to take action Collaboration is also about knowing what is going on

without having to ask. Dashboards and traceability views provide real-time status of the team’s progress.

Rely on email discussions. All discussions in work items integrated on the plan. Use lifecycle queries to answer more meaningful questions such as “Which requirements are affected by defects?

39

Page 40: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

In-context Collaboration always shows the latest

Unread work Items bolded for developers

Threaded discussions on requirements

Recent Threaded discussions highlighted on requirements

40

Page 41: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Dashboards summarize for quick access to the latest information

Requirements comment updates

Feeds focused on Requirement comments focus stakeholders on changes and strip out the noise of attributes changes etc..

Any changes to a Requirement

Feeds on all changes give project leads visibility into all requirements changes so that know exactly what is changing by whom and can access immediately assess the impact for the team.

41

Page 42: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Rich hovers automate information access without having to click

42

Rich hovers provide quick access to information to determine if additional details are required!

Page 43: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Test your collaboration capabilitiesCan your team…

Easily access the “single source of the truth” through linked artifacts?

Quickly grasp the “who, what, when and why” of team activities?

Bring new team members up-to-speed quickly?

Overcome the barriers of multipletime zones when working with outsourced and distributed team members?

43

Page 44: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

If Measurement is so important, we must be doing it a lot, right?

Source: Capers Jones, Measurement, Metrics and Industry Leadership, 2009 and Software Engineering Best Practices, McGraw Hill, 2010.

Fortune 500 firms with: Quality measures: 45% Productivity measures 30% Complete measures: 15%

Impact of not measuring

Strong Weak

Projects with strong versus weak measurement practices

44

Page 45: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Don’t Do

Manually collect data by hounding the team for status reports.

Use live dashboards that provide transparency of information and dashboard reports based on data coming from the team’s activity.

Take a ‘big bang’ approach to instituting measures Identify a weak spot or a current pain point or bottleneck.

Don’t expect to get it right the first time. Conduct retrospectives to discover what worked, what didn’t work, and how you can improve.

Imperative 4: Development Intelligence

45

Page 46: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Dimensions Team(In Process)

Middle Management(Development Mgmt.)

Development Executive(VP Development)

Time-to-Value (Schedule)

User Story Points / Use Case PointsIteration Burndown, Blocking Work Item

Release BurndownProduct Value Iteration Velocity

Stakeholder Feedback, # of Enhancement Request, Age of Enhancement RequestTested and Delivered Requirements, Business Value Velocity,

Customer SatisfactionEffort (Man-hours)

Cost / Unit of workDevelopment / Maintenance

CostsTechnical Debt (Defect trend, defect density)

Test Status, Test Coverage of Requirement, Test Execution StatusQuality at Ship

User Story Points / Use Case PointsPlanned/Actual Cost and Velocity

Trend Variance. Likelihood of on-time delivery

Note: Bold indicates that there is Out-Of-The-Box report supported by Rational tools

From In Process (Team) To Executive ValueAppropriate Metrics for Each Management level

46

Page 47: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Measuring Time-to-Value (Schedule)

Iteration Burndown

Showing how much work is left to do in an iteration. It enables the team to adjust scope or resources to finish the iteration successfully.

Release Burndown

Shows the estimated functionality remaining to complete the current release.

47

Page 48: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Measuring Product Value

Enhancement Request Trend

Shows the trend of enhancement requests received, approved, and closed during the project lifecycle. A high number of enhancement requests can indicate that the system is not functioning as stakeholders expected.

Age of Enhancement Requests

Tracks the length of time stakeholder enhancement requests remain open. Unaddressed requests can impact the stakeholders' perception of value.

48

Page 49: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Measuring Product Cost

Cost per unit of work

Tracks the cost of delivering a single unit of work (such as a user story point or use case point) across iterations. Monitoring this metric in each iteration helps the team understand if they are burning budget at a sustainable rate.

49

Page 50: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Measuring Product Quality

Defect Trends

Shows defect arrival and closure rates, determines the remaining defect backlog, projects the future defect arrival/close rate up to and post-ship

Test Execution StatusMonitors test completion and success

50

Page 51: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Use dashboards to provide that 1 view of project health

51

Page 52: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Test your development intelligenceCan your team…

Time-to-Value

–Produce the right capabilities according to the committed schedule?

Product Value

–Deliver a valuable product?

Product Cost

–Measure what we spending to deliver the system?

Product Quality

–Build a high quality system?

Predictability

–Manage the risk and uncertainty?

52

Page 53: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Imperative 5: Continuous process improvement

Don’t Do

Define a process and place it on a shelf Use a tool that can ‘enact’ your process definition and guide the team toward the desired result.

Ignore process altogether or treat it like an unnecessary burden.

Learn from what other teams have done and leverage their results across other teams when appropriate Ignore process altogether or treat it like anunnecessary burden.

Institute process police Let the tool govern behavior and refine it over time. Add peer reviews to encourage knowledge sharing and collaboration.

Step 1Adopt

Step 2Enact

Step 3Measure

Step 4Improve

53

Page 54: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Project : Project : RetailRetailProject : Project : RetailRetail

Project : Project : SavingsSavingsProject : Project : SavingsSavings

Adopt - Process SharingLeverage the Best practices from Rational and other teams

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

1 Import/export TemplatesProvides the ability to leverage best practices from Rational and other teams

2 Servers support multiple templatesAllowing administrators to support different processes.

Teams improve their process independently.

Process updates can be sharedAllows teams to control when they want to accept improvements.

3

Scrum TraditionalIterative

WebWeb BankingBankingWebWeb BankingBankingTeam : Core

Team : UI

Team : Benefits

54

Page 55: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Team Retrospectives help identify areas of improvement

Tracking Retrospectives help team members to collaborate on improvements.

–Ranking of process improvements help to focus on where the team feels the biggest pain.

–Metrics where available help support process improvements and show results.

55

Page 56: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Test your process improvement capabilitiesCan your team…

Leverage out-of-the-box process templates for traditional and agile workflows?

Change process “on the fly” as part of a continuous feedback loop?

Allow team leads to determine how strict or lax the “rules of the road” should be?

Modify process enforcement over the life of a project, to encourage early-stage experimentation and end-game stability?

56

Page 57: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Agenda

Current market situation

Proven results

1

44

Delivering the 5 ALM imperatives 3

IBM Rational Collaboration Lifecycle Management2

57

Page 58: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us58

Automated status reportingderived from evolving engineering artifacts

can improve productivity by5-10%

Source: IBM analysis based on services research.

Best practices in scope management can improve predictability

of project delivery by 20-30%

Being able to collaborate on work items, defects and build errors

can reduce late rework by 25-50%

COLLABORATE AUTOMATE REPORT

Business Results

Page 59: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us59

Gartner MarketScope for Application Life Cycle ManagementIBM Rational earns “Strong Positive” – the highest possible rating

IBM earns “Strong Positive”―the highest possible

rating

The MarketScope is copyrighted November 11, 2010 by Gartner, Inc. and is reused with permission. The MarketScope is an evaluation of a marketplace at and for a specific time period. It depicts Gartner's analysis of how certain vendors measure against criteria for that marketplace, as defined by Gartner. Gartner does not endorse any vendor, product or service depicted in the MarketScope, and does not advise technology users to select only those vendors with the highest rating. Gartner disclaims all warranties, express or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. The MarketScope graphic was published by Gartner, Inc. as part of a larger research note and should be evaluated in the context of the entire report. The Gartner report is available upon request from IBM.

Efficient coordination and automation of the delivery process requires new, collaborative approaches to the planning, measurement, execution, control and reporting of activities.

These new approaches are what differentiate current application life cycle management (ALM) tools, and what make ALM processes vital to leading-edge development activities.

ALM is what enables sustainable agile practices. ALM creates a management framework providing consistent, auditable records of the decisions and activities of agile teams.

Page 60: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

What analysts are saying... Liz Barnett, Ez-Insight

“With the Jazz project, Rational has developed breakthrough technology and is poised to set the standard for collaborative ALM... Given the current business climate of ‘deliver more with less much sooner,’ organizations have no choice but to rethink the ways that they deliver software solutions. The Jazz project will help teams achieve that goal.”

Paul Herzlich, Ovum“IBM has taken the opportunity to exploit the Jazz platform’s power inventively. Its ‘living’ test plan is a masterpiece of applying new technology to a familiar problem… What is being delivered will demonstrate convincingly that IBM is raising the standard for a test management product.”

Julie Craig, EMA“Rational’s differentiators are difficult for competitors to equal, and the new Jazz platform foundation may well turn out to be one of the best investments the Rational team has made.”

Simon Jacobson, AMR“Frankly I wish folks who sold quality management solutions took this approach. Most of the folks I speak to talk about the lifecycle, but they are selling you a mass transit system, but only really provide the train station.”

Dave West, Forrester “What collaborative application lifecycle management is going to provide us with as an industry is the idea that these people have to work together on a platform to support them…I think that’s really exciting.”

Bola Rotibi, Creative Intellect Consulting“Jazz’s intuitiveness and simplicity – for configuration, management, and implementation – is allowing IBM Rational to extend beyond its traditional enterprise audience and appeal to smaller and more agile teams and organizations… IBM Rational has embarked on a grand vision for the Jazz platform that is starting to pay off.”

60

Page 61: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Rational solution for Enterprise Modernization

Establish a modern development platform designed to extend your investments

Software Change & Configuration Management

Rational Team Concert

QualityManagement

Rational Quality Manager

Build & DeployManagement

RequirementsManagement

DevelopmentRational Developer

for System z Rational Software Architect*

Rational Team Concert Rational Automation Framework

for WebSphere*

Rational Requirements Composer

*Optional add-on solutions

61

Page 62: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Rational solution for Systems and Software Engineering

Open Services for Lifecycle Collaboration

On-target product and process management via integration on an open platform

QUALITY MANAGEMENTAchieve “quality by design” with an

integrated, automated testing processRational Quality Manager

DESIGN MANAGEMENTUse modeling to validate requirements, architecture

and design throughout the development processRational Rhapsody

REQUIREMENTS MANAGEMENTManage all system requirements

with full traceability across the lifecycleRational DOORS

COLLABORATION, PLANNING & CHANGE MANAGEMENTCollaborate across diverse engineering disciplines and development teams

Rational Team Concert

62

Page 63: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

jazz.netCreating a higher-fidelity connection to our customers

Suppose we did our development out on the Internet?

A transparent software delivery laboratory where you can...Get answers and insights

directly from engineeringCommunicate with the

development teamTrack the progress of

builds and milestonesGet the latest product

trials and betasJoin developers and

product managers in discussion groups

Submit defect and enhancement requests

63

Page 64: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Summary: Rational Collaborative Lifecycle ManagementTransforming software and systems delivery

CollaborateBridge the gap between technical and business communities through shared access to enterprise documents, workflows and collaboration solutions.

AutomateMake it easy for individuals and teams to "do the right thing" and "do things right" by automating team process and workflow.

ReportTrack and measure progress across multiple teams, tools and geographies by leveraging the real-time instrumentation of the software lifecycle.

Helping customers improve the value and performance of their investments in software as strategic business assets

64

Page 65: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Next steps: Resources

Collaborative Lifecycle Management on Jazz.net Learn about the latest releases and features, participate in the forums, watch recorded videos of the solution in action. (link)

Agility@Scale eKit Download the Forrester Agile Wave and get a wealth of resources for improving team flexibility and responsiveness. (link)

ALM Buyer’s Guide – Explore objective criteria you can use to evaluate ALM solutions. (link)

ALM Value Estimator – In just five minutes, determine how much money you can save your organization with Rational ALM solutions. (link)

ALM Everyware eKit Download the Gartner MarketScope on ALM and get a wealth of resources for improving team productivity. (link)

65

Page 66: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Coming in this series …..

A Single Source of Truth -- Aligning Business Priorities and IT Project Deliverables

When: Wednesday, June 22, 2011 at 2:00 p.m. EDT

Software Quality Delivered -- From Concept to Launch to RetirementWhen: Wednesday, June 29, 2011 at 2:00 p.m. EDT

Sign up now:http://www.strongback.us/w3/events/CALMWebinar.jsp

Page 67: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us67

© Copyright IBM Corporation 2011. 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, Rational, the Rational logo, Telelogic, the Telelogic 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.

Page 68: Collaborative Lifecycle Managmenent - an Introduction

BACKUP SLIDES

Page 69: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

ResultsMV was the first company in Brazil to become certified to use electronic health records, meeting the security standards issued by SBIS and CFM.

Business challenge:MV is a leading provider of healthcare systems in Brazil with three software development centers that needed to improve their development processes to rapidly respond and take advantage of market opportunities and regulations in the changing healthcare industry.

Solution:Collaborative Lifecycle Management solution and lifecycle offerings, with RUP methodology and agile practices. MV first adopted and updated their change and configuration management processes with Rational Team Concert and then added Requirements Composer for business process and rules modeling, requirements collaboration and elicitation, and Quality Manager for test planning, test creation, execution, and quality management.

Benefits:MV accomplished the following:- Greater integration of and collaboration among three development locations- Improved developer and tester productivity- Decreased the learning curve when employees switch from one location to another- Gained greater visibility into requirements- Achieved greater reuse of requirements.

Greater productivity, global collaboration, and lifecycle visibility Case Study: MV Sistemas Ltd

Solution components:

Requirements ManagementRational Requirements

Composer

Quality ManagementRational Quality ManagerRational Functional Tester

Rational Performance Tester

Software Change & Configuration Management

Rational Team ConcertRational Method Composer

Build & Deploy ManagementRational Team Concert

Architecture & Development

Rational Software ArchitectRational Software Modeler

Rational Application Developer for Websphere

69

Page 70: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Build Health

Build completion over time shows if the team is impacted by build

Other Metrics

–# of daily builds

70

Page 71: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us71

Team CentralShows what is happening on project:

• News & events• What’s being worked on• Changes

Configurable (RSS feeds) - New kinds of information easily added

Personalized, Persistent - Each team member can tailor to their needs

Customize your vantage point to keep what's important to you in focus

Page 72: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us72

Multi-level continuous integrationIndividually - with your team - with your project

Page 73: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Symbolic link support

Are you using ClearCase or another scm that supports symbolic links?Rational Team Concert supports symbolic links as first class objectsSymbolic link changes are tracked – just like directory or file name changes

ln -s ./v2.0.0.2/readme.txt readme.txt

Page 74: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Formal Reviews drive agreement and prevent re-work

Test Artifacts

Requirements

Work Items

Reviews & approvals insures artifacts are reviewed and/or approved by key team members and captures compliance requirements.

74

Page 75: Collaborative Lifecycle Managmenent - an Introduction

www.strongback.us

Distributed source controlDeliver and accept across repositories

Share, compare, manage the flow of changes between developers, teams, and projects across different repositories

Provides organizations with flexibility while governing source control across distributed locations

Improves collaboration with other lines of business, and outside suppliers, who need to share component code changes across repositories