Downloaded 16 times
Uploaded byTasktop
Accelerate DevOps and Quality with Integration
The document discusses the challenges faced in software projects, highlighting that 30-70% fail due to visibility issues and inefficiencies in traditional methods. It proposes a new approach using a real-time lifecycle hub and automated testing to enhance integration and reliability. Additionally, it lists various software tools and versions supported for integration testing and project management.
More Related Content
Similar to Accelerate DevOps and Quality with Integration
![Accelerating Software Delivery [Decoding DevOps Conference - InfoSeption]](https://cdn.slidesharecdn.com/ss_thumbnails/decodingdevopsapr2015nareshchoudharyshareablepdf-150727174655-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
![Lect 1 Number systems and base conversions. [Autosaved].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/lect1numbersystemsandbaseconversions-260111134109-67c2d865-thumbnail.jpg?width=640&height=640&fit=bounds)
Accelerate DevOps and Quality with Integration
- 1. © Tasktop 2016 AccelerateDevOps and Quality with Integration August 24, 2016
- 2. Meet The Presenters GernotBrandl Solutions Manager, Tricentis Jeff Downs Principal Solutions Architect, Tasktop
- 3. 30-70% of allsoftware projects fail Agile, Lean, DevOps are not enough
- 4. Lack of visibility Siloedthinking Long cycles Project failures Large-scale software
- 5. Brittle point-to-point Requires developers Maintenancenightmare Overloads Systems Does not scale Historical Approaches Manual, error prone Email & spreadsheets Does not scale Email
- 6. Delayed releases Reduced ROIfrom Agile/DevOps Time to Market compromised Opportunity Cost Hidden Expenses Failed tool deployments Integration maintenance Impossible to satisfy requests Project failures Lack of project visibility Manual & incorrect reports Audit & traceability gaps Lifecycle Challenges
- 7. A New Approach Real-timelifecycle hub Configurable, reliable Easy to scale • Manual, error prone • Email & spreadsheets • Does not scale Email • Brittle point-to-point • Requires developers • Maintenance nightmare • Overloads Systems • Does not scale
- 8.
- 9. Integration factory 3300 APItests in integration spec 500K API tests running per day 339 versions supported 9 years in the making Model-based testing Fully automated testing Over 100 person years invested World’s only knowledge base of how tools can be connected, all API/schema shortcomings All integrations work. All the time.
- 10. Jama 2014.1, 2014.2, 2015.1,2015.2,2015.3, 2015.4, 2015.5, Current On Demand Version LeanKit Current On Demand Version Microsoft Project Server 2013 SP1 Microsoft TFS 2012, 2013, 2015, 2015 SR 1, 2015 SR 2, 2015 SR3 Microsoft Test Manager 2012, 2013, 2015, 2015 SR 1, 2015 SR 2, 2015 SR3 Polarion ALM 2014, 2015, 2015 SR1, 2015 SR2, 2015 SR3, 2016; Current On Demand Version Rally (CA Agile Central) 2014.1, 2014.2, 2014.3, 2015.1, 2015.2, 2016.1; On Premise, On Demand Enterprise Version Serena Business Manager 10.1.2, 10.1.3, 10.1.4, 10.1.5, 11.0, 11.0.1.1 Serena Dimensions RM 11.2, 12.1, 12.2, 12.3, 12.4 ServiceNow: ServiceDesk PPM, SDLC Eureka, Fuji, Geneva, Helsinki Sparx EA 12.0, 12.1 Targetprocess Current On Demand Version ThoughtWorks Mingle 13.1, 13.2, 13.3, 13.4, 14.1, 14.2, 15.1, 15.2, 16.1;On Premise and On Demand Tricentis Tosca 8.3.0, 8.3 SP 1, 8.4, 9.0, 9.1, 9.2 VersionOne Enterprise and Ultimate 13.2, 13.3. 14.0, 14.1, 14.2, 14.3, 15.0, 15.1, 15.2, 15.3, 2016.0, 2016.1; On Demand Zendesk Current On Demand Version Atlassian JIRA 5, 5.1, 5.2, 6.0, 6.1, 6.2, 6.3, 6.4, 7.0, 7.1; Current On Demand Version Atlassian JIRA Service Desk 6.1, 6.2, 6.3, 6.4, 7.0, 7.1; Current On Demand Version Blueprint 6.1, 6.2, 6.3, 6.4, Current On Demand Version BMC Remedy 8.1, 9.0, 9.1.00 Bugzilla 5.0, 5.0.2, 5.0.3 CA Agile Central See Rally CA PPM 13.2, 13.3, 14.1, 14.2, 14.3, Current On Demand Version GitHub Issues Enterprise 11.10.343, 2.0.0 and higher; and Current On Demand HPE ALM 10, 11, 11.52, 12.01, 12.2, 12.5, 12.53 HPE Quality Center 9.2, 10, 11, 11.52, 12.01, 12.2, 12.5, 12.53 HPE PPM 9.3, 9.31, 9.32 IBM Rational Team Concert (RTC) 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5,4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2, 6.0, 6.0.1, 6.0.2 IBM Rational DOORS NG (RRC) 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2, 6.0, 6.0.1, 6.0.2 (opt-out mode only) IBM Rational DOORS 9.1.x, 9.2.x, 9.3.x, 9.4.x, 9.5.2, 9.6, 9.6.1 IBM Requisite Pro 7.1.0, 7.1.2, 7.1.3, 7.1.4 IBM Rational Quality Manager 4.0, 4.0.1, 4.0.2 , 4.0.3 ,4.0.4, 4.0.5, 4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2, 6.0. 6.0.1, 6.0.2 IBM Rational ClearQuest 7.1.2.0, 8.0.0, 8.0.1 iRise Current On Demand Version High Fidelity Connectors
- 11. Testing Tool Dev Tool Issue Management AgilePlanning Tool CI Tool
- 12.
Editor's Notes
- #4 Just about every company in just about every industry is driven by software. Software development and delivery teams are under tremendous pressure to deliver applications that are mission-critical to their companies. They’ve embarked on all kinds of initiatives that promise to streamline software delivery: Agile, DevOps, Lean… they’ve provided their teams training and tools... But the thing is, while these tools make individual disciplines more effective, they don’t help with the overall lifecycle. After all, the work that each of these stakeholders does is actually for the benefit of team as a whole. And the work and artifacts that each of these disciplines create is specifically to share it with other team members. So the irony in buying and using these tools is that since these tools aren’t integrated… sharing of these artifacts is actually BLOCKED by these tools. The defects are stuck in the test management tools Requirements don’t naturally flow from business analysts to testers and to developers. The fact that these tools are unintegrated and do not inter-operate, makes it difficult for team members to easily collaborate on the very work that should bind them together: the development artifacts that are common across their disciplines. The very tools that are designed to increase the effectiveness of individual disciplines are actually creating silos of information… and are actually hampering the effectiveness of the team as a whole! Silo focus is breaking the value stream…it’s the antithesis of Lean, DevOps and Agile thinking! So, back to why projects fail. A lot has been written on this topic, but it’s easily correlated to: project complexity, Cost/time overruns, scope creep and shifting expectations and lack of alignment with business strategy Agile, Lean and DevOps are all meant to help alleviate these problems... But as I said, the tool infrastructure tends to be a countervailing force against the fluid flow of information, collaboration and visibility that each of these methods require.
- #6 Last update: 16 Feb 2016
- #7 So the Cost overruns- failed tool deployments, excess work and rework and manual entry Or those lines can be related to a Delayed release- where because of a lack of communication or insight into the total SDLC lifecycle there was an inability to see things like cycle time and make adjustments accordingly in order to delivery ontime Or those lines could be related to a lack of visibility where your project failed, like so many do due to
- #8 Last update: 11 May 2016 Real-time lifecycle integration hub - Unifies value streams by flowing work across them and collecting lifecycle activity data Enables collaboration – synchronization allows practitioners work on the same artifacts in the context of their tool of choice Removes waste and administrative overhead Eliminates manual status and time reporting, searching for information, wait time Reduces rework caused by errors or lack of information Improves employee engagement – people are just happier when they don’t have to sit in status meetings, or go searching for the information they need to get their jobs done It’s configurable and reliable - Reduces complexity through automation Setting up the integrations is a matter of configuration, not programming – it’s done by a Sync admin This allows you to embraces and enable change Scales throughout organization Reliable and transparent Collects metrics across lifecycle Drive reporting, metrics and dashboards Traceability for governance and compliance For agile/lean teams: Provide information for continuously improving teams and empowered decision-making Objective evidence that your Agile/lean/DevOps transformation is delivering value
- #9 Last updated: 18 July 2016
- #10 Updated: 10 August 2016
- #11 Last updated: 18 July 2016