1. Introducing IBM Rational Team Concert
Umang Shah
Senior IT Specialist

2. Collaborate in Context Right-size Governance
Envisioning a technology… That can transform software delivery
An open technology initiative to transform how people work together to deliver greater value and performance from their software investments
Robust, extensible and scaleable
Globally distributed, fluid and dynamic
Community-based and open at Jazz.net
Collaborate in Context
Right-size Governance
Day One Productivity
Enable team transparency of “who, what, when, why”
Build team cohesion and presence
Automate hand-offs so nothing falls through the cracks
Automate team workflow improving productivity
Automate data collection eliminating administrative overhead
Real time reporting and alerts reduces project risk
Dynamic provisioning of projects and teams
Real-time iteration planning and workload balancing
Unify teams with tools choice
Notes for Deon’s Business Benefits:
Base development middleware platform can be administrated and managed by the project team
One of the key issues with CC/CQ is that It requires IT/ADMIN to instantiate projects. There is little separation for IT administration of the platform and the workflows.
With Jazz the server admin is like and other IT application and the project team can more or less service the project themselves. So Deon, once he’s setup the tools, can have the project teams self manage vs. Deon having to do it for each and every project.
Flexible options for owning or renting:
With Jazz, agile teams can own the platform, manage the platform, etc or choose to rent a project space (aka collabnet).
Real-time integration of people, process and projects across the lifecycle 2

3. The Jazz project People working together to deliver great software
A major investment by IBM to create a scalable, extensible team collaboration foundation.
IBM’s vision of the future of software delivery–globally distributed, fluid and dynamic.
An evolution of the Rational portfolio, which will evolve to support Jazz technology over time.
A community at Jazz.net – where you can see Jazz- based products being built.
Jazz is a project and technology for transforming how people work together to deliver greater value and performance from their software investments.
The Jazz platform
Platform
Collaborative ALM
There is a repository
Technical architecture…

4. Existing IBM Offerings Business Partner Offeringsc
An evolution of value in collaborative ALM bringing forward existing investments and delivering new innovative capabilities
Existing IBM Offerings
New IBM Offerings
Business Partner Offerings
Open Lifecycle Service Integrations
JAZZ TEAM SERVER
Best Practice Processes
Search and Query
In context collaboration
Team awareness
Events notification
Security
Dashboards
offering
offering
offering
offering
offering
offering
offering
Eclipse
Web 2.0
Visual Studio (4Q)
Client Integrations
Existing IBM offerings
Business Partner offerings
Open source offerings
Server Integrations
Powered by

5. Introducing the first wave of new Jazz offerings
Business Expert Collaboration
Elicit, capture, elaborate, discuss and review requirements
Requirements Composer
Team Concert
Innovation Through Collaboration
Unify by “thinking & working” in unison with real-time project heath
Collaborative Business-driven Quality
Quality Manager
Coordinate quality assurance plans, processes and resources
Rational Requirements Composer
offering
offering
offering
Rational Quality Manager
Rational Team Concert
Business Partner Jazz Offerings
Best Practice Processes
Search and Query
Security
Dashboards
Team awareness
Events notification
collaboration
ClearQuest
ClearCase
Build Forge
Asset Manager
Requisite
Pro
JAZZ TEAM SERVER
Open Lifecycle Service Integrations
Powered by 5

6. An evolution for new and existing customers
The Evolution of the IBM Rational Software Delivery Platform
Existing Offerings
New Offerings
Rational Requirements Composer
Rational RequisitePro
Rational RequisitePro
Rational Team Concert
Future Products
Rational Quality Manager
Rational ClearQuest
Rational ClearQuest
Built on the Jazz Technology Platform
Rational Build Forge
Rational Build Forge
Evolution to Jazz Technology Platform
Rational ClearCase
Rational ClearQuest
Rational Build Forge
Rational Team Concert
Rational Quality Manager
Business Partners & Others (Future)
This chart does not belong here – we need to illustrate how we are changing the thinking around collaborative ALM
Globally collaborative alm
Move 15 to the end
Get rid of this chart…
We need an architectural diagram
Examples and scenarios based on architectural diagram
And a scenario that points to the principle being implemented in the product, that makes those products different…
Think differently.
Rational ClearCase
Best Practice Processes
Rational Requirements Composer
Rational ClearCase
Common Jazz Services
Other Rational & Non-Rational Offerings
- - -
JAZZ TEAM SERVER
FUTURE IBM RATIONAL SOFTWARE DELIVERY PLATFORM 6 6

