InfoQ Homepage Customers & Requirements Content on InfoQ
-
/articles/user-story-conversation/en/smallimage/user-story-a-placeholder-for-a-conversation-small-1695641308270.jpg)
User Story: a Placeholder for a Conversation
User stories are meant to be a placeholder for a conversation. This article dives into the differences between user stories and tickets, where stories came from and how recent trends are moving us away from conversations. It shows the impact this is having on product development and easy ways to improve collaboration through conversation and writing better stories.
-
/articles/tech-stack-not-meeting-needs/en/smallimage/your-tech-stack-doesnt-do-what-everyone-needs-it-to-small-1674818401120.jpg)
Your Tech Stack Doesn’t Do What Everyone Needs It To. What Next?
Stack extensibility is an essential trait of well-designed IT ecosystems. Low-code BPA (Business Process Automation) has advantages that puts it at the forefront of approaches to stack extensibility. Learn how low-code software increases process resiliency by empowering business teams with an easy-to-use, easy-to-understand and, most of all, IT-sanctioned set of tools.
-
/articles/metrics-quality-software/en/smallimage/finding-adequate-metrics-for-process-quality-in-software-development-small-1673953064694.jpg)
Finding Adequate Metrics for Outer, Inner, and Process Quality in Software Development
Implementing a feature can be measured. Quality is harder to measure. This article explores how to balance improving quality and adding new features. It dives into different domains of quality: Outer quality which is owned by the product people (e.g. product owners, testers), inner quality owned by the developers, and process quality owned by managers.
-
/articles/monitor-digital-experience-feature-effectiveness/en/smallimage/monitoring-digital-experience-to-determine-feature-effectiveness-small-1666951981148.jpg)
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.
-
/articles/problem-reframing-method/en/smallimage/logo-1646680413270.jpg)
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.
-
/articles/technology-change-human/en/smallimage/logo-1621267095641.jpg)
Keeping Technology Change Human
When we are at the forefront of so much change, it's easy to forget that other people around us find change more challenging. This article is a reminder to look beyond the code and processes, to consider how tech team actions can affect our users in emotional ways. It seeks to establish a few ways of thinking to help bring others along with us when working through technology change.
-
/articles/whole-product-technology-adoption/en/smallimage/applying-whole-product-model-small-1620984743493.jpg)
Applying the “Whole Product Model” to the “Technology Adoption Life Cycle”
In order to develop products customer love, product managers need to truly understand how their “whole product” delivers value and when to address which customer segment. Two models that are very powerful when applied together, and that a product manager can use to develop extraordinary products, are The Whole Product Model and The Technology Adoption Life Cycle.
-
/articles/flow-system-customer-feedback/en/smallimage/Turner FLOW SYSTEM-s-1616790623151.jpg)
The Flow System: Getting Fast Customer Feedback and Managing Flow
The Flow System elevates Lean Thinking in an age of complexity by combining complexity thinking, distributed leadership, and team science into the Triple Helix of Flow, which organizations can use to become more innovative, adaptive, and resilient. This first article explores the importance of quality, getting fast feedback from customers, the concept of flow, and The Flow System.
-
/articles/agile-demo-feedback/en/smallimage/logo-1615911629760.jpg)
Put the Feedback back into “Demo & Feedback”
As agilists, we know the importance of showing our work and getting feedback as early as we possibly can. That feedback guides what we do next. To get what you need to meet the desires of your stakeholders, this article looks at the demo and the feedback part of that session and provides suggestions for creating amazing demo & feedback sessions.
-
/articles/agile-survive-change/en/smallimage/agile-survive-change-s-1602517443986.jpeg)
Only the Agile Survive in Today’s Ever-Changing Business Environment
Today's business environments are changing more rapidly than ever before, with major shifts impacting all departments. Ongoing success requires the agility to quickly capitalize on opportunities, using technology to evolve and stay ahead of the game in employee retention, customer satisfaction, governance and compliance. Indeed, your ability to act swiftly can truly make or break your company.
-
/articles/book-review-further-faster/en/smallimage/FURTHER-FASTER-s-1596634806313.jpg)
Q&A on the Book Further, Faster
Businesses that thrive over the long term can focus on just a few things that truly matter to their teams and core customers. The book Further, Faster by Bill Flynn provides ideas for business leaders to build teams, create a strategy to stay close to customers, and manage a company’s growth with cash as the primary metric.
-
/articles/application-models-software/en/smallimage/Application Models as Working Software-logo-1581510283123.jpg)
Application Models as Working Software
Discusses using an application model in an iterative time-bounded development approach. Employ user flows to create easily comprehended stories that contain sufficient detail. Get closer involvement from UX design and product owners to create solutions prior to the first coding iteration. Incorporate as-built decisions back into the model to ensure its relevance in an ongoing product lifecycle.