In Agile frameworks, the Product Owner is the person responsible for maximizing value, for example through prioritisation of development work, engaging stakeholders; and learning from the market and customers.  Product Owners formulate a crystal-clearvision that guides product development, involve key stakeholders, makes use of the possibilities afforded by new technologies; and develop features to target new audiences. Ideally, Product Owners act as entrepreneurs within their organisation and have the mandate to make tough decisions. However, the reality of Agile practices shows that organisations can obstruct their Product Owners when it comes to acting in such an entrepreneurial manner.

Dealing with organisational contexts is crucial in making the most of the Product Owner role and of prime importance in facilitating a successful journey towards agility.

Product Owner scenarios

We typically encounter the following five scenarios that impede the entrepreneurship of the Product Owner:

1. Death by hierarchy

The organisation features strict separations of departments. ‘Business’ and ‘IT’ fail to communicate and collaborate efficiently. A transition to a new business model and/or Agile framework may have been enforced by decree, sometimes to the chagrin of everyone involved. Rather than being single points of authority, Product Owners run the risk of being go-betweens: they’re bound by procedural and administrative chains, forming yet another layer in the communication between various employees and departments.

In such cases, it’s advisable to facilitate and enhance communication among employees in ways that cross responsibilities and forms of expertise. Product Owners need to acquire the mandate to act more independently by dealing with organisational impediments. In collaboration with a dedicated Scrum Master, an entrepreneurial Product Owner may tackle death by hierarchy by making changes on a small level, there by acquiring authority to make decisions and eventually earn more widespread appreciation for Agile ways of working.

2. Stalemate

An organisation struggles to become successful. Revenue may be low and competitors are on the rise. There are endless discussions about what to do next, yet those involved never seem to agree. Resources that should be combined for maximum effect are fragmented, compromising the organisation’s ability to make an impact.

Entrepreneurial Product Owners can optimise the process of learning from the market and potential customers, for example by developing an MVP that will solicit feedback from target audiences. The MVP allows feedback from the market to be incorporated into product development, with the Product Owner acting as a key ambassador for stakeholder involvement.

3. Business model paralysis

An organisation may be learning from the market and internal discussions, yet fails to use these interests to its advantage, e.g. by seriously reconsidering their business model and pivoting towards a new approach. Vested interests, long-term contracts, or a more general fear of change may prevent any serious change to the erstwhile successful business model. However, upon closer look, the foundations of this business model appear to be slowly crumbling.

Product Owners should beable to have a disruptive impact by testing assumptions, pointing out blind spots in the organisation’s activities, and questioning the value of work produced by teams within the organisation. Breaking through this organisational stasis requires a Product Owner working with different stakeholders, both internally and externally, and someone willing to verify and calibrate business models through market research, the release of an MVP, stakeholder consultation and management, etc.

4. Wet behind the ears

The organisation might be relatively new to Agile frameworks and may have yet to persuade every employee in the organisation that agility is important. As a result, some employees may see Agile as an IT-related matter that primarily concerns frequent releases and flexibility so that customers are being kept satisfied. It may seem that agility doesn’t affect everyone, and most departments can safely stay on the beaten path and continue according to the old ways.

Agile concerns the entire organisation and never a singled-out department like ‘IT’. Product Owners should overcome boundaries between departments and domains of expertise to truly intertwine business with IT. Strategically aligning project and program management with Agile’s product-oriented mindset can ensure involvement of project, product, and program managers, who may feel left out due to the transition towards agility.

5. Greed is good

Product Owners may be ruthless in pursuing their own personal interests and may operate under the adage “greed is good”. The organisation is put in a vulnerable position by the Product Owner, who may damage the creation of value due to the pursue of exclusively personal interests. Even the transition towards agility within the organisation can be negatively affected.

Truly being an entrepreneur means responding to the outside by being open to it. Pursuing personal interests that aren’t aligned with the organisation’s interest is more like pillaging.

Conclusion: best practices

Embarking on the journey towards increased agility can be difficult. We advise the following best practices regarding Product Ownership to help organisations become responsive and prosperous:

  • Avoid miscasting: if transitions to Agile frameworks aren’t carried out with care, those fulfilling a new role (such as the role of the Product Owner) may not have the professional and personal traits required.
  • Hire an external Product Owner: organisations that have the characteristics of scenarios 1 (‘Death by hierarchy’) and 4 (‘Wet behind the ears’) can benefit from an external Product Owner. He/she can help to facilitate a transition to agility by functioning as a relatively independent arbiter to build consensus and coaching other Product Owners within the organisation.
  • Form a crystal-clear product vision and be willing to rigorously test its viability, for example by means of an MVP.
  • Form interdisciplinary, flexible, creative, and high-performing teams who can make a difference.
  • Find out what stakeholders have the mandate to make decisions and involve them using techniques that foster dialogue. Thus, the sphere of influence of the Product Owner expands.
  • Co-create product backlog items and sprint goals using input from all layers in the organisation.
  • Enable and sustain collaboration between Scrum Teams and internal/external stakeholders.
  • Fail again, fail better: accept the fact that releasing early and often is the gateway to success, even though this may at times be painful.