© 2007 IBM Corporation Demo Shimon Nir, Rational Technical & Service Manager, IBM Southwest Europe.

© 2007 IBM Corporation

Demo

Shimon Nir, Rational Technical & Service Manager, IBM Southwest Europe

© 2007 IBM Corporation2

Process Awareness

Project Manager

Developer / Build Engineer

Tester

© 2007 IBM Corporation3

Work Items

Project Manager

Developer / Build Engineer

Tester

© 2007 IBM Corporation4

In Context collaboration

Project Manager

Developer / Build Engineer

Tester

© 2007 IBM Corporation5

Iteration Planning and Execution

Project Manager

Developer / Build Engineer

Tester

© 2007 IBM Corporation6

Team Build

Project Manager

Developer / Build Engineer

Tester

© 2007 IBM Corporation7

Web Client

Project Manager

Developer / Build Engineer

Tester

© 2007 IBM Corporation8

Highlights from recent milestones ClearCase Connector is now

included in the Rational Team Concert client. Included in this

release is dynamic help.

Importing changes from a CVS repository into Jazz is

now supported.

Source Control command line client is starting to take shape. basic commands for browsing,

check-in, deliver, and accept but won't be ready for self-hosting

use until sometime in M4.

Search for change-sets based on several search criteria:

changes to back port, team member changes,

suspended changes

The Resolve Wizard is there to assist you in resolving conflicts. The wizard is non-modal, so you

can continue to use the whole Jazz UI in parallel.

Based on the new fulltext service, a new search page has been added allowing searches across all information artifacts that are known to the service:Textual references like "work

item 321" and embedded item references created with drag-and-drop become represented as explicit references when a

work item is saved.

You can now move workitems between

projects. A wizard assists with mapping

You can now rename and delete pages that are

attached to iteration plans.

You can now customize your My Work view by adding Team Central sections. A simple

workflow helps you organizing your work; and a quick filter helps you find what you are looking for

The Team Artifacts and Team Organization views now

present helpful hyperlinks for getting started with a new

Eclipse workspace.

© 2007 IBM Corporation9

SCM Agile Best-Practices* supported

• Mainline

• Active Development Line

• Private Workspace

• Repository

• Private System Build

• Integration Build

• Third Party Codeline

• Task Level Commit

• Codeline Policy

• Smoke Test

• Unit Test

• Regression Test

• Private Versioning

• Release Line

• Release-Prep Codeline

• Task Branch

*Software Configuration Management, Patterns: Effective Teamwork, Practical IntegrationBy Steve Berczuk with Brad Appleton Published by Addison-Wesley (http://www.awprofessional.com)

© 2007 IBM Corporation10

Extended Agile features supported

• Team First

• Awareness

• Iteration Planning

• Daily Planning

• Custom Workflows

• Process Enactment

• Process Permissions

• Approvals

• Build Reproducibility

• Build Promotion

• Build Comparison

• Traceability

© 2007 IBM Corporation11

World Class SCM, Work Item, and Build features

• SCM– The usual SCM checklist: atomic commits, change-sets, renames are tracked, multi-streaming is

cheap (branching).

– Multi-stream development including change-set cherry picking, history sensitive merging, and visual

stream editing.

– Flexible conflict resolution for all conflict types, renames, evil twin, structural, and content auto-

merge. Allows agile teams to refactor without stopping all development.

• Work Items– Rich in-place editors with built-in traceability and linking.

– Configurable work item types, states, workflows, and approvals.

– Iteration and personal planning with free-form and structured plan editors.

• Build– Brings build alerts, progress monitoring, and control to the team in a rich UI.

– Provides valuable linkage between builds, work items, and change-sets.

– Designed to work with the team's existing build tools.

© 2007 IBM Corporation12

SCM Integration Techniques

• Import– One-time import of data with best-effort mapping between models

• Connector– Designed for developers who want to use the fully integrated Jazz SCM, but need to connect into a “mother

ship” SCM system.

– SCM artifacts are replicated/synchronized between the Jazz SCM and the “mother ship” SCM

– Useful for pilot projects/staging migration to RTC – not all teams need to move at the same time. Allows teams to begin using RTC in the context of requirement to maintain master source code in a different SCM system.

– The team that is using RTC in this scenario is gets the full benefit of the tight Jazz SCM integration.

• Coexistence– Designed for developers who can’t or don’t want to switch SCM’s: You continue using your favorite SCM client

and server (with all its features and problems)

– RTC CDE installs “beside” SCM client

– Limited integrations depending on particular SCM client e.g. linking, client-side process integration. Inferior to native Jazz SCM integration due to implementation limitations and the fact that server side is not integrated (example: Subversion and other SCMs don't support process enactment for SCM operations. If you want that, you have to get your SCM from us)

– Jazz SCM can be optionally available to try out for possible upsell (packaging decision)

© 2007 IBM Corporation13

World Class SCM, Work Item, and Build features

• SCM– The usual SCM checklist: atomic commits, change-sets, renames are tracked, multi-streaming is

cheap (branching).

– Multi-stream development including change-set cherry picking, history sensitive merging, and visual

stream editing.

– Flexible conflict resolution for all conflict types, renames, evil twin, structural, and content auto-

merge. Allows agile teams to refactor without stopping all development.

• Work Items– Rich in-place editors with built-in traceability and linking.

– Configurable work item types, states, workflows, and approvals.

– Iteration and personal planning with free-form and structured plan editors.

• Build– Brings build alerts, progress monitoring, and control to the team in a rich UI.

– Provides valuable linkage between builds, work items, and change-sets.

– Designed to work with the team's existing build tools.

© 2007 IBM Corporation14

SCM Integration Techniques

• Import– One-time import of data with best-effort mapping between models

• Connector– Designed for developers who want to use the fully integrated Jazz SCM, but need to connect into a

“mother ship” SCM system.

– SCM artifacts are replicated/synchronized between the Jazz SCM and the “mother ship” SCM

– Useful for pilot projects/staging migration to RTC – not all teams need to move at the same time. Allows teams to begin using RTC in the context of requirement to maintain master source code in a different SCM system.

– The team that is using RTC in this scenario is gets the full benefit of the tight Jazz SCM integration.

• Coexistence– Designed for developers who can’t or don’t want to switch SCM’s: You continue using your favorite

SCM client and server (with all its features and problems)

– RTC CDE installs “beside” SCM client

– Limited integrations depending on particular SCM client e.g. linking, client-side process integration. Inferior to native Jazz SCM integration due to implementation limitations and the fact that server side is not integrated (example: Subversion and other SCMs don't support process enactment for SCM operations. If you want that, you have to get your SCM from us)

– Jazz SCM can be optionally available to try out for possible upsell (packaging decision)