Vous êtes sur la page 1sur 34

The world is flat(ter): software development and reducing barriers with Rational Team Concert

Eyal Abukasis Director East Region, ATSC eabukasis@atsc.com Pratik Bengali pbengali@atsc.com Track #: RWI-2137A

The premiere software and product delivery event. June 610 Orlando, Florida

How to use this template

To allow all masters of your presentation to be updated correctly, download this template to your hard drive and copy your existing slides into the new template See slide notes for further formatting instructions

Eyal Abukasis - Background


Historical retrospective
The 80s: Teams, tools andWaterfall the 90s: teams (more organized), tools (more integrated) andIterative development The new world: teams (leaner), tools (integrated, transparent) andAgile

An Introduction to Agile and Scrum Jazz and Rational Team Concert Real Worlds Case Study and its results Demo of our environment and solution

Historical Retrospective the 80s

Pre-90s: Remember when

Few projects (mostly small) Mainframe, Unix platforms Distributed started to gain support Small teams People wearing multiple hats Few tools No need for collaboration, visualization, tracking, dashboards Co-located Little need for process Waterfall is KING!

Requirements Analysis


Conceptually simple Logical order Disciplined Well defined milestones

Code and Unit Test

Subsystem Integration

System Test

The world is getting flatter

Then world started to get FLAT

World Wide Web Workflow Software Outsourcing Off shoring Supply chaining In-sourcing

No body wanted to be left out

Capital pouring into the markets Funded projects with no limits We began to get sloppy with our projects and code

Historical Retrospective the 90s

The 90s
Projects became larger (more code, multiple platforms, multiple interfaces) Complexity increased (LoC, Requirements, models, testing) Outsourcing became the new buzzword (distributed teams)


How do we track changing requirements, code, tests, metrics How do we communicate How do we share artifacts without tripping Process? What for? Whats that? How? How? How?

Solution: Rational Suite

Multiple point products Rational Unified Process (Iterative) Some dashboards

Meet The IBM Software Development Platform A complete, open, modular, and proven solution
Model, simulate, assemble, and monitor business processes


Rapidly construct, transform, integrate and generate code


Deployment Manager
Provision, configure, tune and troubleshoot applications

Visually model applications and data

Design, create, and execute tests

Project Manager

Follow a common process Track project status Manage requirements

Manage change and assets Manage quality

Iterative Processes

Reqs Design Code Test Reqs Design Code Test

Well-defined milestones Resolves risks early Can experiment to unearth requirements Measure progress via actual system development Provides for early partial deployment



Early Integration Results

Progress (% Coded)
100 90 80 70 60 50 40 30 20 10 5 10 15 20 25 30

Iterative Development


Final Test Integration Begins Late Design Breakage









Problems Implementing RUP

Too much information 2000+ pages Tailoring approach is subtractive not additive Leads to high-ceremony heavyweight implementations Often implemented from an artifact perspective Moves focus away from executable software to a document centric view Sometimes too much emphasis on architectural risk vs. business risk Architecture is important but so is delivering business value

Thenthe good times end. Back to the drawing board

Wasnt that enough? What are the challenges? Year 2000 the bubble bursts environment as we know it was changing
Capital became scarce Projects needed to prove fast ROI To more with less Are the current methods too heavy? Should tools drive process or vise versa?

Where Does Process Come From?

Agile Principles drive the technical practices.

Lightweight, minimalist, low-ceremony Highly collaborative: People over process and tools Value-driven: Frequently provide value to end users Embrace Change: Adapt instead of Predict Feedback: Promote extremely tight response loop Build Quality In: Adopt a stop the line mentality

Some key Agile Practices

Iterative and incremental development Two levels of planning Frequent releases Self-organizing teams Just-in-time requirements specification Concurrent testing (developer & system) Continuous Integration Refactoring Unit testing & Test Driven Development (TDD) Retrospectives

Iterative and Incremental Development

Iterative Develop working software in time-boxes Fix date, manage scope Incremental Progressively evolve the system Small chucks of working, tested software Adaptive versus Predictive Respond to change by expecting it Use frequent feedback to adjust plan


Scrum Characteristics

And the details of scrum

Sprints Product Backlog Product Owner Scrum Master The Team Daily Scrum Retrospective

Envisioning a platform that can transform software delivery

