As DevOps enters its second decade, it’s time to re-evaluate your strategy.
Organizations can easily fall into the trap of settling for “good enough” because measuring productivity and flow across varying teams and systems is challenging. That’s where value stream management comes in.
Join HCL UrbanCode leaders, Brian Muskoff and Steve Boone, for a conversation about scaling your DevOps strategy by focusing on data and culture through value stream management. In this webinar, we’ll cover:
What is value stream management and how it works in a DevOps culture
How to harvest opportunity from your DevOps pain points
The resources you need to successfully implement a value stream management approach
This webinar is especially beneficial for technology executives, transformation leaders and DevOps managers who are responsible for their DevOps strategic direction.
Much of this was locally optimized, where as in Day 2 the whole system needs optimized
Little ‘a’ agile was generally team level or teams for a product line. Big ‘A’ Agile will be optimizing the business – Running IT as a Business creates enterprise Business Agility
Do you feel like you're getting a late start to a DevOps and/or Agile transformation? You may not be as late as you think. Most attendees at the 2019 European SAFe Summit classify their status as "Crawl'.
Velocity is:
A conflict spotter – a conflict resolution tool
A business process optimizer
Most Enterprises are driving to cloud, but currently have Product teams, platforms application architectures all over the spectrum and will for years. It’s been described as a digital battlefield where you can look behind you and see the wreckage of change over the decades, but much of it still runs the business and needs maintained. 75% of all transformations fail.
3 leaders – CIO, CTO & PMO – spread across different orgs competing agendas and funding for the same goals – affinity for certain dimensions
Loosely coupled architectures and teams are strongest predictor of CD - DORA
APP Modernization - The transition period of rewriting or upgrading legacy apps, and/or developing all new applications with modern languages and protocols.
How can we make DevOps ROI == Business ROI
Optimize beyond Agile & CI/CD – reduce queues, focus on cost of delay
This slide is really Day 2 of Culture, Process, Automation / Tech.
How would you define Value Stream Management?
Work development team are doing is aligned to business goals
Provide data to encourage teams to be responsible for their own value streams
Take an idea an move it from backlog to production
Better understand the handoffs and where work gets held up
No longer are bottlenecks simply in lack of automation
Teams want to identify the new bottlenecks
Velocity’s breadth of DevOps Data provides tremendous opportunities for machine learning. Some possibilities we are considering…
Identify areas of the code base that are most problematic and candidates for refactoring – based on production incident data, change histories, defect histories, static analysis…
Flag backlog items most valuable to work on based on past deliveries across the organization
Release risk analysis: Predict number of Sev 1 / Sev 2 incidents for a release (change history, developers involved, test results and coverage, etc
Suggest process or tooling changes: identify teams that have part of their delivery slower than other parts of the organization.
(Value Tracking) Can you tell me with certainty what the last package released in production contains? Probably??
(Cycle time) Can you tell me how long it took from when the idea was capture and when the package was actually deployed to your production server? Maybe, how long would it take to compute that? How many tools would you have to consult?
(Productivity Trends) Can you tell me how many bugs your team crushed last week and actually delivered to customers? Done versus deployed to production?
(Visibility Security) Can you tell me what team across your organisation have not done security scans in the last 30 days?
(Quality Trends) Can you show me that adding resources to your team had a positive impact on the quantity or quality of the delivery? Or that increasing the speed did not mean sacrificing quality??
(Business Result) That business initiative that will transform your organisation, where are we in the process of delivering that value, is it in planning, development, QA, some of it already in production?
(Business Productivity / Predictability) Can you tell me today how long it will take your team to deliver that brand new feature that will revolutionize the market?
Showing data sources, putting into a database where key things are happening – rest APIs, access control, cool views into data, keeping raw records, normalizing data so we can gain insights
From bottom up, showing what velocity does
Because we have those 3 things, we're able to give you those different views at the top
DevOps is thought of as being automation driven – that's great, but you need data backing that automation. Should we go to production should be backed by quality metrics and data.