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

2. © 2007 IBM Corporation 2 Process Awareness Project Manager Developer / Build Engineer Tester

3. © 2007 IBM Corporation 3 Work Items Project Manager Developer / Build Engineer Tester

4. © 2007 IBM Corporation 4 In Context collaboration Project Manager Developer / Build Engineer Tester

5. © 2007 IBM Corporation 5 Iteration Planning and Execution Project Manager Developer / Build Engineer Tester

6. © 2007 IBM Corporation 6 Team Build Project Manager Developer / Build Engineer Tester

7. © 2007 IBM Corporation 7 Web Client Project Manager Developer / Build Engineer Tester

8. © 2007 IBM Corporation 8 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.

9. © 2007 IBM Corporation 9 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 Integration By Steve Berczuk with Brad Appleton Published by Addison-Wesley (http://www.awprofessional.com)

10. © 2007 IBM Corporation 10 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

11. © 2007 IBM Corporation 11 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.

12. © 2007 IBM Corporation 12 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 cant or dont want to switch SCMs: 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)

13. © 2007 IBM Corporation 13 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.

14. © 2007 IBM Corporation 14 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 cant or dont want to switch SCMs: 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)