Jazz Project and Rational Team Concert Overview

1. IBM Rational Software Jazz Project and Rational Team Concert Overview Giora Katzir, Rational Software, IBM Software Group, Israel CTO

2. Disclaimer and Non-Disclosure • Though this represents our current direction, these plans are subject to change • Nothing in this presentation is intended to create any representations or warranties • IBM Rational warranties are contained in the applicable license agreements

3. Agenda • Setting the Stage • Jazz Project Overview • Rational Team Concert Overview • Demo • The Jazz Project Approach • Extending Jazz

4. Agenda • Setting the Stage • Jazz Project Overview • Rational Team Concert Overview • Demo • The Jazz Project Approach • Extending Jazz

5. Forces in Motion • Evolving business requirements • Agile programming • Web 2.0 and Social Networking • Application Lifecycle Management (ALM) • The Eclipse phenomenon and our experiences

6. The Shift: Intense focus on business outcomes • Align technology and business goals to enable flexibility & innovation • Manage value and mitigate risks via improved project management • Increase customer intimacy & knowledge to grow relationships & markets • Control costs & gain operational efficiency while meeting compliance mandates Consume & integrate value in organizationally diverse environments

7. What’s different today? • 2007 and beyond: Shifts in software delivery • What we’re seeing • Increasingly diverse and cross organizational global project teams • SOA, Web-centric & Web 2.0 enabling new business models • Popularity of Agile development and social networking models • Interest in replicating the proven models of open, community- governed software delivery models • What we’re hearing… “2/3 of our projects span multiple business units”“People knew it was a train wreck; no one could see what to do.” “We’ve done two acquisitions in six months and we can’t lose customers” “We run on the Web – and we run fast — new code makes us really nervous” “We have to go where the best talent is, but we have IP and compliance realities”

8. Changing Business and IT Environment “Managing dependencies between high-priority change requests and ongoing application development efforts “sometimes seems like it isn’t humanly possible.” (US healthcare company) • Demand for visibility into IT • Mandate to drive down cost of ongoing operations • Changes in IT governance • Geographic and organizational distribution • More complicated architectures and processes “We do progress reporting the same way we've been doing it for 40 years. It's all manual: weekly status meetings, progress reports, demonstrations. We’d love to get test results from nightly builds posted somewhere instead of having to run people down to ask them whether things are working yet.” (Bank) “We had a consulting company define a methodology for us. We still have it on a shelf somewhere. A process needs to live in the tools we use if it's ever going to be followed.” (Transportation company) “Automating our build-deploy-test processes would probably save each of our developers about an hour a day.” (Financial services firm)

9. Governance Software “Supply Chains” Customers are maturing their approach to software delivery Managing value & risk with continuous portfolio and lifecycle management aligned with business imperatives Cross organizational process & project management with an emphasis on collaboration and asset utilization Portfoliomanagement Real time Middleware platform including process activation Future Team productivity via change, quality &release management Lifecycle tools integrated with best practices process guidance Process management Late 90’s - Today Integrated Develop. Env (IDE) including Source Code Mgmt Systems F O C U S Design& construction Projectmanagement Compilers and Editors and simple test tools 1980’s – 1990’s Resourceavailability Pre-1980’s S C O P E Individual Team Organization Business

10. www.agilemanifesto.orgAgile programming

11. You cannot be Agile if you are not in shape • Scrum is CMM Level 3 compliant • Implies that it builds on a Level 2 organization! • If you do not know what proble, you are solving, then any solution is as good as any other • If you do not have the preconditions for going Agile, you will fail • Half of all SCRUM projects fail • Preconditions to Agile: • Open communication • Basic competencies • Lean • Stakeholder Engagement • Freedom • Balanced Maturity Coplien – Bootstrapping Agile

