Enterprise CLM Usage Model

1. Enterprise CLM Usage Model Scenario Driven Configuration

2. Background • Your Collaborative Lifecycle Management (CLM) solution currently includes a set of server and client tools, out of the box, integrations, templates and reports. This workshop is intended to address the overall usage model, selection of out of the box capabilities, allocation of responsibilities between roles and products, redefine reporting needs and set the boundaries for the practice area/product configuration workshops. • IBM recommended practices and configurations that support traditional and agile methods for the software development lifecycle (SDLC). The CLM configurations provide a means to plan, track, measure, reuse and automate the Software Development Lifecycle (SDLC) activities. During this workshop we will • Explore the potential of the CLM capability during a hands on demonstration • Review your organizations current SDLC processes, gates and products • Use this presentation as a means to capture the initial configuration and usage model • Following this workshop we will hold practice/product workshops to further refine the usage model for the particular area/product and implement the configuration within the product in preparation for a pilot of the solution.

3. Defining CLM usage model “Check List”

4. Adoption approach

5. Milestone-based Adoption Framework Milestone 0 Solution & Plan Approved Milestone 1 Core Team Enabled Milestone 2Incremental Working Model Defined Milestone 3Ready for Pilot Milestone 4Ready for Roll out Milestone 5 Adoption Complete Execute Adoption Strategy Prepare and Plan Pilot initial Win Scale Assess and Roadmap

6. Adoption Milestone Measures • Pilot objectives approved • Adoption framework defined • Adoption assets delivered and approved • Asset reuse strategy defined and tested • Pilot team completed introduction training • Core team prepared for mentoring • Core team resourced • Solution enablement delivered to core team • Solution usage workshop complete • Dev environment architecture approved • Develop environment deployed and tested • Communications plan initiated • All objective capabilities piloted • All releases rolled out • Core team evolution to COE completed • Monitoring and mentoring program in place • Department adoption goals met 3 5 1 • Stakeholders engaged or socialized • Solution v1.0 of approved • Example in Dev environment for enablement/demos • Successful Solution UAT complete • Test / production environment architecture approved • Deployment and performance test production complete • Release validated in pilots • Adoption Framework approved • Adoption schedule approved • Reusable assets delivered and approved • Continuous Improvement program in place • Final performance testing complete • Assessment completed • Roadmap resourced • Project plan outlined Milestone 0 Solution & Roadmap Approved Milestone 1 Core Team Enabled Milestone 2Working Model Defined Milestone 3Ready forPilot Milestone 4Ready for Roll out Milestone 5 Adoption Complete 0 2 4 Execute Adoption Strategy

7. Adoption Activities and Tasks • Measured pilot objectives • Organizational Adoption Plan • Training & Job Aids • Adoption assets • Data reuse strategy • Deploy production environment • Incremental releases • Common, reusable framework • Scale usage across enterprise • Manage Change • Resource Membership • Focused Enablement • Solution Workshop Execute Adoption Strategy • Business Goals • Measured Objectives • Current Status Assessment • Prioritized Strategy • Actionable Roadmap • Practice area and usage threads • Break out sessions • Reuse Current practices • Configure Solution • Prototype and document model • Gain Approval • Mentoring • Measuring objectives • Validate introduction process • Collect lessons • Continuously improve • Final roll out preparations

8. Iterative Roll Out Tailored Reporting Coded Extensions Data Reuse Measures OOTBNew Features Third Party Current Usage Integration Automation Lessons AuditsNew Usage Prototyping Deployment Backlog Release1 Release 2 Release 3 • Prioritize and Select those features, functions that meet your initial release needs • Prioritize and schedule follow on improvements • Capacity is important • Core team preparation / mentoring • Organizational adoption • Incremental build up of COE • Deploy initial capabilities and improve/ mature them over one or more releases is the recommended approach • Allows you to “adjust course” if you see greater value that differs from initial plans • Focus on core capabilities to then expand based or your priorities and capacity

9. Requirements

10. Requirements Section • This sections is used to capture your business needs, CLM requirements and any assumptions or risks that affect the usage model. • Business needs should include the approach to measure success at achieving the outcomes. Ideally this will be performed within CLM using OOTB or RRDI reports. • Once requirements are defined align them to this usage model to validate/reflect satisfaction of the requirements. A set of CLM project areas may be created to define the usage model content, the stories/tasks to implement the model in CLM and adopt it and the validation or UAT of the iterative capabilities. • The diagram below is an option for creating the usage/implementation model in CLM RRC RTC RQM Planning Item UAT Business Need Measure Risk Performance Functional Test Requirement Execution Item Release Plan Release Test Plan Role (Actor) Practice (Use Case) Reusable Asset Release Collection

11. Business Needs and Outcomes

12. CLM Requirements

13. Risks and Assumptions

14. Methodology

15. Methodology • Use this section to describe the clients methodolgy(s) that will be used with CLM. The goal is to capture enough of their processes to influence how the tools will be used and configured. This will also limit the practice area discussions for detailed usage. • You do not need to elaborate in detail, but rather provide enough information for the context of the capabilities and practices

