Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Product Management Content on InfoQ

  • IDEA: a Framework for Nurturing a Culture of Continuous Experimentation

    For a team to be agile, they need a culture that allows them to learn, unlearn, and relearn. This article explains how teams can foster such a culture, navigate through the complexities of modern development environments and harness agility to deliver software quickly that fits the needs of users and business sponsors. It describes a framework to explore, plan, implement and evaluate ideas.

  • Hard-Won Lessons from the Trenches: Failure Modes of Platform Engineering — and How to Avoid Them

    Platform Engineering is a hot topic with many orgs hoping to reap the benefits. However, it is easy to go astray. This article reviews the common pitfalls of building a platform and how to avoid them.

  • Bringing a Product Mindset into DevOps

    To be successful, organisations need two things: products and services their customers find valuable, and the ability to deliver these products and services well. This article shows why we must design, implement and operate our delivery pipelines (the means of turning ideas into products in the hands of users) as we would any other product or service: by adding a “product mindset".

  • How to Run Your Product Department Like a Coach

    Having found what I thought was my calling as an agile coach, I took the tough decision to move sideways into Product Management in the hopes of using what I’d learned to one day run my own department. I believed that coming from coaching would allow me to see things others could not and create something special. Time will tell if I have succeeded. This is the story of where I am so far.

  • Installing a Robust Dev Culture for the Micro-app Environment

    While consumer-facing apps have increased, a bigger increase is taking place within enterprises, with so-called “micro-apps” that are used to create customized solutions. Continuous release environments place developers in a state of regimented activity, leaving insufficient time for micro-app projects. Here's how companies can create a cultural shift that incorporates micro-app development.

  • 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.

  • Seven Key Insights of Product Management

    What a product manager does and how they do it seems like a perennial question, an ongoing discussion, often ending in debate. This changes depending on factors such as the size and culture of the company, the industry or sector, the business model, where the product is in its lifecycle, and the type of product. What doesn’t change is they’re always thinking about customer and business needs.

  • 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.

  • The Complexity of Product Management and Product Ownership

    Doug Talbot discusses the confusion surrounding Product Ownership / Product Management. He provides some advice on tackling the complexity of creating your own contextualised and personalised product value stream for your organisation or team and using systems thinking and Cynefin for complexity.

  • How to Build a Strong Beta Testers Community

    It is important to involve the real users at the early stages of your development cycle. A strong beta testers community not only improves your product, but also provides context, pain points and ideas while increasing loyalty and engagement. This article offers tips and tricks on how to build a beta testers program and a process of supporting the program with a modest allotment.

  • Q&A on the Book Retrospectives for Everyone

    The book Retrospectives for Everyone by Madhavi Ledalla explains how metaphors can be used to foster reflection and result in actions in agile retrospectives. The book provides examples of metaphors that can for instance be used to nurture teamwork, manage change, focus on objectives and personal reflection, and also provides recommendations for facilitating retrospectives beyond a single team.

  • Agile Initiative Planning with Roadmaps

    Most “agile” initiatives fail to meet their value, time and budget goals despite spending ½ their time and 1⁄3 of their budget designing and planning upfront. Agile Initiative Roadmaps add product, project, architecture and UX planning to initiatives so that you can take a longer view with a small amount of time and effort, which means that you can deliver benefits much sooner at a lower cost.