12. Social Networking – Power of communities • Wikipedia on Web 2.0: • a perceived second generation of web-based communities and hosted services … that facilitate collaboration and sharing between users • Key principles of Web 2.0: • the web as a platform • data as the driving force • network effects created by an architecture of participation • innovation in assembly of systems and sites composed by pulling together features from distributed, independent developers (a kind of "open source" development) • lightweight business models enabled by content and service syndication • the end of the software adoption cycle ("the perpetual beta") • software above the level of a single device, leveraging the power of The Long Tail. • ease of picking-up by early adopters

13. e-mail, phone etc. Social computing Social computing turns individual preferences into niche markets that can be identified and reached syndicate you tag blog review people you know rate society economy people you don’t buy sell comment the world

14. Pillars of ALM* • Traceability of relationships between artifacts • Automation of high-level processes • Providing visibility into the progress of development efforts * Forrester Research report, “The Changing Face of Application Life-cycle Management”

15. The make up of ALM support* • Greater insight for problem resolution and better control and management • Collaboration and communication across the board • Better quality control, risk management and impact analysis • Connected requirements lifecycle • Instrumentation and more relevant metrics • Support for geographically distributed IT teams (internal and external to the organization) • Democratization of roles and role support • Process and workflow • Change and agility-driven environment • Seamless integration between the different phases of the application lifecycle and interoperability with solutions from other providers. *Ovum report “Application Lifecycle Management Market Analysis”

16. From Eclipse to Jazz • Pre-Eclipse Way • Culture: shipping matters, delivering quality on time • Eclipse • 6 years shipping on time • Reflecting on process • Describing the process  the Eclipse Way • Jazz • Tooling the process

17. fitness The Eclipse Way --- Iterative/incremental sign-off sign-off sign-off release 3.2 3.1 warm-up M1 M2 … endgame retrospective decompression initial release plan plan stabilize plan stabilize plan stabilize test fix test develop develop develop fix - spit & polish 6 weeks 6 weeks 6 weeks

18. What is behind the Eclipse Way • Practices underpinned with values • ship quality on time • Used, developed and improved over time • Worked for us (and others) • Practices are from all kinds of sources • XP, Scrum, Crystal Clear, RUP, … • Patterns - Organizational Patterns of Agile Software Development – Coplien • It is not low ceremony • Approvals, verifications, reviews • It is agile: iterative, time-boxed, incremental, feature-based, collaborative, transparent, customizable

19. What is behind the Eclipse Way

20. 5 Years Shipment in Time !

21. But… there are Pain Points… • Joining a team • Get my environment configured to be productive • What is happening in my team • Collecting progress status • Following the team’s process • Ad hoc collaboration/sharing of changes • Starting an ad hoc team • Is the fix in the build? • What will be in the next build? • Tracking a broken build • Avoid breaking a build/personal build • Why is this change in the build? • Reconstructing a context for a bug/build failure • Creating, tracking iteration plans • Interrupting development due to a high priority bug fix • Working on multiple releases concurrently • Tracking the code review of a fix • Referencing team artifacts in discussions • How healthy is a component? • Collecting project data/metrics? Teamawareness Buildawareness Boring and painful Projectawareness

22. What if your tools know… • … about your teams • … about your artifacts • … who is responsible for what • … rules under which circumstances code can be delivered • Code quality, traceability, test runs, intellectual property • … how to bootstrap a project • … howto help new team members get started • … your favorite work item types and their state transitions • … when the build runs and what to do if it breaks

23. Jazz: Technology Innovation for the Rational Software Delivery Platform ALM Eclipse Experience Web 2.0 Agile Practices

24. Agenda • Setting the Stage • Jazz Project Overview • Rational Team Concert Overview • Demo • The Jazz Project Approach • Extending Jazz

