InfoQ Homepage Business Value Content on InfoQ
-
Why Developers and Staff+ Engineers Should Get Involved in Open-Source Collaborative Development
Over the last 30 years, the world has become connected and digital. Open source is how we do modern software development, stitching together downloaded open-source libraries, frameworks, and other code to create new applications or functionality. This is why every developer and senior staff+ roles need to know what open source is and how it works.
-
Step One to Successfully Building Your Platform: Building It Together
You may feel that investing in an internal platform is a win, but the business may need more convincing. This article covers how to frame your case in a way that the business can understand and support.
-
How to Have More Effective Conversations with Business Stakeholders About Software Architecture
Technical leaders must be able to communicate with business stakeholders to effectively design software solutions that meet the business needs and stay within an established cost threshold. Making architectural decisions requires understanding the desired quality attributes that will affect trade-off discussions between technical and non-technical stakeholders.
-
Are Your “Value Streams” Keeping You Stuck in the Past?
The essence of business agility is being able to respond quickly and systematically to feedback. As a means of achieving business agility, value stream management falls short, and ends up being not very different from what organizations have done for a long time: using program management practices to coordinate work across different teams in a large organization.
-
Are They Really Using It? Monitoring Digital Experience to Determine Feature Effectiveness
This article reflects on the challenges of determining user experience and effectiveness and how modern techniques such as Real User Monitoring and Application Performance Monitoring can determine the true effectiveness of features. It includes stories from banking to show which measures can help agile teams determine not only if features are being used, but diagnose other common issues too.
-
Code Red: the Business Impact of Code Quality
Everyone in the software industry “knows” that code quality is important, yet we never had any data or numbers to prove it. In this article, we explore the impact by diving into recent research on code quality. With twice the development speed, 15 times fewer bugs, and a significant reduction of uncertainty in completion times, the business advantage of code quality is unmistakably clear.
-
Accessing Agile Games as a Tool in Transformation and Change
This article puts the usage of Agile Games into a broader business context and introduces the steps needed to make any game a verifiable contribution to a given business objective. As “business” is a wide area of topics to be addressed, the article focuses on accessing Agile Games as a tool used within transformation and change. It provides an example that was taken from this area.
-
DevOps at Schneider: a Meaningful Journey of Engaging People into Change
Adopting DevOps at Schneider started with building a case for change. Tech people were engaged into change by organizing learning and collaboration sessions and getting feedback from the front lines. Change is hard and without leadership support, dedicated time for developers to really digest it and continual reinforcement and conversation, it will be challenging to be successful.
-
Continuous Portfolio Management as a Contributor for Achieving Highly-Aligned, Loosely-Coupled Teams
There is a business need for fast software delivery in order to frequently test business hypotheses and drive development based on the resulting feedback. Organizations need to rapidly decide on what to build next, using a short feedback loop that greatly reduces the risk of running on untested assumptions for too long. This article explores a journey towards continuous portfolio management.
-
Using the Problem Reframing Method to Build Innovative Solutions
Building products that customers love relies heavily on the problem space: how well you know your audience and how clear are the pain points and main problems your users are facing. This means that the solution to a problem depends on how we frame the problem. This article provides different practices and tools on how to apply problem reframing underpinned by a real case study.
-
Talking Like a Suit - Communicating the Importance of Engineering Work in Business Terms
This article explores how to construct engineering work as a story, including clearly presenting a problem, offering a solution, and showing the business a path to success that solves their problem and avoids failure. By presenting your case in this way, you significantly increase your chances of getting these engineering problems addressed, while also becoming a better partner for the business.
-
How the Financial Times Approaches Engineering Enablement
Companies need teams working on infrastructure, tooling and platforms; the way they work has to change so that they do not become a bottleneck. These teams need to be about enabling product teams to deliver business value. Investment in this area pays off as it speeds up many other teams and allows product-team engineers to focus on solving business problems that provide value to the organisation.