The Hybrid: The best of both worlds?

This post really is not an advert. Trust me. However, sometime ago I went into Halfords and asked for their expert advice. Given the type of terrain I would likely ride on (roads and moderately off-road) the expert recommended to me the Boardman Hybrid Bike Pro.


Features and Benefits:-

I recall the chap saying that “You get a lot of bike for your cash” and then highlighted the price tag which provided some small change from £900! #happydays

The website informs us that the hybrid is “the perfect bike for the most discerning of commuters. The superlight alloy frame is coupled with an aerodynamically formed full carbon fork to provide accurate and nimble steering. Complete with Shimano’s excellent 20 speed 105 gearing, beautiful crafted Shimano Deore Hydraulic disc brakes and the superb Shimano RX05 wheelset”.

It then highlights that “this bike is the perfect blend of comfort, performance and function, making it ideal for navigating the busiest of city streets”. 

It seems to me that this bike seeks to address the ‘optimal sweet-spot’ between three key criteria:comfort, performance and function.

This got me thinking whether there are any lessons to be learned for Agile transformational programmes; and more especially, in large, complex organisations?

Using a little of my imagination I think we can apply these three critical criteria in these kinds of ways:

  • comfort. This seems to me to map neatly to the UX role who ensure that the End Users have a first-class experience of any software solution that enhances their day-to-day jobs and more especially for ‘front-line’ jobs so as to enhance productivity, efficient and ergonomic outcomes.
  • performance. Agile- whether Scrum or Kanban for example will look to ensure that any software has high quality. There is now a well established evidence-base of what business and organisational contexts Agile works incredibly well in and when it is less effective.
  • and function. Enterprise-wide Architects add value in this ‘space’ particularly well. Having a well designed Architecture ensures an optimal fit in and between different projects and solutions.

It seems to me that having a transformational programme may well benefit from the hybrid metaphor for large-scale, complex organisations.

Take care, Jason.

whatisbp Association_for_Project_Management_(logo)

Minimum Viable Product: Ignoring the Call of the Sirens

One of the most fascinating stages for any Agile product is working through what constitutes the Minimum Viable Product (MVP). 

It seems to me that all three signifiers, or words, have equal weight or importance. The process determines or ‘locks in’ at least for a point in time that which makes something of sufficient substance that we can recognise it as a ‘product’ per se.  Next the analysis concerns itself with what the minimum number of features the product has so that from a market perspective we can successfully have a product to release or take it to the market as part of a new product launch. Finally, the second term the viability becomes critical in at least three ways:-

  1. In terms of our market segmentation strategy and market research this meets or fulfills our customer demographic needs
  2. If for an internal customer, or business unit, then in a similar way- the product needs to meet a similar set of needs- at least for the point in time for the Release date (as by definition later releases will meet future needs that may well change, emerge or become redundant as a function of time)
  3. Finally, viability has a keen association with the business case. The latter will normally have the ‘golden triangle’ of classic project management tools and include analysis around time, quality and costs.

What can we learn from depth psychology? I’ve pondered this recently and think that there are some lessons from the Odyssey (Homer) and in particular the episode with the gorgeous Sirens.


You may recall that the poem centres around the hero Odysseus and his long-winded adventure and journey home after the battle of Troy. On their way home his skilled and brave crew are faced with mortal danger in the form of beautiful women called the Sirens. The Sirens lure sailors to their deaths by a fatal combination of the most enchanting, beautiful and hypnotic songs as well as their gorgeous beauty. They were seen as daughters of the god Achelous.

By their physical beauty, and melodious songs they, if successful, get the ship to change direction and shipwreck on the rocky nearby coasts. Thus, to this day, the Siren song refers to an appeal that is hard to resist but that, if heeded, will lead to a poor or bad conclusion. It is it seems an ‘irresistible distraction’.

Thankfully in our myth, our hero was fore-warned of the Siren call and consequently (and very wisely) strapped himself to the mast of his ship. He then ordered his crew to use wax in their ears so that they could not be seduced by the Sirens! No easy task! To be fair, the sailors obeyed and as we now know by looking back that this was a set of wise choices in such demanding circumstances! Thankfully, it all worked! and they were able to sail on despite the ‘distractions’.

This speaks to me in the following three ways:-

  1. After we have completed our market research we must be as wise as Odysseus and keep our eyes fixed on our objective asking carefully and wisely if each feature meets the litmus test of all three signifiers in the MVP trinity
  2. Next, we must paradoxically ‘resist the irresistible‘ and this ensure that we keep pace with our own progress and be careful not to be distracted by any external, or at times, internal ‘Siren call’s’ even though they may be beautiful features
  3. Lastly, as Scrum Masters we need to work alongside the Product Owner, in particular, and if need be ‘fasten him to the mast‘ and so ensure the safety of the project team.

Take care Jason