Jazz is a project and platform for transforming how people work together to deliver greater value and performance from their software investments. robust, extensible and scaleable globally distributed, fluid & dynamic community-based & open at Jazz.net

Collaborate in Context
Enable team transparency of who, what, when, why Build team cohesion and presence Automate hand-offs so nothing falls through the cracks

Right-size Governance
Automate team workflow improving productivity Automate data collection eliminating administrative overhead Real time reporting and alerts reduces project risk

Day One Productivity

Dynamic provisioning of projects and teams Real-time iteration planning and workload balancing Unify teams with tools choice

Dynamic integration of people, process and projects across the lifecycle

How Jazz is different from past approaches

Dynamic integration of People
Desktop/database integration Global integration Function first Team first Pre-determined tool function Dynamically extensible

Rigid rules Creative collaboration Manual tasks Process aware and transparent Proprietary infrastructure Internet standards



Lengthy project onboarding Day one productivity Hindsight analysis Continuous steering Status guesstimates Real-time insight

...across the software lifecycle

An evolution of value in collaborative ALM bringing forward existing investments and delivering new innovative capabilities
c Existing IBM Offerings New IBM Offerings Business Partner Offerings

offering offering




offering offering

Best Practice Processes

Search and Query Dashboards Team awareness Events notification

In context collaboration


JAZZ TEAM SERVER Open Lifecycle Service Integrations

Client Integrations
Eclipse Web 2.0 Visual Studio Powered by

Server Integrations
Existing IBM offerings Business Partner offerings Open source offerings

Jazz Value proposition

Integrated collaboration improves team effectiveness Designed for organizationally distributed development Process integration for enhanced productivity, repeatability, and best practices Seamless integration across the software development lifecycle Traceability across the life cycle Non-intrusive visibility into project status and health information Lower Total Cost of Ownership Scalability: process and team and project size Extensible on the client and server A growing Eclipse-based community

Rational Team Concert: A closer 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

Integrated stream management Component level baselines Server-based sandboxes Identifies component in streams and available baselines ClearCase connector

Work Items
Defects, enhancements and conversations View and share query results Support for approvals and discussions Query editor interface ClearQuest connector

Work item and change set traceability Build definitions for team and private builds Local or remote build servers Supports Ant and command line tools Integration with Build Forge

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 enables team members to communicate in context of their work

Improve business agility and project success rates

IBM Rational Team Concert

Facilitates the principles of high-performance teams

Optimized for Agile processes inlucluding Scrum, The Eclipse Way, OpenUP, etc out of the box

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

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

Advantages of RTC Case Study would likes

Web 2.0
Social networking drives team collaboration and productivity enabling today's distributed teams to work in unison.

Iteration planning and end to end visibility

Real time project progress via web browser planning and estimation and metrics for each milestone were all linked end to end so everyone new the projects progress in real time?

Open rather than proprietary

Any platform Leverage open source eco system Support for client and server side plug-ins

Support for legacy tools already in place

Case Study - Healthcare

Started with Agile discovery, pilot and mentoring Using myriad of legacy Rational tools (CC, CQ, RFT, RPT, RSA) Introduced RTC to support pilot effort (other teams evaluating other options)
Product backlog Task board Burn down charts Integrated with CC, CVS, CQ, Bugzilla Customized process to each team

Solution and training rolled out on a per Role basis

Day in a life scenarios Use language and terminology of the customer (increase comfort level)

Where are they now?

Agile coaches in place to help with The Agile way and the tools to support Multiple teams have adopted Agile and RTC Teams are exploring RQM and RRC as a natural fit with RTC Management buy-in (visibility, reporting)

Whats next?

Additional Jazz tools and integrations Additional 3rd party plug-ins Better integration and collaboration (increased transparency) Less overhead (increased productivity) Faster on-boarding processes Easier customization Better reporting Support for multiple processes Jazz based tools are the future (or at least the near future )

Daily iPod touch giveaway

SPONSORED BY Complete your session surveys online each day at a conference kiosk or on your Innovate 2010 Portal! Each day that you complete all of that days session surveys, your name will be entered to win the daily IPOD touch! On Wednesday be sure to complete your full conference evaluation to receive your free conference t-shirt!


Copyright IBM Corporation 2010. 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 IBMs 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.