25. What is Jazz? Rational Products Innovation A commercial project led by the IBM team that brought you the Eclipse Platform. Rational Team Concert will be the first product built on Jazz and feature tooling the agile practices. A major investment by IBM to create a scalable, extensible team collaboration platform for seamlessly integrating tasks across the software lifecycle Innovative Software Engineering Vision Community A vision for the value and experience that future Rational products can bring to software and systems delivery teams Jazz.net – Jazz project venue for open commercial development of Jazz platform and Jazz-based products and an extension of the world wide Eclipse ecosystem

26. How is the Thinking Behind Jazz Different? DesktopIntegration Lifecycle Integration Eclipse established a desktop client integration model for individuals, Jazz will establish a similar integration model across the lifecycle of software projects Function First Team First Jazz will challenge us to think first about how people work together and then about the tool function needed by individual practitioners for specific roles Manual Process Aware & Transparent Focuses on automating the unique dynamic of a team enhancing productivity by enabling real-time collaboration, visibility and transparency across the team, and process enactment

27. The value of the technology? Enables teams to collaborate in real time in the context of the work they are doing Provides visibility into accurate current project health information drawn directly from actual work across the team Automates traceability and auditability by managing artifactsand their inter-relationships across the lifecycle Enables custom process enactment via process automation & definable checkpoints Provides an extensible technology platform for building products & adapters ThePlatform An Open, Services Oriented Architecture Eclipse Client Jazz Client Extensions Eclipse Platform Web 2.0 or Web Services clients Lotus Sametime or open source Jabber Team Server Web UI Jazz Server Extensions Jazz Kernel DB2 or open source Derby Eclipse Equinox J2EE Web Services 27

28. Jazz Customer Value • Accelerate time to value: Steer projects iteratively and integrate/test continuously to cut downstream scrap and rework • Improve project predictability: Real time instrumentation of changing work products for lifecycle assessment of progress and quality • Extract organization value and knowledge: Balance existing reusable assets with evolving user needs and employ know-how and skills from anywhere in a collaborative development environment. • Right-size development governance: Dynamically adapt process agility and level of process rigor to be commensurate with the uncertainty in the estimate to complete. • Focus value to the business: Link work and artifacts across the lifecycle to optimize economic outcomes • Improve effectiveness in a globally and organizationally distributed environment: through improved transparency, best practices capture and enactment, project dashboarding • Tap into community value: Extend Jazz-based offerings, e.g. Rational Team Concert, with broader value of the Eclipse community

29. Jazz Platform Architecture – Open Source middleware Jazz Web Client Jazz Eclipse Client Other Clients Jazz Client Extensions Eclipse Platform HTTP, Web Services, RSS, Atom Apache Derby Jazz Team Server Jazz Server Extensions Web UI Jabber Jazz Kernel Eclipse Equinox Apache Tomcat

30. Jazz Platform Architecture – IBM middleware Jazz Web Client Jazz Eclipse Client Other Clients Jazz Client Extensions Eclipse Platform HTTP, Web Services, RSS, Atom DB2 Jazz Team Server Jazz Server Extensions Web UI Lotus Sametime Jazz Kernel Eclipse Equinox WebSphere

31. Jazz Components Overview Kernel IterationPlanning Code Coverage Static Analysis Other Systems Project Health Source Control TeamBuild WorkItems Inter-op Inter-op Collaboration Repository Process 31

32. Jazz: Enabling innovation in the Rational Software Delivery Platform 32 • Jazz is about technology innovation and a forward looking vision for IBM Rational • It is a fundamental building block for collaborative software development and application lifecycle management • Jazz adds value to the Rational SDP • By enhancing existing products, E.g. Rational ClearCase and ClearQuest • By enabling new offerings, e.g. Rational Team Concert • By providing a new level of extensibility for customers and business partners

33. Agenda • Setting the Stage • Jazz Project Overview • Rational Team Concert Overview • Demo • The Jazz Project Approach • Extending Jazz

