Front cover Collaborative Application Lifecycle Management with IBM Rational Products An IBM blueprint for Collaborative Application Lifecycle Management Green-thread reference scenario showing the Agility-at-Scale approach IBM Jazz products incorporated into an enterprise solution Mats Göthe Carolyn Pampino Philip Monson Khurram Nizami Katur Patel Brianna M. Smith Nail Yuce ibm.com/redbooks International Technical Support Organization Collaborative Application Lifecycle Management with IBM Rational Products December 2008 SG24-7622-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (December 2008) This edition applies to IBM Rational Build Forge Enterprise Edition 7.1, Rational ClearCase 7.1, Rational ClearQuest 7.1, Rational RequisitePro 7.1, Rational Quality Manager 1.0, Rational Requirements Composer 7.1, Rational Software Analyzer 7.0, and Rational Team Concert 1.0. © Copyright International Business Machines Corporation 2008. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Preface . xiii The team that wrote this book . xiv Become a published author . xvii Comments welcome. xvii Part A. Collaborative Application Lifecycle Management defined. 1 Chapter 1. Introduction to Application Lifecycle Management and this book . 3 1.1 The scope of Application Lifecycle Management . 4 1.1.1 People, process, information, and tools that drive the life cycle . 4 1.1.2 The scope of this book . 7 1.2 Using this book . 11 1.2.1 Goals and objectives. 11 1.2.2 How this book is organized . 11 1.2.3 Target audience and chapters of interest . 13 Chapter 2. Collaborative Application Lifecycle Management . 15 2.1 Understanding Collaborative Application Lifecycle Management . 16 2.1.1 Changes in the ALM market . 16 2.1.2 A CALM blueprint to streamline software delivery . 24 2.2 Life-cycle collaboration and management. 30 2.2.1 Success indicators . 30 2.2.2 Cycles of activity in the development organization . 35 2.2.3 Scaling agile methods. 38 2.2.4 Aligning work assignments . 44 2.2.5 Being requirements driven . 45 2.2.6 Striving for build clarity and quality . 46 Chapter 3. A scenario for CALM . 47 3.1 A story telling a tale of integrations . 48 3.1.1 Story objectives. 49 3.1.2 The context for the story . 49 3.2 The project . 49 3.3 The software delivery team . 50 3.3.1 A team of teams . 51 3.3.2 The solution team leads . 53 3.3.3 The agile development team. 54 3.3.4 The solution testing team . 55 3.4 The approach . 55 3.4.1 Phases and iterations for establishing cadence . 56 3.4.2 Frequent builds to drive clarity and quality . 57 3.4.3 Testing to drive quality . 57 3.4.4 Lean governance . 58 3.5 A story told act by act: Completing an iteration. 58 3.5.1 Act 1: Responding to a change request . 60 3.5.2 Act 2: Collaborative development . 61 © Copyright IBM Corp. 2008. All rights reserved. iii 3.5.3 Act 3: Enterprise integration builds . 63 3.5.4 Act 4: Managing quality. 64 3.5.5 Act 5: Delivering the solution . 65 3.6 Life-cycle collaboration . 66 3.6.1 Life-cycle assets in this CALM scenario . 66 3.6.2 Agility at Scale . 67 3.7 Reference architecture and configuration . 69 3.7.1 An enterprise CALM solution . 70 3.7.2 Product integrations for this scenario . 72 3.7.3 Supporting distributed teams . 73 Part B. Act 1: Responding to a change request. 77 Chapter 4. The team responds to a requirement change . 79 4.1 Introduction to change management. 80 4.1.1 The changing change management market . 80 4.1.2 The changing requirements definition and management market . 83 4.1.3 Collaborative development blueprint and change management. 88 4.1.4 Requirements definition and management blueprint. 93 4.2 A reference scenario for responding to a change request . 105 4.2.1 The actors . 106 4.2.2 The workflow. 106 4.2.3 Bob submits a request . 108 4.2.4 Patricia updates the project iteration plan. 108 4.2.5 Marco updates the development iteration plan . 109 4.2.6 Tammy updates the solution test plan . 109 4.2.7 Patricia confirms the project iteration plan . 110 4.2.8 Bob defines and manages the requirements . 111 4.3 Considerations in change management . 112 4.3.1 Analyzing and prioritizing requests . 112 4.3.2 Sizing requests . 113 4.3.3 Rational Team Concert for stakeholder requests . 114 Chapter 5. Rational ClearQuest, Requirements Composer, and RequisitePro to manage stakeholder requests . 115 5.1 Act 1: Responding to a change request . 116 5.2 Rational RequisitePro and Rational Requirements Composer . 117 5.3 Rational ClearQuest ..