7. The evolution of value:
2008
2009
On-going
Rational Quality Manager
Enterprise Reporting
Rational Team Concert
Project Management
Others…
Rational Requirements Composer
Business Partner & IBM Offerings
Best Practice Processes
Search and Query
In Context Collaboration
Team Awareness
Dashboards
Events Notification
Security
JAZZ TEAM SERVER
Eclipse
Web 2.0
Visual Studio (4Q)
Others to come…
Client Integrations
Open Lifecycle Service Integrations
Server Integrations
Rational ClearCase 7.1
Rational ClearQuest 7.1
Rational Build Forge 7.1
Rational Asset Manager 7.1
Subversion

8. Today's focus: Rational Team Concert
The first offering built on Jazz technology
Rational Team Concert
Best Practice Processes
In Context Collaboration
Team Awareness
Search and Query
Dashboards
Events Notification
Security
JAZZ TEAM SERVER
Open Lifecycle Service Integrations
Server Integrations
Client Integrations

9. Rational Team Concert: High-level Overview
Iteration Planning
Integrated iteration planning and execution
Task estimation linked to key milestones
Out of the box agile process templates
Project Transparency
Customizable web based dashboards
Real time metrics and reports
Project milestone tracking and status
SCM
Work Items
Build
Integrated stream management with flow relationships
Component level baselines
Server-based sandboxes
Identifies component in streams and available baselines
ClearCase connector
Defects, enhancements and conversations
Query results view and share queries with team or member
Support for approvals and discussions
ClearQuest connector
Query editor interface
Work item and change set traceability
Local or remote build servers
Supports ant and command line tools
Integration with build forge
Build definitions for team and private builds
Jazz Team Server
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
Team advisor for defining / refining “rules” and enabling continuous improvement
Process enactment and enforcement
In-context collaboration shows team members and status of their work

10. Delivering customer value with Rational Team Concert
The evolution of software delivery
Fewer meetings and status reports
Reduction in late scrap and rework
Reduced attrition of skills and greater flexibility to leverage top technical and business talent
Collaborate in context
Right-size governance
Less overhead to stay compliant with standards
Earlier detection and accelerated resolution of defects
Improved predictability of project outcomes
THREE MAIN POINTS
…How is 2008 different than last year?
First –sheer complexity and the distribution of business models is putting new pressure on development teams & projects – impacts to architecture
Second - we’re seeing the impact of shifts in globalization combined with new, technology enabled ways of working – a la Web 2.0 is changing the expectations between employees and managers, partners and customers, communities and companies…
TRANSITION --- These shifts are driving different conversations …
Day one productivity
Project initiation in days rather than weeks
Reduction in time to first demonstrable release
Improved cycle times through automated and reusable patterns, services and architectures
Supporting the software economics of an increasingly global, dynamic and web-based technology environment

11. IBM Rational Team Concert
Software innovation through collaboration
Real time, in-context team collaboration
Make software development more automated, transparent and predictive
"Think and work in unison"
Integrated source control, work item and build management
Assess real-time project health
Capture data automatically and unobtrusively
Automate best practices
Dynamic processes accelerate team workflow
Out-of-the-box or custom processes
Unify software teams
Integrate a broad array of tools and clients
Extend the value of ClearQuest and ClearCase
Visual Studio Client (1Q09)
Support for System z and System i servers (Q4)
IBM Rational Team Concert
transparent integrated presence wikis OPEN real-time reporting chat automated hand-offs Web 2.0 custom dashboards automated data gathering EXTENSIBILITY Eclipse plug-ins services architecture FREEDOM TO CREATE
Open and extensible on
Collaborate in context
Right-size governance
Day one productivity

12. Unify distributed teams in mid-sized or enterprise settings
New York City
North Carolina
A complete, solution for departmental and medium-sized distributed teams
Testing Ireland
Project Management Europe
Development China
Config & Build China
Team Concert
Development Australia
Rational Enterprise-proven ALM Infrastructure
Rational ClearQuest
Define
Build
Test
Deploy
Bi-directional auto-synchronization
Rational ReqPro
Rational Build Forge
Rational ClearCase
EclipseTM, Linux®, Microsoft® Windows®, UNIX®, IBM z/OS®, IBM i5/OS
Benefits of ClearCase/ClearQuest Connectors
Optional bridge to Subversion
Enables teams to reuse enterprise assets, process and investment in ClearCase/ClearQuest
Take advantage of new collaborative ALM in an evolutionary way with lower business risk
Manage status/priorities in ClearQuest and develop with the right ALM solution for your project.
Use the “right-sized” governance solution for different projects needs.
Developers can deliver work from “satellite” teams directly into enterprise ClearCase projects