34. What is Rational Team Concert? A New Family of Products based on Jazz Technology • Optimized for Agile development teams in midsized & large businesses • Integrates the entire team around an integration server • Includes Enhanced Eclipse Development environment Primary Features • In-place collaboration between team members • Support and enforcement for development processes • Transparency of status and trends through automated data-gathering and reporting Motivation • Enable flexible, agile application lifecycle management • Low administrative footprint optimized for agile teams in SMB & large businesses • Add value for existing ClearCase and ClearQuest customers • Step one in the rollout of “lifecycle service integration” middleware in the Rational SW Delivery Platform

35. Agile team collaborationClient RAD / RSA integrated with TCS New Rational Client for Bus. Analysts (BAW) New Rational Clientfor Requirements Definition New Rational Client for Enterprise Program Mgmt. Third-party Clients Other IBM Clients (WBM, RDA) Team CollaborationServices AdaptiveProcess Enactment& Continuous Analysis Artifact relationships Powered by Rational Portfolio Manager Rational RequisitePro Portfolio Management Events(optional) Evolving the Rational Software Delivery PlatformAn open ecosystem based on IBM middleware LIFECYCLE SERVICE INTEGRATION MIDDLEWARE • Integrated Events / Status Function • Integrated Work Item Function • Integrated SCM Function Point Product Integrated Platform Rational Functional Tester/ Performance Tester Third-party products(i.e., Subversion connectors) Rational ClearCase/ ClearQuest RationalBuild Forge Rational Asset Manager Asset Governance and Collaboration ClearCaseSCM (optional) ClearQuestWork Items (optional) Built for development efficiency: Allows developers to innovate rather than duplicating efforts, figuring out who to hand off to, or tracking and reporting status

36. Target Scenarios we will Support with Rational Team Concert v1.0 Co-exist Connectors Import Integration with the SVN repository with the Collaborative development capabilities of RTC (Workitems, Build) Provide capability to import from tools into RTC v1.0 ClearQuest (includes CQ enabled UCM) Bugzilla repository Bi-directional Synchronization Rational Team Concert v1.0 Rational Team Concert v1.0 CVS or SVN repository Rational Team Concert v1.0 ClearCase (Base CC and UCM) Subversion repository 36

37. Team Concert Connectors Governance focused teams cannot hold agile teams accountable ClearCase/ClearQuest Dev Team Release Integration Agile Dev Team Add/edit Deliver Add/edit Deliver Rebase Rebase Integration Build Build Forge (optional) UCM / Base CC projects Other Repositories Rational ClearCase/ ClearQuest Network shares & Other systems 37

38. Jazz and Team Concert Timeline Jazz Platform 1.0 2010 Jazz Platform 1.0 Milestone drivers Jazz Platform 0.6 Availability Jazz Platform 0.6 Milestone drivers Team Concert 2.0 2009 Jazz Platform 0.6M1 Team Concert 1.0 Fix packs • Jazz Platform 0.5 Team Concert 1.0 • Jazz worldwide team • self hosts at jazz.net Continued beta and incubator drivers 2008 Team Concert Beta 2 Jazz.net Launch Team Concert Beta 1 Other technology incubators Jazz Closed Pilot begins 2007

39. Who are the customers RTC** will address? Small and medium business: Ideally, development teams with an affinity for Eclipse based development. Small teams in large enterprises who want an agile development process. Bringing the Jazz technology to the ClearCase and ClearQuest Customers Create innovation and thought leadership for Rational Customers ** In the first release 2008 39

40. Rational Team Concert for Agile Teams • Agile teams need more than just an SCM system. They need tools to help them plan, organize, build, and ship their products. • Traditional SCM Agile best practices focused on the structure of the artifacts, Rational Team Concert adds the structure of the team and its process. • Helps structure and plan iterations with measurable executable output so that the teams know what is expected of them. • Rich integration allows team members to easily switch between different roles which is typical for agile teams (planning, development, testing). • Low total cost of ownership.

