fast track rtc innovate india 2013

© 2013 IBM Corporation

Fast track your Agile Project Teams using Rational Team Concert

Daniel LerouxIBM Distinguished Engineer – Rational Team

Concert


Outline

• What is Rational Team Concert?• What is Agile?• Rational Team Concert for Agile Teams


What if…as a developer today…

Everything I need to do my job is in one place at my fingertips

All my code, my tasks, my builds, my to do lists, my plans, my backlog

I know exactly what’s going on

Work items and RSS event feeds track everything -- change sets, builds, and approvals

Everyone else knows what’s going on (so they can stop bugging me!)

When can I test your fix?What’s your status? When will you be done? Did the plan change?

I can work smarter AND faster

Fix goofs, juggles tasks, patch in seconds, easily add or remove features. I can figure out and fix my mistakes AND the “other guy’s” mistakes…I can experiment with new ideas without impacting the rest of the team


What if…as a team today…we could…

Work more like a startup – all in one virtual room?

Our team could collaborate around all development artifacts and events in one place?

Automatically keep everyone informed of project status?

Web based dashboards track quality, status, important project updates

Move away from a culture of over committing and under delivering?

Our team is empowered with data to understand the impact of adding more work.

Transform the way we work so we can adopt rapid release cycles or agile?

We need tools that help us transform - we need a breakthrough approach, not just another point tool..

© 2013 IBM Corporation 5

Rational Team Concert – All our work …

• Source Control Planning Work Items

Process Enforcement and Automation

Dashboards & Reporting Builds – Continuous Integration


Linked together

Work Item

IterationPlan

Build

Release

Change SetSnapshotUser

Stream

Artifacts

subscribesapprovesreviews related

implements

promoted

built from

found in

plannedfor

included

reportedagainst

included

included

Workspace

change flow

“Everyone else has point product integrations. Rational Team Concert has a fusion of workflowsthat enable developers to work faster and smarter”


In one placeFriction-free communication


QueryStorage

Collaboration

Discovery

Administration: Users, projects, process

JAZZ SERVICES

Business Partner Extensions Your Extensions

Rational Developer for z

Rational Software Architect

Rational Systems Developer

Rational Business Developer

Rational Developer for i

Eclipse Clients Web ClientsVisual Studio

Microsoft .NET Clients

Rational Desktop Clients

Rational Team Concert

Web 2.0Jazz Client Extensions

Eclipse Platform

IBM Rational Extensions

Best PracticesPresentation:

Mashups

Across any platform

Windows Shell

MSSCCI

Other Clients

SCM CLI

ISPF

Open, extensible, linked data platform that enables other tools to participate and provides future portability as your platform needs evolve


Visible to everyone RTC enables “viral visibility” – free read access to web dashboards for ALL users


Outline



What is Agile?

• Agile is not about• No design• No documentation• Stand-up meetings• Rapid coding• Speed of delivery• Doing more with less…


What is Agile?

• For every stable development methodology, there need to be checks and balances

What you aim for How you get to it

Software that works Is delivered on time Responds to changes

Iteration and Release Planning

Just enough design Evolving processes Continuous integration Test driven development Stakeholder collaboration

throughout the cycle End of iteration demos Retrospectives

© 2013 IBM Corporation1414

Agile Practices

milestonesfirst

APIfirst

endgame

retrospectives

always havea client

continuousintegration

community involvement

new & noteworthy

adaptiveplanning

continuous testing

consume yourown output

componentcentric

drive with open eyes

validate

reduce stress

learn

enable

attract to latest

transparency

validateupdate

featureteams

show progress

enable

explore

validate

livebetas

feedback

signoff

End of iterationdemos/reviews

RankedProduct Backlog

Burndown Stories

Daily StandupAdoptionsExpectations

Buddy ReviewRules of theRoad

Feature teams


Start with the Planning…

It’s all in the Planning!• Strategy – vision for a business need

or direction.• Portfolio – overall product offering

that consists of applications and tools and how they integrate.

• Product – product vision and the road-map for the product.

• Release – prioritized backlog of product features committed to be delivered in a given time period.

• Iteration – short, fixed-length subsets of releases, typically 1-4 week time frame.

• Day – actions taken in a day to achieve the iteration goals.

In a Development Project the four innermost levels of the planning onion are the most important.

Strategy

Portfolio

Product

Release

Iteration

Day


Go Agile!

• Optimize your agile teams through• Real-time planning• Traceability• In-context collaboration• Development Intelligence• Continuous Improvement

• Get up and running quickly• Extend as your needs evolve• Choose the right tools


Outline



Planning (and Tracking) in RTC

• Plans are at the heart of an agile process• The product lead works on the product backlog

• Business stakeholders, market direction

• At every release, feature teams work on the prioritized items of the ranked product backlog.

• Release planning

• At every milestone, the feature team lead creates a sprint plan.• Every day, developers work off their personal work views

• My Work, My Dashboard


Rational Team Concert (RTC) Plan Definition

Work item summary

Defect, Enhancement, Task, Story, ..

Category

Planned For


• Prioritized feature list

• Plan Views• Ranked List• Work Breakdown

• WorkItem Types• Plan items: Work items that are relevant for

planning. Ex: Epics, Stories, etc.

Product

Release

Iteration

Day

• Reports• How your product backlog is evolving?• How many items are there on the

