Comprehensive software reviews to make better IT decisions
Bridge the Business-IT Chasm With BizDevOps
DevOps took the industry by storm. Successful organizations see significant improvements in their software delivery process and product quality with automated and collaborative IT practices:
- 61% of highly mature DevOps organizations with fully integrated security practices were able to deploy on demand (Puppet, CircleCI, and Splunk, 2019).
- Compared against low DevOps performers, elite performers have 208 times more frequent code deployments, 106 times faster lead time from commit to deploy, 2,604 times faster recovery from incidents, and seven times lower change failure rate (Dora and Google, 2019).
While the prospective DevOps benefits are enticing, speed and quality are not everything. The question is whether the latest products and changes deliver business value. Enter BizDevOps.
What is BizDevOps?
Unlike Agile, the industry does not have a consensus of what BizDevOps (or even DevOps) means or what is required to be BizDevOps (e.g. manifesto). Info-Tech proposes that BizDevOps is an operational philosophy that seeks to promote an improved relationship among development, operations, and lines of business (LOBs) by breaking down barriers, aligning all groups to a common vision, and becoming jointly accountable for customer value delivery.
How Do I Implement BizDevOps?
Stakeholders are swayed by the praise they hear and see from those who have successfully implemented or provide BizDevOps practices, and they want to invest. However, BizDevOps brings significant organizational, process, and technical changes that the business and IT are often not prepared or willing to adopt. Tools alone will not solve BizDevOps implementation challenges despite the urging of certain industry perspectives and vendors.
Delivery tool vendors (such as Blueprint Software Systems) and delivery practice thought leaders (such as Disciplined Agile) attempt to clarify BizDevOps as a set of collaborative activities and/or as an integrated pipeline, but they stop short of providing consumable and achievable implementation guidance. The overwhelming and intimidating list of suggested initiatives (or lack thereof) create a perceived barrier to entry and confusion about where to start.
Info-Tech recognizes that the crux of successful BizDevOps implementation is centered on the strategic adoption and optimization of five key delivery capabilities, which serve as a launching point for other delivery and collaboration practices:
- Good requirements and roadmap – clear business rationale of the problem IT is requested to solve, which is then used to commit to an achievable delivery plan.
- Increased delivery frequency – short release iterations to enable quick value generation and early product verification and validation for future enhancements.
- Formal and continuous engagements of all participants – bringing business and IT together at the most opportune times to improve delivery effectiveness using the appropriate method for the team, application, and type of work (e.g. Scrum, Kanban, Hybrid).
- High fidelity environments – non-production environments (e.g. development, testing, staging) mirror production in order to generate and test features and changes against realistic conditions.
- Post-production support – continuous monitoring of the production environment in order to proactively address risky areas and identify application and system optimization opportunities. Work closely with support staff and end users to expediate the feedback loop.
With the right foundation, leadership, support, and willingness to change, organizations will begin to see higher-quality products delivered with satisfactory throughput. This reputation will strengthen the business-IT relationship and shift IT’s role from a trusted operator to a trusted partner.
Want to Know More?
Custom application development is a strategic differentiator in the digital economy. Organizations need to make good decisions on how to insource or outsource that development or they risk bad software … and worse results.
The concept of building a software factory has increased in popularity with the drive to build digital platforms, products, and services. It is also a major transformation from traditional, hands-on-keyboards software development practices in and of itself. Before you build your software factory make sure you have a firm foundation for success!
COVID-19 has forced software companies and their suppliers to refocus efforts around prioritizing systems and workflows that are nearly 100% digital in nature. As a result, Info-Tech has observed the quick emergence of six market themes that are highly relevant post COVID-19. This note series will profile key vendors and how they fit into the post-COVID-19 world.
COVID-19 has forced software companies and their suppliers to refocus efforts around prioritizing systems and workflows that are nearly 100% digital in nature. As a result, Info-Tech has observed the quick emergence of six market themes that are highly relevant after COVID-19. This note series will profile key vendors and how they fit into the post-COVID-19 world.
IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.
Is it true that everything that can go wrong will go wrong? Don’t bet on it to not.
Test data management tools offer you the ability to provision, mask, and govern the access and use of your test data, alleviating these manual, laborious and error-prone tasks from your testing, operations, and DBA teams.
While Microsoft is not a prominent player in the RPA space now with its Power Automate solution, compared to Blue Prism, UiPath, and Automate Anywhere, its latest acquisition of Softomotive, maker of WinAutomation, demonstrates Microsoft’s dedication to mature and expand its RPA offerings.
When trying to implement Agile as a defined process, Scrum turned BAs or other roles into order takers with the title “product owner.” This undermines the entire value proposition of product management.