13. Improve business agility and project success rates
IBM Rational Team Concert
transparent integrated presence wikis OPEN real-time reporting chat automated hand-offs Web 2.0 custom dashboards automated data gathering EXTENSIBILITY Eclipse plug-ins services architecture FREEDOM TO CREATE
Facilitates the principles of high-performance teams
Supports enactment of any process, including Agile
Working
Software
Individuals Interactions
Respond to Change
Customer
Collaborative
Continuous integration
Manage team assets
Change driven
Integrated / traceable
Starting ad-hoc teams
Team awareness
Process awareness
Ad-hoc sharing
Process flexibility
Iterative plan-execution
Multiple releases
JIT code reviews
Transparency
Objective commonality
Project health checks
Context driven

14. Scaleable configurations for differentiated usage scenarios
Standard
Express
Express-C
Mid-sized and Departmental
Project dashboard
Out-of-box processes
Commercial middleware
Corporate Teams
Customizable process
Real-time project health
Lower cost of LDAP
Scalability / extensibility
Rational Team Concert
Community and Academia
In-context collaboration
Rapid deployment
Open source servers
Maximum developers/contributors per server
10 total
50/unlimited
250/unlimited
Database and Application Server support
Tomcat, Derby
DB2/DB2E, SQLServer, Oracle, Tomcat, WebSphere
DB2/E, SQLServer, Oracle, Tomcat, Websphere
Source code, work item, build 
Agile planning
Subversion Integration
Server-level permissions
LDAP Authentication
Customizable Process
Dashboards
1 per project
unlimited project, team, and personal dashboards
Floating licenses available
Reports
Customizable Work Items/workflow
Role-based process permissions
ClearCase/ClearQuest Connectors
LDAP Import
Standard http proxy server support

15. Rational Team Concert: A Deeper Look
Iteration Planning
Integrated iteration planning and execution
Task estimation linked to key milestones
Out of the box agile process templates
Project Transparency
Customizable web based dashboards
Real time metrics and reports
Project milestone tracking and status
SCM
Work Items
Build
Integrated stream management with flow relationships
Component level baselines
Server-based sandboxes
Identifies component in streams and available baselines
ClearCase connector
Defects, enhancements and conversations
Query results view and share queries with team or member
Support for approvals and discussions
ClearQuest connector
Query editor interface
Work item and change set traceability
Local or remote build servers
Supports ant and command line tools
Integration with build forge
Build definitions for team and private builds
Jazz Team Server
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
Team advisor for defining / refining “rules” and enabling continuous improvement
Process enactment and enforcement
In-context collaboration shows team members and status of their work

16. Work Items are central to Rational Team Concert
An IBM Proof of Technology
Work Items are central to Rational Team Concert
Build includes change-sets
Planning
Source Control
Build
Report
Plans define & organize work items
Change-sets implement work items
Work items
describe the builds
Reports show work item activity
The main goal of this slide is to explain that the work items are a central part in Jazz. As the slide says (animated one by one):
- Planning component helps the user in defining and organizing WI
- SCM changes implement/resolve WIs
- Because include changes then we can say that WIs describe builds
- Report component draws the WIs activity
The dashed arrow means that the relationship is derived from the 2 others!...
Work Items
This module
looks at
Planning
using
Work items
Module 2 - Planning Your Work 16
Module 2 - Planning Your Work 16

17. Work Item details An IBM Proof of Technology
Module 2 - Planning Your Work 17
Module 2 - Planning Your Work 17

18. The Iteration Plan Assigned to a given milestone For a given team
An IBM Proof of Technology
The Iteration Plan
A collection of work items…
Assigned to a given milestone
For a given team
Plans are live
Changing work items changes the plan
Changing the plan directly changes the work items
Create new work items from the plan
Plan structure is dynamic
Easily be grouped by owner, category, duration, priority, etc.
Plans are visible
Available to everybody on the team
Observable by interested outsiders
Module 2 - Planning Your Work 18
Module 2 - Planning Your Work 18

