Dave Bales

This presentation aims to raise awareness that default Product Ownership (that uses only ordering and prioritising PBI’s) is not enough to be successful.  A higher level of consciousness is required to appreciate the challenges and dynamics of the work at hand. Devising evolutionary strategies to cater for the undercurrents, changing landscape and the opposing dynamics in the product and its backlog, may help to tip the balance in favour of being more successful.

Project dynamics can include:

  • Releasing a new insurance app to millenials on a smartphone platform.  The challenge with this is that more customer testing and an exploratory approach of how milenials think will be required, hence each sprint goal may include working toward a customer testing objective;
  • A compliance risk project where compliance objectives are static.  How those objectives are satisfied is variable, hence an evolving strategy to use an iterative approach is to be considered.  The first iteration would be to neutralise the compliance risk, starting with a manual process. Successive iterations would then be run by automating and adding more value;
  • An integration risk project, where a central framework has to integrate with several other systems. An evolving strategy would focus on setting sprint goals to achieve integration, as well as regression testing objectives to neutralise the integration risk early
David Bales