Innovate2011 DevOps TSRM RTC

Editor's Notes

• #2: Author Notes: This is the PowerPoint template for the Innovate 2011 Track Sessions ALL FINAL FILES MUST BE CONVERTED TO LOTUS SYMPHONY. Learn more here: http://w3.ibm.com/connections/wikis/home?lang=en#/wiki/Rational%27s%20Phased%20Approach%20in%20Migrating%20to%20Lotus%20Symphony Additional IBM Rational presentation resources can be found on Rational’s Managing the Brand W3 Intranet site: https://w3-03.ibm.com/software/marketing/marksite.nsf/AllMarketingPages/Brand-Rational-rt_rtb?opendocument?opendocument Third party material cannot be used in a presentation without written permission (this includes product and Web page screen shots). Images must be acquired from a ‘royalty-free to use’ source such as: Microsoft Clip Art library http://www.freebyte.com/clipart_images_photos_icons/#freevectorgraphics http:// www.freedigitalphotos.net / IBMers can use images from: IBM image library: https://w3-03.ibm.com/software/marketing/marksite.nsf/AllMarketingPages/Brand-Rational-rt_rtb?OpenDocument&ExpandSection=3,2#_Section3 Royalty free images in Marketing Asset Manager database (you will need to register to access this site) : http://217.28.164.25/IBM001/templates/login.html
• #3: Author Notes: Confused whether to convert this deck to Lotus Symphony? Learn more here: http://w3.ibm.com/connections/wikis/home?lang=en#/wiki/Rational%27s%20Phased%20Approach%20in%20Migrating%20to%20Lotus%20Symphony This template has been created in PowerPoint 2003 Depending on how the source file was formatted, some slides will not ideally reformat once the template is applied. Therefore, some reformatting will be necessary. Reapply slide layouts: Task Pane / Slide Layout Can be applied thru normal or slide sorter view May have to reapply the layouts more than once in order to take effect Limit altering slide layout attributes on your slide (fonts, positioning, text box anchoring, positioning, etc.), this will create less reformatting rework when switching templates in the future or repurposing this slide in other presentations. Use “shift returns” if text wraps are needed to wrap around imagery. If slide layout customization is needed, it’s advised to break the customized text box from the slide layout by selecting the bounding box of the altered text box and cutting it from the slide, apply either the title slide layout or the blank layout, and then paste the text box back onto the slide. Your custom-formatting of the text layout will then be retained for future repurposing in other presentations. Recolor graphics if needed by using the embedded color palette swatches already in this template. Slide text: Don’t create long sentences or paragraphs on slides. Use concise bulleted list format. Use speaker notes for supporting bulleted content to avoid slides that are too text heavy. Use sentence case capitalization for presentation titles, slide titles, category labels and bullets: Format / Change Case / Sentence Case. Initial capitalization is limited to our products and offerings. When referring to our products, use the correct full name, (e.g., IBM Rational ClearCase). See “IBM Rational A-Z Product List” on the Rational brand All-in-One-page for reference: http://w3-103.ibm.com/software/xl/portal/!ut/p/_s.7_0_A/7_0_IP?type=doc&srcID=R9&docID=R106605Y95736W79 Avoid using cartoon like clip-art, use photo-art instead. Third party material cannot be used in a presentation without written permission (this includes product and Web page screen shots). Images must be acquired from a ‘royalty-free to use’ source such as: Microsoft Clip Art library http://www.freebyte.com/clipart_images_photos_icons/#freevectorgraphics http://www.freedigitalphotos.net/ IBMers can use images from: IBM image library: https://w3-03.ibm.com/software/marketing/marksite.nsf/AllMarketingPages/Brand-Rational-rt_rtb?OpenDocument&ExpandSection=3,2#_Section3 Royalty free images in Marketing Asset Manager database (you will need to register to access this site) : http://217.28.164.25/IBM001/templates/login.html Close each presentation with the mandatory “Rational ThankYou Slide” located in the back of the .ppt file.
• #4: Background on problem space Slides 1-5, John Need for openness / OSLC Slides 6-11, Steve TSRM – RTC Slides 12+, John
• #7: Solutions designed only for point-to-point integration No external review or visibility into solution Solutions built to patch immediate need Often integrations were built after the fact with limited product APIs Solution design goals and approach limited No consensus driven approach Integrators limited to a small set of business partners No open process for other interested parties to get involved Limits solution to particular use cases and technologies Restrictive licenses and usage of intellectual property License fees or fear of giving up IP, force alternative solutions
• #8: Single repository Hard to add existing tools Difficult to evolve tools individually Limited to a single vendor’s tools or affiliates Point-to-point integrations Limited coverage: there are too many tools to cover more than a small fraction of possibilities Tight dependencies between tools require lockstep upgrades Proprietary APIs create vendor lock-in Universal metadata standard Too slow to complete to keep pace with the market Hostage to vendor in-fighting Difficult to migrate existing project data and assets Standard implementations Requires “forklift” rip and replace of existing tools Hard to get widespread vendor support Insufficiently flexible to address different user approaches
• #9: Now… what’s the technical approach?
• #10: Open Services for Lifecycle Collaboration Apply the OSLC Architectural Approach to Integrate Design and Delivery starting with the Customer Validated Scenarios 1. Talk about how in Rational we used to have point-to-point integrations 2. Then we moved to OSLC (tell brief OSLC motivational talk) 3. And now we ’re exploring doing the same thing in Tivoli and between Rational and Tivoli (hedge appropriately)
• #11: Resources have representations XML encouraged, not required Unprecedented extensibility Extend “web” New [mime-] types Extend representations
• #12: 1. Talk about how in Rational we used to have point-to-point integrations (Click) 2. Then we moved to OSLC (tell brief OSLC motivational talk) (Click) 3. And now we’re exploring doing the same thing in Tivoli and between Rational and Tivoli (hedge appropriately)
• #13: The previous chart introduced Service Desk and Service Catalog as applications (PMPs) thatoperate on top the Service Management Platform. This chart now introduces the concept of the Service Request Manager as a common package of Service Desk and Service Catalog capabilities. What we have in common here is the concept of satisfying user requests. In general, requests to the Service Desk are handled on a case by case basis; while Service Catalog requests are usually handled in pre-configured manner that is intended to fulfill the request in a best practice manner. Service request center (SRC) offers a unified solution for service request management – whether it is performance problem needing help from service desk or request for provisioning of new software into your workstation through service catalog. Users need to access one application via web or call a person over phone or simply send an email. SRC has built-in service desk functionalities such as incident & problem management; offering solutions to the users through knowledge management; integration with network/application management products to open incident tickets automatically. It also offers service delivery functionalities through its catalog where users can “shop” for services they need through online catalog. Remember they need to pay for what they buy……enabling tighter control over expenses.. Technical highlights of the product are mentioned in the bullet points.
• #14: When: - use this to create and maintain links between issues found in production and the fixes made in development to address them - use this to understand the status of problems which require development teams to provide fixes Why: - it is very common for coordinated actions to be taken across development and operations. Linking respective work items increases efficiency of all collaborators - linking information can assist with problem analysis and troubleshooting of similar problems found by operations in the future. How: - background processes (tasks) are run which maintain synchronization of information between TSRM and ClearQuest - extensible to allow for an organization's customized fields to also be updated appropriately
• #16: Author Note: Optional Rational DEMO slide. Available in English only.
• #17: Speaker Notes: In Phase 1: We are linking Problems in TSRM to Defects in RTC We support interactions that are initiated from TSRM. Phase 1 TSRM-RTC Integration will be available March 2011 from the ISM Library In second phase: We will support bidirectional interactions. More process artifacts (e.g., Change) will be integrated.
• #22: Author Note: Optional Rational QUESTIONS slide. Available in English only.
• #24: Daily iPod Touch giveaway sponsored by Alliance Tech Each time you complete a session survey, your name will be entered to win the daily IPOD touch! Complete your session surveys online each day at a conference kiosk or on your Innovate 2010 Portal! On Wednesday be sure to complete your full conference evaluation to receive your free conference t-shirt!
• #25: Author Note: Mandatory Rational Closing Slide (includes standard legal disclaimer). Available in English only.