BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Product Management Content on InfoQ

  • Adoption of SAFe at TomTom

    InfoQ interviewed Hans Aerts, vice president software development and agile coach at TomTom, about why they decided to adopt SAFe and how it was introduced and used to simplify the organizational structure and stop doing projects, why they focus on throughput rather than output, how they modified SAFe for Custom Systems, and what using SAFe has brought TomTom.

  • Q&A with Gil Zilberfeld on Agile Product Planning and Management

    InfoQ did an interview with Gil Zilberfeld about better ways to do product planning and tracking, his thoughts about #noestimates, including value in product planning discussions, and how to improve decision making in product development.

  • Using the "Worse is Better" Concept with Agile and Lean

    Less functionality can make a better product according to the “Worse is Better” concept described 25 years ago by Richard P. Gabriel. According to Kevlin Henney and Frank Buschmann we can learn from the worse is better concept for development and architecture with agile and lean.

  • Product Roadmap Creation Using Different Views

    Scott Sehlhorst, product management and strategy consultant describes two views of the product roadmap.

  • Knowing if You Are Building the Right Product

    Developing and delivering products which customers don’t want and for which there is no market can be costly. Agile can help you to efficiently develop products, but you need to know what to build. How can you find out which products your customers need?

  • Using a Definition of Ready

    Many teams use the Definition of Done to check if a user story is finished and the product is ready to be delivered. But what about the user stories that a team receives from their product owner? Teams can check the quality of the user stories using a Definition of Ready.

  • Rocket to Mars: A Sprint Planning Game

    “Many team and their product owners believe that the team's unique job is to deliver more and more story points, but we consider this to be a complete misunderstanding of the relation between the team and the product owner” said Damien Thouvenin and Pierrick Revol. They ran a sprint planning game on investing time to produce stories, investigate issues, reduce technical debt, or do training.

  • Is Getting Rid of All Projects a Good Idea?

    At the XP Days Benelux conference, Paul Kuijten did a session called "kill all projects" where he questioned if getting rid of all projects could be a good idea. InfoQ did an interview with Paul about project management practices that can be valuable for agile, and the funding of product development.

  • Different Approaches for Product Backlog Grooming

    The purpose of backlog grooming is to keep the product backlog up to date and clean. Different approaches are used by product owners and teams to do this.

  • "February Revolution" Aims to Focus Software Delivery on Business Outcomes

    In February 2013 a group of authors, speakers, consultants and practitioners met to identify the common elements in their approaches to focusing software delivery on business outcomes. The group identified some underlying principles and practical steps that organisations and teams can take to help ensure the products they "build the right product" to maximize business value.

  • Minimum Viable Products for Enterprises

    Enterprise software startups use a minimum viable product (MVP) to learn about customers with limited effort and money. How can organizations deploy lean startup principles to develop a viable product for their stakeholders?

  • Too Much Technology?

    As technologists we often never question how technology is affecting us and our world. This interview with Eric Brende presents an a different view on progress, innovation and technology.

  • Individual Yield

    Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.

  • Product Owner Patterns

    The Product Owner role is regularly debated and discussed. The challenges of the role and the responsabilities encompased by it are a frequent source of discussion and advice. Recently there has been discussion about common aspects of the role and the important activities a product owner needs to ensure happen on an agile project, and the difference between the product owner and product manager

BT