19. Reports – Displaying the project status
An IBM Proof of Technology
Reports – Displaying the project status
Rational Team Concert uses the BIRT* reporting engine
A huge variety of report formats are designed and available to display an actual overview of your projects:
Reports for the health of your builds
Reports for viewing the team load and the distribution of work items
Reports for your code
Etc.
Reports can be arranged in the Web UI to Dashboards
Reports can be exported to: .pdf, .xls, .doc, .ppt formats
*BIRT is an open source Eclipse-based reporting system that integrates with your Java/J2EE application to produce compelling reports.
Module 3 - Keep Track of All Our Work 19
Module 3 - Keep Track of All Our Work 19

20. Reports – Displaying the project status
An IBM Proof of Technology
Reports – Displaying the project status
Module 3 - Keep Track of All Our Work 20
Module 3 - Keep Track of All Our Work 20

21. Reports – Displaying the project status
An IBM Proof of Technology
Reports – Displaying the project status
Display your choice of reports and queries in your own dashboard, e.g. to control the flow of work items.
Module 3 - Keep Track of All Our Work 21
Module 3 - Keep Track of All Our Work 21

22. Reports – Displaying the project status
An IBM Proof of Technology
Reports – Displaying the project status
For a detailed Report open the Reports page and choose from a variety of available reports
Module 3 - Keep Track of All Our Work 22
Module 3 - Keep Track of All Our Work 22

23. Module 4 - Performing and Sharing Your Work
An IBM Proof of Technology
Basic Jazz SCM Anatomy
Stream
Repository Workspace
Local Workspace
Your change-set
Other change-sets
Streams are for sharing
Repository workspaces are your personal space
Eclipse workspaces are where you work
Change-sets flow back and forth
Subsequent modules will cover each of these
NOTE: We will be mapping the RTC terms to CC terms in the next module if the question comes up on this slide or any of the following slides.
Note that blue is server and green is client
Also note the icons
These conventions will be used throughout the SCM charts
There is a 5 click animation on this slide.
1st – shows the stream object and bullet
2nd – shows the repository workspace object and bullet
A repository workspaces is your personal space on the server but they are searchable by others and others can get change-sets from them.
3rd – shows the Eclipse workspace object and bullet
NOTE: multiple repository workspaces may be loaded into a single eclipse workspace
4th – shows the change-set bullet and runs the change-set animation (if you hit page up after it runs and then click again, it will rerun)
5th – shows the final bullet and the icon in the upper right. This icon will be used on other slides to remind us of this relationship.
Module 4 - Performing and Sharing Your Work 23
Module 4 - Performing and Sharing Your Work 23

24. Module 4 - Performing and Sharing Your Work
An IBM Proof of Technology
Components
Repository Workspace
Component
Local Workspace
Repository Workspaces
Partitioned into components
Jazz understands the structure of your components
Jazz directly supports component based development
Jazz SCM goes beyond most other system’s simple file and folder awareness
Jazz understands more of your components’ structure as we will see next when we look at what a component looks like…
Module 4 - Performing and Sharing Your Work 24
Module 4 - Performing and Sharing Your Work 24

25. Module 4 - Performing and Sharing Your Work
An IBM Proof of Technology
Components (cont)
Repository Workspace
Component
Eclipse Project
Folder
File
Local Workspace
Eclipse Project
Folder
File
Folder
This example shows Eclipse projects since that is what we will use in the exercises. However, Jazz SCM is not Eclipse project specific. Jazz SCM content can map to other types of local workspaces such as a Visual Studio workspace or a build area on a build machine.
In this example:
There can be any number of components in a repository workspace and any number of Eclipse projects in a component.
Note how an Eclipse project can be contained within a folder structure in a component.
For each component and its Eclipse projects the structure continues as briefly shown here.
Module 4 - Performing and Sharing Your Work 25
Module 4 - Performing and Sharing Your Work 25

26. Components (cont) Local Workspace Change set Change set
Repository Workspace
Local Workspace
Components
Repository Workspace
Change set
Components
Change set
Components Track Changes
Configuration of resources builds from the change set flow
Each change set builds on what came before
Component’s Change History
A time-ordered sequence of change sets
Describes how the component’s content was built from nothing
Note that each user has their own repository workspace(s) and that we are still not sharing these changes with the team yet. That is coming soon when we discuss streams.
There is a four click animation on this slide
1st shows a change set flowing in and the first sub-bullet
2nd shows a change set flowing in and the second sub-bullet
3rd shows a change set flowing in and the second main bullet and its first sub-bullet
4th shows a change set flowing in and the final sub-bullet 26

