Automated Distributed Planning With RTC and Stages

Transcription

1 Automated Distributed Planning With RTC and Stages Stages Insights 2015 Dimitrios Dentsas Software Engineer Robert Bosch GmbH 1

2 Outline What exactly do we mean by Distributed Planning? How do we approach planning with Rational Team Concert at Bosch The Case for Process Automation Steps to achieve Process Automation Demo Q&A 2

3 A Reuse-Based Approach Product A Product B Component 1 Component 2 Component 3 A Multi-Tier structure Loosely coupled independent components are composed into software systems A Product is potentially served by a number of Component Teams A Component Team potentially serves a number of Products 3

4 A Typical Change/Release Management Scenario Customer provides a Change Request to the Product Manager After careful analysis the request is approved and broken down to Needs All Needs have to be implemented by the Component Teams, for which they return tested software deliveries. Product B Component 2 Component 3 4

5 Planning with RTC at Bosch Structuring of Project Areas Two Project Areas for Planning and Executing Execution Area is self-contained Planning Area is dependent on Execution Area (Progess Info) Planning Area is customer oriented Push Requests Planning Area (Consumer) Provide Progress Info Execution Area (Provider) Process A Process B 5

6 Planning with RTC at Bosch Ok, but how do we approach planning in RTC? Two Project Areas for Planning and Executing Product Teams have dedicated Team Areas for planning Software Releases (Product Releases). They break down their Business Needs (Product Needs) into specialized work items and push them to the Component Team Backlogs! 6

7 Planning with RTC at Bosch Ok, but how do we approach planning in RTC? Product Manager plans a new release and associates a set of Needs to it Those Needs can be broken down further into component-specific Needs All component-specific Work Items are pushed into the Backlogs of the respective component team areas. Component Group 1 Product Alpha Component Group 2 7

8 Things we notice and complications we see Process patterns emerge across Product/Component Team Areas A lot of steps in planning produce overhead and reduce efficiency And last but not least 8

9 IBM Collaborative Lifecycle Management Powered by the Principles of Linked Data 9

10 How can we ensure that our processes are implemented consistently across the organization? 10

11 Steps to achieve Process Compliance I. Identify Important Workflow Fragments II. See what changes are needed in your Process Configuration and how each Workflow Fragment can be simplified and automated III. Provide a means of orchestrating said Workflow Fragments in order to achieve full compliance to your organizations Business Processes 11

12 Identify Workflow Fragments A number of different Workflow Fragments can be extracted: Plan new Product Releases Analyze Incoming Change Requests Breakdown of default Work Items Create tasks for integration and testing 12

13 Make things as simple as possible, but not simpler. OSLC Multi-Picker based Breakdown Break down Product Need WI File them against the chosen categories Push new items to remote Teams 13

14 Method Park Stages Process Management for Systems Engineering Fully web-based Define, share and use processes directly in Rational Team Concert Define Share Use 14

15 Method Park Stages Control Define Compliance Project Status Reports Measurement Repository Process Metrics IMPROVE Organizational Processes Use TAILOR Maturity Models Industry Standards Company Standards MEASURE Project Processes Compliance Reports DOORS ClearCase MS Project Team Concert Test Manager Subversion Sharepoint 15

16 Method Park Stages Define & Push Create and tailor best-practice models and processes in Stages Automate execution of lifecycles by pushing to RTC Instant adoption of process changes Automate boring tasks and concentrate on creating value. 16

17 Push process models from Stages to RTC 17

18 How Stages Works under the Hood The Stages Operation Participant catches all Work Item Events The Process Config Source provides the complete Workflow Model The next enactment job is put into a Task Queue Work Item Event Execute Task Queue Put Determine Workflow Transition 18

19 DEMO 19

20 Thank You! Questions 20