product backlog?• Can we find out how long it would take to

complete the product backlog?

• Top down Planning

Working on the … Product Backlog


• High-level plan that contains stories not planned for any release or iteration yet• Targeted for the iteration marked as Backlog Iteration• Prioritized feature list based on risk, business value, etc.

• Plan items – include only non execution items such as Epics and Stories

─ Customize with themes, business value, etc

─ Define the Done Criteria

• Sizing in Story points - rough estimates based on complexity and development effort

• Ranking - ensure that the most valuable functionality is delivered first

Managing the Product Backlog


• Progress on Product Backlog• Story Points Remaining • Open Vs Closed Work items

• Burndown report which uses Story Points

Managing the Product Backlog


Working on the … Release Backlog• Planned/Committed features for the release of the product

• Plan Views─ Iterations─ Ranked List─ Roadmap─ Teams─ Traceability (optional)─ Work Breakdown

• Work Item Types─ Plan items: Work items that are relevant for the planning.Examples: Stories

• Reports─ Team Velocity─ Release Burndown

• Top down Planning

Product

Release

Iteration

Day


• Overview of all sprints in the release

Demo

Managing the Release Backlog …


• Tasks planned for the iteration

• Plan Views• Planned Time• Ranked List• Roadmap• Taskboard / Kanban• Work Breakdown

• WorkItem Types• Execution items: Work items which have work assigned.

Examples: Task and Defect.

• Reports• Sprint Burndown

Estimated hours required to complete remaining work items.

Product

Release

Iteration

Day

Working on the … Sprint Backlog


• Focus on Execution: large stories broken down into smaller sub-stories and execution items

• Fine grained: Estimation of effort: typically estimated in Ideal Hours/Days• Custom view: Can the execution task relate to the business value expressed on

the product backlog?• Estimates are important

Demo

Planning a Sprint


• My Work View: Developers plan their assigned work and adjust estimates─ Managing new work─ Managing current work─ Managing future work─ Work Load─ Find, filter, and colorize planned work items

• Daily Stand ups: Developer Task board view to see what people are working on.

• Planned Time: Developers sort the work items in the order in which they intends to work on them

• Bottom Up Planning

Product

Release

Iteration

Day

A Day in the Life of an RTC Developer


My Work View / My Dashboard View


• Taskboard view:─ Shows plan items in the left column and execution items in the state group

columns. ─ Visualize the progress of the stories and their children.─ Ability to adjust the state quickly with drag and drop from this view.─ Color tags can be used to show the state of the plan items.

Demo

Daily Planning – stand-ups


Now, if only I had code to work on…


Parallel Development with SCM

• RTC SCM supports several levels of parallel development─ Team Stream on Server─ Personal Repository Workspace on Server─ Sandbox, locally on Client system

• Collaboration based on Change sets:─ Between Team Stream and Personal Workspace─ Between sibling Personal Workspaces

• Traceability─ Change sets get attached to work items─ Get included in builds─ Reviews─ Locate, Search


Isolation Levels – Isolate Work not People

• Repository workspaces – Provides individual isolation• You don't have to make your changes visible to the team to:• Backup or use the repository features.• Collaborate on a change with someone else

• Streams – Provides team isolation• Suspend and Resume – Provides task level isolation for personal

work• Team areas – Provides process isolation


Continuous Integration with builds

• Team of Team• Scheduled integration builds• Cross-component

• Continuous integration builds

• Each Team• Continuous builds• Always green

• A Developer• Personal builds

• Unit tests


Transparency with Feeds, Dashboards, Reports

• Team event notifications• Build events• Source Control changes• Work item changes• Team Process changes

• Dashboards• Live project status• For all stakeholders

• Reports


Retrospectives

• Teams reflect on what worked and what didn’t• How to tune the process• PMC retrospective summarizes team retrospectives

─ Defines actions for the PMC


Smart Tools, Winning Teams

• Plan your way• Out-of-the-box templates for agile workflows• Plans linked to development execution – see immediate impacts of change• Not an isolated planning tool

• Track your tasks• Smartly linked work items that behave how you want them to

• Be Team aware• Day one: up, running, coding, and productive• Linked work, enables TEAMS to find, fix and test faster • Artifact feeds, make work transparent across teams• Live project status: Not manually cobbling bad data from multiple tools


Smart Tools, Winning Teams

• Process simplified• An agile, adaptive process: trained by you• Learn, Adapt, Reflect, Change

• Manage your sources• Create, undo, share, update, review, suspend, resume, patch

• Keep builds healthy• Build continuously, at multiple levels, with the technology of your choice

• Build, deploy, test, fix• Continuous integration

• Dashboards for status• Easy-to-create, web-based dashboards


• Mike Cohn, Agile Estimation and Planning

• Effective Planning with RTChttps://jazz.net/library/article/594

• Effective planning using Snapshots in Rational Team Concerthttps://jazz.net/library/article/658

• Customizing the Agile Planning tools in Rational Team Concerthttps://jazz.net/library/article/587

Recommendations

https://jazz.net/library/article/594




www.ibm.com/software/rational

http://www.ibm.com/software/rational


© Copyright IBM Corporation 2012. 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, Rational, the Rational logo, Telelogic, the Telelogic 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.

www.ibm.com/software/rational

http://www.ibm.com/software/rational