27. Change set Details
Composed from a collection of changes to one or more files and folders
Change set orientation is another example of Jazz understanding your source and its relationships
A change set that affects multiple resources is committed as a single atomic unit
Indicates the reason for the changes
Via a comment, and/or
By referencing the relevant work item
Can be shared with another team member
Via a stream, or
From your repository workspace via a work item
Note that this change set orientation means cross resource dependencies can be managed as a single atomic change set
There is a two click animation on this slide
1st click shows the second primary bullet and its sub-bullets
2nd click shows the third primary bullet and its sub-bullets 27

28. Change Sets Review change sets that make up the build
An IBM Proof of TechnologyAn IBM Proof of Technology
Change Sets
Review change sets that make up the build
Change Explorer lists files that were modified for a given change set
Module 7 - Exploring Changes and Traceability 28
Module 7 - Exploring Changes and TraceabilityGo to 'View > Header and Footer' to change this to match the event title 28

29. Streams Stream A place to share source with your team Local Workspace
Repository Workspace
Local Workspace
Components
Repository Workspace
Change set
Change set
Change set
Change set
Components
Change set
Change set
Change set
Change set
Stream
Note that streams and repository workspaces are essentially the same except that streams are for sharing and repository workspaces are private
This animation (3 clicks) starts with where we ended on the “Components” chart. The changes have been checked-in to each developer’s repository workspace. Now we will see sharing via a stream.
1st click – delivery
2nd click – accept
3rd click – automatic (if affected component loaded) propagation to local workspace
The following charts will introduce the actions for making this all happen.
Components
Change set
Stream
A place to share source with your team 29

30. Typical Journey For A Change set
3. Complete (usually combined with deliver)
4. Deliver
Stream
Component
Repository Workspace
Component
2b.Change set
2a. Check-in
A quick animated change flow overview with the screen shots to show the annotations.
Note that Check-in can be made automatic after a save via the preferences.
Local Workspace
1. Change 30

31. Change-set Delivery is Process Enabled
An IBM Proof of Technology
Change-set Delivery is Process Enabled
The deliver operation is process-enabled, allowing the team’s process to check and enforce delivery rules automatically
A failure is shown with a quick fix available.
After fixing, the deliver works. Single click animate here.
During the lab, you will experience this yourself.
There are other rules that can be enforced at delivery and other times. We will not have time to explore all the possibilities but this one is a good example.
Module 4 - Performing and Sharing Your Work 31
Module 4 - Performing and Sharing Your Work 31

32. Getting Teammates’ Delivered Work
An incoming change-set is
In the change history of the stream, but
Not in the change history of your repository workspace
Accept adds the change-set to your repository workspace’s change history
Stream
Component
Repository Workspace
Component
Accept
After you deliver changes, others will see them as incoming change sets and will want to get them.
Single click animation now the shows the last bullet, the accept call-out and lines and changes the screen shot.
Note that iff you have the Component loaded into your Local Workspace then the change is also propagated to your Local Workspace (the dotted arrow).
Local Workspace 32

33. Rational Team Concert Build
An IBM Proof of Technology
Rational Team Concert Build
Is an integral part of the project infrastructure
Consistent, repeatable process throughout the project
Brings awareness of build progress and results to developers
Easy sharing of information
Links build results to related Jazz artifacts
Integrated experience, traceability and tracking “baked in“
Allow developers to have a private build area
Build and test code before delivering to the main branch
Accomodates existing build technologies (Ant, CruiseControl , Build Forge, Maven, …)
Leverages technology that fits your project best
Module 6 - User's View of Build 33
Module 6 - User's View of Build 33

34. Build is very visible to the user
An IBM Proof of Technology
Build is very visible to the user
My builds
Recent builds
Published build
Animated slide!
Alerts
History 34
Module 6 - User's View of Build
Module 6 - User's View of Build 34

35. Personal builds run from your repository workspace.
An IBM Proof of Technology
Personal builds
Builds normally run from a dedicated repository workspace.
Personal Builds
run from your repository workspace.
allow you to build your changes before delivering them to the stream.
provide you with some assurance that your changes will not disrupt the team builds when you deliver them.
Module 6 - User's View of Build 35
Module 6 - User's View of Build 35