16. Extreme Programming (XP) Unified Process (UP) Agile Modeling Scrum Agile

17. Traditional (Waterfall/RUP)

18. Other Methodologies Disciplined Agile Delivery

19. Capability Practice Framework

20. Usage Model Analysis Management Management Management Explain the Capabilities to be improved, deployed or introduced Define current and objective practice maturity and specify practices for this usage model Derive Use Cases or user stories for each role that must be supported by the solution, techniques and reusable assets. Output role permissions, skills and tasks, practice procedures and reusable assets and tool architecture and configuration needs for the solution

21. Usage Model Framework Capability Tool Configuration Measures Business Outcomes Practice People Practices Technology Deployment Requirement Role Skill Description Performance, Licenses, Integration Detailed Use Cases Reusable Asset Improvement Phase Scope

22. Initiative Scope Level of importance: Critical Important Nice to Have Not Critical Plan /Measure Develop /Test Release / Deploy Monitor / Optimize Portfolio Management Code Deployment Monitoring Requirements Test Provisioning Customer Feedback Release Pipeline Change & Configuration Management Dashboards/ Analytics

23. Capabilities

24. Capability Descriptions

25. CLM Role Description

26. Use Case Approach

27. Practice based Maturity Model Define release with business objectives Measure to customer value Improve continuously with development intelligence Test Continuously Leverage Quality Tends Manage environments through automation Provide self-service build, provision and deploy Automate problem isolation and issue resolution Optimize to customer KPIs continuously • Plan and source strategically • Dashboard portfolio measures Manage data and virtual services for test Deliver and integrate and build continuously Standardize and automate cross-enterprise Automate patterns-based provision and deploy Optimize applications Use enterprise issue resolution procedures Link objectives to releases Centralize Requirements Management Measure to project metrics Link lifecycle information Deliver and build with test Automate testing Embed Quality Reporting Plan departmental releases and automate status Automated deployment with standard topologies Monitor using business and end user context Centralize event notification and incident resolution Document objectives locally Manage department resources Manage Lifecycle artifacts Schedule SCM integrations and automated builds Test following construction Plan and manage releases Standardize deployments Monitor resources consistently Collaborate Dev/Ops informally

28. Capability and Use Case Model

29. Capability and Use Case Model

30. Practices for Cross Cutting

31. Practices for Plan and Measure

32. Practices for Develop and Test (1 of 2)

33. Practices for Develop and Test (2 of 2)

34. Practices for Release and Deploy (1 of 2)

35. Practices for Release and Deploy (1 of 2)

36. Practices for Monitor and Optimize

37. Use Case Description: Define or refine requirements Example of completed practice

38. Solution Architecture

39. Logical Tool Architecture 3rd Party Tool 3rd Party Tool RRDI RFT RRC RQM RPT Clients RTC JBE RAM RAF SCP

40. Logical Architecture Description

41. User and Tool Interactions RRDI Web Client Web Design Administer RRC RQM Web Web Client RTC Test Stakeholder Web Client Web Client Analysis Develop Manage Design

42. Usage Capacity Total/Concurrent * = Reviews only

43. Licenses Requirements Type/Number

44. Physical Architecture • Physical Architecture Diagram

45. CLM Information Model

46. Information Model • This model can be developed incrementally • Overall: Overall model, align information to repository, separate interests, logical links • Repository level links: • Define packaging (project, team, folder) model. Requirements pattern model with types, attributes, intra-repository links, method for creating placeholders, Pattern parts to process alignment, informal/formal reviews • Define packaging (Repository, Project, Team) model. Project work item model using IBM OOTB process templates (eg. SCRUM, FPM, DAD). Packaging plan for system administration • Define packaging (Repository, project, team) model. Use OOTB Test object linking model. Define Requirement place holder model. Define defect creation model. • Define packaging for projects and models. Architecture meta-model and linking between model diagrams, elements and RRC/RQM/RTC objects. (Business processes and use cases in RRC) • Develop and document model with levels of abstraction. Incorporate into training and job aids assets.

47. Overall Information Object Model (Agile) Scrum Template RRC Cross Dept RTC Business Needs Release Plan Adoption Item Epic Single Dept Business Requirement Retrospective Story Defect Release Collection User Story Task Impediment Biz Rule Track Build Item Non-Functional UI/Flow Build Definition Build Result RQM RDM Business Processes Test Plan Test Case Appl Arch Test Execution Record Data Arch Svc Arch Test Results

48. Information Model Descriptions (Agile)

49. Overall Information Object Model (Waterfall) FPM Template RRC RTC Cross Dept Goal Program Plan Cross Team Biz Need Milestone Feature Release Collection Release Plan Risk Issue Biz level BPM PCR Risk Action Milestone Biz UC Task Biz Rule Defect NFBR UI/Flow Build Definition Build Result RDM RQM Test Plan Biz Arch Appl Arch Test Case Data Arch Svc Arch Test Execution Record Test Results

50. Information Model Descriptions (Waterfall)