Experiences Applying Agile Practices to Large Systems

Transcript Experiences Applying Agile Practices to Large Systems

Rational Team Concert Overview

Joe Meagher

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) Copyright © 2011 321Gang – RTC, RRC, RQM 2

Software-Centric Systems Development Needs

• 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

User Stories

• Send notifications when anything of interest occurs

Self managed Teams Continuous Integration

• Support distributed teams

Planning Poker (Estimating) Collective Code Ownership Pair Programming Coding Standards Customer Acceptance Testing Refactor Customer Evolve Team Simple Design Member Open Workspace Shared Vision TDD Daily Standup Sustainable Pace Planning Game Small Releases Time-box Iterations

Best Practice Development Tools Stack

Collaboration Mylyn,

Confluence, FishEye

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

Collaboration Planning Continuous Build Issue Tracking SCM

Rational Team Concert

Team Concert in the ALM Context

• Strength through integration – value multiplier on product investment • Built on

Jazz

team collaboration platform Insight Project status and trends Publishing Engine Automated document generation DOORS/RRC Requirements Mgmt Quality Manager Test plans Lab management Test execution history Quality Products Rational Solution other Solutions Rhapsody System Engineering Modeling/Simulation Team Concert Project and team visibility Work scheduling and tracking Adaptive project management Configuration/build management Copyright © 2011 321Gang

Jazz Platform

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 Copyright © 2011 321Gang 6

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 Copyright © 2011 321Gang 7

Team Collaboration (process) Awareness

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

Supporting Complex Relationships

Requirement(s) implements Tests verifying Design elements guiding

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)

Dev Team A Dev Team B Story Story Story Feature

Project Plan

Feature Feature Story

Team Iteration

Story Story

…

Story Story Story

Team Release Plan

Plans Provide Customizable Views

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

Source Control Streams and Repository Workspaces

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 Defect Trends Burndown Build Health Quality Taskboard

• • • •

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)