InfoQ Homepage Product Development Content on InfoQ
-
How Tech-Enabled Networks of Software Teams Work
To maintain agility at scale, software teams can use technological and organizational solutions to reduce dependencies and work autonomously. According to Fabrice Bernhard, collaboration technology can be leveraged to create a distributed network of teams. To empower their teams, leaders can support them with a systematic problem-solving culture aimed at delivering good products to customers.
-
How Continuous Discovery Helps Software Teams to Take Product Decisions
Continuous discovery for product development is regular research that involves the entire software product team, and that can actively inform product decisions. Equating continuous discovery to weekly conversations with one or more customers can be misleading. Combining quantitative and qualitative research methods can help software teams gather data and understand what is behind the data.
-
Sustainable Product Development Using Agile and Value Stream Mapping
Sustainable product development can be done by combining agile with concepts from the circular economy in our daily work. Value stream mapping can be extended to incorporate circular economy principles to optimize the flow of materials, information, and energy usage.
-
The Challenges of AI Product Development
Developing artificial intelligence (AI) products involves creating models and feeding data to train them, testing the models, and deploying them. Software engineers can support the adoption of AI and machine learning (ML) in companies by building an understanding of the technologies, encouraging experimentation, and ensuring compliance with regulations and ethical standards.
-
Building Cyber-Physical Systems with Agile: Learnings from QCon New York
In her QCon New York 2023 talk Success Patterns for building Cyber-Physical Systems with Agile, Robin Yeman explored how we can use agile practices at scale for large initiatives with multiple teams, building cyber-physical safety-critical systems with a scope that includes software, firmware, and hardware development.
-
Unlocking Software Engineering Potential for Better Products
Becoming an empowered team means solving problems rather than shipping features. Empowering software engineers and involving them early in discovery work can result in better products. If we measure outcomes rather than output, we can also hold teams accountable. Supporting software engineers to empower them means trusting them and getting out of their way.
-
Sustainability for Software Companies: Reducing Impact by Deciding What Not to Do
Small and medium-sized companies can contribute to sustainability with emissions reduction, mental health offerings and inclusion. To support sustainability, software engineers can think about “what not to do” to reduce complexity and make solutions smaller, resulting in a smaller carbon footprint.
-
Getting Feedback When Your Colleagues Are Also Your Customers
Getting and using feedback from colleagues who are also customers using your product can improve the quality of the product and help to improve the way of working. In this situation, it’s easier to receive feedback, but you can get overloaded by it.
-
Measuring the Environmental Impact of Software and Cloud Services
Software has an influence on the limitation of the service life or the increased energy consumption. It’s possible to measure the environmental impacts that are caused by cloud services. The design of the software architecture determines how much hardware and electrical power is required. Software can be economical or wasteful with hardware resources.
-
Migrating a Monolith towards Microservices with the Strangler Fig Pattern
ScholarPack has migrated away from its monolith backend using a Strangler Fig pattern. They applied incremental development and continuous delivery to target customers’ needs, in the meanwhile strangling their monolith.
-
Taking Advantage of Attitudes for Building Products
Attitudes like cynicism, skepticism and optimism impact how we develop products. Being aware of attitude matters, as it can block development or lead to building the wrong product. InfoQ interviewed Gwen Diagram about cynicism, skepticism, and optimism, the impact developers can have, and dealing with attitudes in teams.
-
Camille Fournier on Effectively Managing Internal Platform Teams
Camille Fournier, managing director, head of platform engineering for Two Sigma, recently shared her learnings from managing internal platform engineering teams. Two of the key challenges she shares are the smaller size of the customer base and the challenge in understanding how your customers will use your product.
-
Effective Product Development for the 2020s
Ram Sivasankaran examined the market failures of Google’s social media attempts, Kodak and Blockbusters. His analysis identified slow adoption of technology, a lack of data-driven decision-making and low customer focus. Martin Reeves and Bill Lydon have also both written about a more competitive market in the 2020s, requiring the adoption of product strategies which embrace emergent technologies.
-
Becoming Outcome Focused: Q&A with Jeff Patton
We need to become focused on outcomes and adapt our way of thinking and our processes to continuously release small changes to our products and services, argued Jeff Patton in the closing keynote at the Agile Greece Summit 2019.
-
Lessons Learned from Innovating at Google: Frame the Problem, Use Data, and Define the MVP
The truly great, innovative, useful ideas come mostly from two sources: your target users, and people working in the organization - not necessarily those with a "product manager" hat. Experimentation can help us to materialize ideas into actual products and technology. Framing the problem, using data, and defining the MVP can help us to increase the chance of success in innovation.