36. An IBM Proof of Technology
Builds and Snapshots
A build can request a snapshot
If there are any changes in a component since the last build
A new baseline is created with the same name as the snapshot name
Convenient for reproducing build problems
A build does not have to request a snapshot but if you want to be able to easily recreate the build, you will want one.
Module 6 - User's View of Build 36
Module 6 - User's View of Build 36

37. Builds Identify work items and change sets that went into the build
An IBM Proof of TechnologyAn IBM Proof of Technology
Builds
Identify work items and change sets that went into the build
Module 7 - Exploring Changes and Traceability 37
Module 7 - Exploring Changes and TraceabilityGo to 'View > Header and Footer' to change this to match the event title 37

38. Visualize Change History
An IBM Proof of TechnologyAn IBM Proof of Technology
Visualize Change History
Use annotation to view specific changes
Module 7 - Exploring Changes and Traceability 38
Module 7 - Exploring Changes and TraceabilityGo to 'View > Header and Footer' to change this to match the event title 38

39. Interoperation Architecture Overview
An IBM Proof of Technology
Interoperation Architecture Overview
Versions selected by the ClearCase interoperation configuration view are committed to the ClearCase Synchronized Stream in Team Concert by the synchronization process.
If any item in the ClearCase Synchronized Stream have been modified concurrently by Jazz source control users and ClearCase, they appear in incoming change sets for the merge workspace.
The merge workspace owner resolves the conflicts, and then delivers the merged results to the ClearCase Synchronized Stream.
The change sets delivered to the ClearCase Synchronized stream are propagated back to ClearCase the next time the synchronization process runs.
Module 10 - Integrating with Other SCM Systems 39
Module 10 - Integrating with Other SCM Systems 39

40. Synchronize (export) Team Concert code changes to ClearCase
An IBM Proof of Technology
Synchronize (export) Team Concert code changes to ClearCase
Module 10 - Integrating with Other SCM Systems 40
Module 10 - Integrating with Other SCM Systems 40

41. Synchronize (import) ClearCase code changes to Team Concert
An IBM Proof of Technology
Synchronize (import) ClearCase code changes to Team Concert
Module 10 - Integrating with Other SCM Systems 41
Module 10 - Integrating with Other SCM Systems 41

42. Multi-Stream Development
An IBM Proof of Technology
Multi-Stream Development
User Interface Stream
Integration Stream
Core Library Stream
Core
Core
Core
Core UI
Core Tests
Core Tests
UI Tests
Documentation UI
UI Tests
Note UI adopter isolation during animation
Mention bug (nightly and weekly integration streams) at the end
There is a 13 click animation on this chart
Jerry tests the latest Core Library changes and baselines the changes
Jerry delivers the baseline to the Core Library stream
Jerry changes his flow target to the Integration stream
Jerry delivers the baseline to the Integration stream
Jerry changes his flow target back to the Core Library stream
April changes her flow target to the Integration stream
April accepts the Core baseline
April changes her flow target back to the User Interface stream
April makes changes to UI component to adopt the Core changes, tests and baselines the UI component.
April delivers the Core and UI component baselines to the User Interface stream.
April changes her flow target to the Integration stream.
April delivers the UI component baseline to the Integration stream.
April changes her flow target to the User Interface stream.
Note that the test components could flow in a similar manner if they changed as part of this.
Also note that all the tests would be run as part of the team and integration builds.
April on User Interface
Core
Core
Jerry on Core Library UI UI
Core
Core
UI Tests
Core Tests
Module 11 - Project Growth and Multi-Stream Development 42
Module 11 - Project Growth and Multi-Stream Development 42

43. Extend team collaboration to a broad range of software professionals
Compliance Officer
Manage business and architectural policies
Track project actuals vs pan
Analyst
Access to source code quality metrics
QA Manager
Manage software licensing risk.
Legal Counsel
Access project and team health information
Executive
Manage documents and workflows (MS SharePoint or Lotus Quckr)
Rational Team Concert
Software Architect
Functional Tester
Application Developer
Business Developer
Lotus MashUps
etc..
IBM
Integrate with Jira CM
Project Coordinator
Web 2.0

44. Additional resources Find out more about Rational Team Concert
Explore Rational Team Concert tutorials, demos and other developer learning resources
Learn more about the Jazz technology and the future IBM Rational product roadmap
Join the Jazz community and participate in the open commercial development project

45. Thank you! © 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.