1 / 18

Rational Team Concert Overview

Rational Team Concert Overview. Joe Meagher 321 Gang joem@321gang.com. Rational History. Founded 1981, Acquired by IBM 2003 R1000 – ADA Development environment Modeling/Process UML, Method Composer Rose, XDE, Software Architect (RSA) Control

cirila
Download Presentation

Rational Team Concert Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Rational Team Concert Overview Joe Meagher 321 Gang joem@321gang.com

  2. Rational History • Founded 1981, Acquired by IBM 2003 • R1000 – ADA Development environment • Modeling/Process • UML, Method Composer • Rose, XDE, Software Architect (RSA) • Control • ClearCase, ClearQuest, Team Concert (RTC), Change, Synergy • Requirements • RequisitePro, DOORS, Requirements Composer (RRC) • Testing • Functional Tester, Performance Tester, Test Real Time • Test Manager, Quality Manager (RQM) • Planning/Management • Portfolio Manager, Publishing Engine (RPE), RRDI, Team Concert (RTC) • Jazz Platform (CLM) – RTC, RRC, RQM

  3. Software-Centric Systems Development Needs UserStories • Know work to be done, work assignments • Plan work; track work progress to plan; adapt plan • Mange configurations; facilitate parallel development • Support continuous integration practices • Send notifications when anything of interest occurs • Support distributed teams Self-managedTeams PlanningPoker (Estimating) ContinuousIntegration Collective Code Ownership Pair Programming CodingStandards Customer AcceptanceTesting TDD Refactor PlanningGame DailyStandup CustomerTeam Member Evolve Simple Design SustainablePace SmallReleases SharedVision Open Workspace Time-boxIterations

  4. Best Practice Development Tools Stack Integrations Collaboration Mylyn, Confluence, FishEye Collaboration Planning Continuous Build Issue Tracking SCM Rational Team Concert Planning Rally, VersionOne, MS Project, Excel, Sticky Notes Continuous Build CruiseControl, Hudson, Ant, Maven, BuildForge Issue/Defect Tracking Bugzilla, Trac, ClearQuest, Change, Jira Source Control/Configuration Management CVS, SVN, Git, Mercurial, ClearCase, Synergy, Perforce

  5. Team Concert in the ALM Context • Strength through integration – value multiplier on product investment • Built on Jazz team collaboration platform Publishing Engine Automated document generation Insight Project status and trends QualityProducts Rational Solution other Solutions Quality Manager Test plans Lab management Test execution history DOORS/RRC Requirements Mgmt Rhapsody System Engineering Modeling/Simulation Team Concert Project and team visibility Work scheduling and tracking Adaptive project management Configuration/build management Jazz Platform

  6. Rational Team Concert • Highly collaborative, team-based development environment • Integrates multiple aspects of the software development lifecycle, including work items, source control, build, and process support • Key capabilities: • Process awareness and customization • Team awareness, team owns work, members, plans • Work item tracking, relationships, and traceability • Build awareness, traceability, and support for other build engines • Integrations with other products to facilitate collaborative application lifecycle management

  7. Team Concert Overview Iteration Planning Integrated iteration and release planning Tracks team and individual progress and load Out-of-box support for processes (RUP, Scrum) Process Transparency Customized web-based project dashboards Live, real-time metrics and reporting Flexible, role-base process support Configuration Management Integrated stream management Component-level baselines Tight integration with Eclipse, work items Integrations with CC, CVS, Subversion Work Items Defects, enhancements, stories Queries, and query results Support for approvals, discussions Custom types, workflows, editors Integrations with CQ, Bugzilla Build Trace to work items and code changes Supports both team and private builds Local and remote build servers Supports Ant and command-line Team Collaboration Integrated chat Rich notification and filtering for all team and project related events Multiple-platform support – Eclipse, Visual Studio, and full-featured web browser Rich querying and reporting engine

  8. Team Collaboration (process) Awareness • All activity within Team Concert operate within a process • Team Concert knows team’s roles, members, timeline/schedule, organization, permissions, collaboration rules

  9. Work Items • Work is focus of development • Owned by a user • Planned for an iteration or release • Filed against a team • SCM changes, builds it includes • May define custom types with workflows and attributes • Supports complex relationships • Parent-child with progress roll-up • Blocking work • Implementing requirement (from DOORS) • Etc. Planned Work Story Story Story

  10. Supporting Complex Relationships Requirement(s)implements Tests verifying Design elementsguiding

  11. Adaptive Planning in Team Concert • Team Concert knows project timeline(s) and teams • Tracks what work is planned for each iteration • Plans provide status at multiple levels (project/team, release/iteration) Project Plan Feature Feature Feature Team Iteration Plan (Backlog) Story Story Story … Dev Team A Story Story Story Team Release Plan Story Dev Team B Story Story Story

  12. Plans Provide Customizable Views Rank Order By Iteration By Team For Single Iterations By Schedule

  13. Source Control • Team Concert provide streams model SCM • Manages changes between teams, versions, customer variants, etc. • Greatly simplifies change process • Group related files changes into a single change set (no branches!!) • Automatically associate file changes with work item

  14. Source Control Streams and Repository Workspaces • Work on multiple changes simultaneously in same workspace • No separate workspaces for developer tasks • Greatly simplifies change process for large complex systems Select work item to suspend and resume associated changes

  15. Feedback and Visibility • Dashboards (Information Radiators) provide status and trends • Data is live and collected automatically – no burden on development Risks, Blocking Work, External Commitments Quality Defect Trends Burndown Taskboard Build Health

  16. Demonstration • Review status (Deb – Project Manager – Web Interface) • Submit defect (Deb – Project Manager – Web Interface) • Fix and Deliver (Bob – Developer - Eclipse) • Confirm fix (Deb – Project Manager – Web Interface)

  17. Questions?

  18. Thank You • Joe Meagher321Gangjoem@321gang.com

More Related