BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Product Owner Content on InfoQ

  • Product Owner Raison d'Etre in an Agile Team

    Companies may claim they're implementing Scrum, but is the claim really valid? Do they uphold the philosophy of Scrum? It turns out it's not, as a lot of companies are still practicing a distorted version of Scrum. Part of the common dysfunction is the misunderstood role of the product owner: a role essential to success with Scrum. What then is the actual job of a good product owner?

  • Q&A on The Great ScrumMaster

    In The Great ScrumMaster Zuzana Šochová explores the ScrumMaster role and provides solutions for dealing with everyday and difficult situations. She describes the #ScrumMasterWay, a concept which defines three levels of operation of ScrumMasters.

  • Q&A on Analysis Techniques for Product Owners Live Lessons

    In the Analysis Techniques for Product Owners video lessons, Kent J McDonald shared a set of techniques that will help you build and maintain a shared understanding and put outcome of a project before the output. You'll learn, amongst other topics, how to best assess the need to be satisfied by a project and how to build and properly communicate the solution to be delivered

  • Product Development Mechanisms

    Steve Andrews discuses the need to empower self-managing teams to stay focused on delivering high-quality solutions using mechanisms like tenets and exit criteria.

  • Q&A with Roman Pichler about Strategize

    The book Strategize by Roman Pichler provides practices, advice, and examples for product strategy and roadmapping that you can use to create successful products. InfoQ interviewed Pichler about applying product strategy and roadmapping with agile, innovation in product strategy, eliminating features when defining products, different kinds of roadmaps, and measurements for product management.

  • Now or Never: the Ultimate Strategy for Handling Defects

    How do you handle a long list of defects in your project? You don't. If it is not worth fixing a defect right now, it’s not likely that we will find the time to do it later. Also, it becomes more and more difficult over time to correct the defect, so it is cheaper to solve it now. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them.

  • Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"

    Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.

  • Characteristics of a Great Scrum Team

    This article explores 'What makes a great Scrum team?' by offering detailed descriptions of the characteristics and skills needed in the Scrum roles of Product Owner, Scrum Master and Development Team.

  • Connect Agile Teams to Organizational Hierarchy: A Sociocratic Solution

    Many agile teams suffer from the mismatch of agile and organizational leadership with the latter being reflected by the organizational hierarchy. This article suggests using sociocracy as a solution that leaves the hierarchies in place yet still allows teams to act in an agile way.

  • The Hierarchy of Needs

    What may be valuable to customers whom you do not even know in an unstructured and completely individualized market? This article suggests prioritizing your backlog using an enhanced quality model based on Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix and give those features highest priority in your backlog.

  • Using Large-Scale Scrum (LeSS) with Feature Teams to Ship Your Product Every Sprint

    An interview with Larman about LeSS and what makes it different from other scaling frameworks and using empirical process control to increase organizational agility. Larman also explained how organizations can work with feature teams, and gave examples of how teams and stakeholders can be in direct contact with their customers and users and can work together to ship their product every sprint.

  • How Agile Has Changed Test Management

    Agile methods have many traditional test management activities built into them. With desired agile team traits like self-organising, role blurring and skill diversification, the nature of test management is changing. We have to question whether the role of Test Manager should exist in effective agile organisations and how the activities which have long made up the role are divested?

BT