41. Agenda • Setting the Stage • Jazz Project Overview • Rational Team Concert Overview • Demo • The Jazz Project Approach • Extending Jazz

42. The Roadmap to the Jazz Vision • If you are using or buying Rational’s existing products (e.g., ClearQuest, ClearCase, BuildForge, Reqpro) you are on the Strategy Roadmap for Jazz. That is, we’ll evolve you to the value over time with minimal disruption … • We will introduce a new middleware jazz-based server family to the Rational product portfolio enabling more flexible & dynamic lifecycle service integration & team collaboration brandedRational Team Concert … • As we introduce new offerings, they will increasingly be based on the Jazz technology (e.g., Lab manager, EQM , Reporting, etc) although they may not necessarily all be branded RTC • Jazz is an enabling technology designed and built in an open commercial community model at jazz.net. Jazz is not an IBM Rational product

43. WORK WORK WORK SCM BUILD SCM BUILD SCM BUILD Rational Team Concert Express Team Concert Server(OEM / Toolkit) Rational Team Concert Enterprise The roadmap: Two roads, one destination Software Supply Chain Rational Team Concert Extended Deployment

44. Agenda • Setting the Stage • Jazz Project Overview • Rational Team Concert Overview • Demo • The Jazz Project Approach • Extending Jazz

45. Open Commercial Community Open Source Community Delivering greater openness & customer participation in the products they depend on for software delivery • IBM is opening up the Rational Software Delivery Platform for greater ease of consumption, extensibility and integration to meet the unique usage needs of our customers • IBM is providing transparent, collaborative customer participation in the development of new Rational technologies through an open commercial community Open commercial development Open source contribution of selected Jazz technology

46. Jazz Community Site

47. Open Commercial Development • IBM does two types of development - open source and commercial • Open source has traditionally implied two things • a license agreement that makes the result free • an open, transparent, release early and ofren development process • Commercial development has traditionally meant two things • a commercial license (inherent) • a closed development process (traditional practice, but not inherent) • IBM's innovation is to use an open, transparent, release early and often process for commercial development. • The license is still commercial • "Open" means that people are free to join the community doing development • "Transparent" means everyone can see what's going on. • “Release early and often” means more opportunity receive and incorporate feedback • Open transparent process is more than publishing the source code. In an open transparent process, from requirements and planning through delivery

48. Open Commercial Development: What can you do? • Open Commercial Development: Participating with the Jazz and Rational Team Concert development teams in an open and transparent way that reduces friction • Download, try out, and (we hope) feedback on betas and incubators, including source code • Access, Create, and update work items • Access milestone and component iteration plans • Provide input on requirements • Access the development wiki • Participate in discussions on the development community newsgroups

49. Toronto Jazz Development Server Raleigh • Repository • Web UI How We Use Jazz Ottawa Beaverton Zurich • Source Control • Reporting • Community Site • UI Foundation • Work Items • Agile Planning • Code Coverage • Build • Process • 2-way Xeon Server running application server (WAS) and another running DB2 • 70 developers, 20 testers, 8 doc selfhosting on Jazz. • 18,000 change-sets • 35,000 work items • 250 repository workspaces • 66K files • 10GB file content uncompressed • Integration stream has 30K files • 40 builds a day • Weekly integration build Saint-Nazaire Lexington • Static Analysis • Interop • Testing

50. Academia • Jazz Faculty Grants • University of California, Irvine • Researching how to organize and present large amounts of information to a team using multiple monitors • University of British Columbia • Exploring dynamic organization of teams with Emergent Expertise Locator tool • University of Victoria • Looking into congruence of project dependencies with communications • Other notable work • Several universities currently exploring applications in classroom use • Many research interests, including paring down for educational use, software global factory, static analysis, visualization of repository information, program understanding and transformations, reverse engineering, knowledge management, code review, agile methods, repository mining, impact of change analysis • Have announced another round of Jazz grants – proposals due by 11/13/07.