16 December, 2024

How Good is HYPERID? A Hybrid for Project Management Methodology


HYPERID claims to offer a true hybrid project management methodology. Does it? I have read the book and have an opinion.

Hybrid Project Management is often just a buzzword. It’s a combination of:

  • Linear, predictive, planned project processes

with

  • Evolutionary, adaptive, iterative approaches

The common way of thinking about hybrid is as the intersection of the two ways of working. I don’t like that. It’s better to think of it as an approach that takes whatever you need from all the toolsets, frameworks, and methodologies in either paradigm.

And that’s how it’s been.

Yes, there are models and frameworks that draw liberally from this whole landscape. Two that come to mind are:

  • The FLEKS Model, by Hélio Costa
  • P3 Express, from Nader Rad and Frank Turley

FLEKS Model

This is a whole approach to handling activities from enterprise-scale down to product level. It is truly hybrid, in that it is methodology agnostic. It provides a mental framework and a set of tools. But it is not a true methodology. Rather it guides how we think about complex situations.

More on FLEKS:

P3 Express

This system is at the opposite end of the spectrum. It’s designed to be minimalist, and aimed at lightweight project implementation. It’s truly hybrid, merging an overall life cycle framework with a series of nested iteration loops. And I’d call it a methodology, because there a clear guidelines for doing each thing you need to do. It even has a lightweight (small) set of (simple) tools.

More on P3 Express:

Frameworks, Methods, and Methodologies

I thought it would be useful to define some terms. Because these terms are used a lot. I would define them as:

  • Framework: a structure within which to do something
  • Method: a way of doing something
  • Methodology: a system of methods and principles used together

Therefore a framework offers a lot of freedom about how we do things. Methods are more specific in how to go about things. Methodologies set clear processes for many (or even all) aspects of what you do.

So, let’s look at the gap

I was not aware of a full methodology that offers a truly hybrid approach to big (and maybe complex) projects. Until, that is, Arash Parsania contacted me.

Disclaimer: Arash sent me a review copy of his book, at no cost. I did not guarantee a review and he has not seen this review or influenced it in any way, ahead of publication.

Arash is the developer of HYPERID (pronounced hype-rid). He explains that it stands for Hyper Inter-methodological Delivery. Well, that naming is all pretty horrible. So, let’s move on quickly!

How Good is HYPERID? A Hybrid for Project Management Methodology

What is HYPERID?

Quite simply:

  • it is a methodology
  • it is hybrid
  • it is scalable (in principle)
  • it is detailed (very)

You can learn more about it on the HYPERID website.

Arash developed his methodology to take the best of traditional linear project methods and combine them with aspects of agile frameworks like Scrum. And he does so pretty well. He also claims to have improved on both in the areas of delivery performance (more on that in a bit) and budget/schedule reporting. I am less convinced that we can see clear innovation.

The HYPERID Book

The book is called HYPERID – A Hybrid Methodology for Project Management and Product Development. It is available in German and English, from the major academic publisher, Springer.

However, the English version is an AI-assisted translation. I am not keen on the prose – there are some very long and rambling sentences. And it rankles that, in 2024, the Project Manager is referred to as ‘he’. That, despite the proper use of ‘person days’ (rather than any gendered versions).

The English version that Arash sent me is clearly a high-quality print-on-demand (POD) book. It has that feel. But it’s high quality in that it has color diagrams and decent layout. As a mainstream publisher, Springer has avoided some of the worst aspects of POD layouts we see. These low-quality POD layouts, by the way, are inexcusable in modern times.

HYPERID – A Hybrid Methodology for Project Management and Product Development by Arash Parsania

Overall Impression

HYPERID is a heavy read – not just because of the poor translation. There is a lot of detail in this book. It has huge amounts of information, ideas, and the author’s tips and experiences. If you want a detailed ‘how to’ for a truly hybrid lifecycle, this book really delivers.

And, for a second-stage project manager (beyond their initial training and looking to learn from the advanced ideas of a seasoned practitioner), this book delivers a vast amount of content.

Simple and Complicated

However, this does not make project management simple. It gives it the feel of lots of complicated things to do. And yet, the over-arching life cycle model is commendably simple:

  • Define Scope
  • ADP: Analyze, Design, Plan
  • Deliver Value

This means we have a book that creates a real working chimera of linear and iterative processes and tools. And it provides prescriptions and advice all the way through.

But, what it does not do is make it clear how you can simplify this methodology for simpler projects.  I think there is a reason for that: why would you. There are simple, lightweight approaches available.

But, this fills a gap.

My Favorite Ideas from the HYPERID Book

To end, I’d like to pick out two ideas that really struck me: the ideas of Delivery Performance Index and Core Design.

Delivery Performance Index (DPI)

I like his concept of ‘Delivery Performance Index‘. He defines it as:

DPI = TP x RE

Where:

  • TP is Team Performance (an indicator of how well people resources are deployed)
  • RE is Results Efficiency (an indicator of how results are used)

It’s a nice idea, and one of many in the book. But you have to hunt to find the definitional details, at the back in chapter 8, Definitions.

Parsania argues that neither Waterfall nor Scrum perform well when measured by DPI. In private correspondence, he argues that Scrum has poor Team Performance and predictive methods show low Results Efficiency. But HYPERID, he argues, does better at both by harnessing the strengths of each. I can see this but, sadly, the book does not draw this through-line clearly.

Core Design

I really enjoyed the metaphor of the product design as a 2D box. Within the area of that box, Arash suggests that waterfall would fill the whole space with the core design. I accept that as a generalization, though my experience is that, even in the most highly planned projects, the design can and will shift.

At the opposite extreme, he shows a scrum or XP (extreme programming) project having a tiny sliver of core design, with the remainder to be filled during implementation.

The hybrid approach is a small area of core design and the remainder to be filled with work packages that are developed during delivery.

Future Plans for HYPERID

For HYPERID to become a widely known and effectively-used methodology, it will need the kind of infrastructure that PMI, Scrum, and PRINCE2 have. This means more than a book and a single advocate. It will need marketing, training, certifications, and a community. I know that Arash Parsania is working on these.

But it is a big task, so do get in touch with him, if you feel that this is an opportunity for you. He and I were first in touch via LinkedIn, so I suggest that this is a good place to start. Take a look at his profile and send him a message there. He may also comment on this article.

Summing-up HYPERID – A Hybrid Methodology for Project Management and Product Development

This is a valuable contribution to the evolving need for truly hybrid methodologies. The book has a lot of value to offer.

I am not sure how successful Arash will be in winning converts to his methodology. That is a BIG task.

But, I do think he has created a methodology and written a book that is worthy of attention. For serious project professionals who want more food for thought on how to craft a true hybrid environment, this is a great stimulus. And, for some, the methodology may be just right to form the basis of their way of doing things in the next stage of their careers.

What do You Think?

Have you read this book, visited the website, or even used the HYPRID methodology? Please do share your thoughts below.

Never miss an article or video!

Get notified of every new article or video we publish, when we publish it.

Mike Clayton

About the Author...

Dr Mike Clayton is one of the most successful and in-demand project management trainers in the UK. He is author of 14 best-selling books, including four about project management. He is also a prolific blogger and contributor to ProjectManager.com and Project, the journal of the Association for Project Management. Between 1990 and 2002, Mike was a successful project manager, leading large project teams and delivering complex projects. In 2016, Mike launched OnlinePMCourses.
  • Many thanks, dear Mike, for this article, which I in fact did not know until today. I am all the more pleased about your positive assessment and evaluation, as I particularly value you as a true expert in the project management discipline and a role model for the majority of PMs. With this accolade, the methodology will bring itself to the people😊.
    I agree with you: the book focuses in particular on large and complex projects. This is because there has been no suitable approach for them so far and because they are the ones that fail the most and have serious consequences. Smaller projects are naturally less risky and therefore run better; and their failure doesn’t hurt too much.
    And to clarify your comment for the readers: from a process perspective, small projects should be treated identically to large ones with HYPERID. Each phase/process step is only processed in a much shorter time. The only question mark for HYPERID newcomers would probably be the ADP phase and its approximations, as the scope of a small project is simply defined more quickly and fewer delivery cycles have to be implemented in the Deliver Value phase, in the minimum case only one. But it would also be easy to apply the ADP phase to small (or very small) projects. Since the actual goal is always to achieve the third approximation, this approximation can be applied directly to the smallest projects. The ADP approximations 1 and 2 are applied beforehand anyway in order to cope with the complexity of large projects.
    But a good suggestion from you to pay more attention to this topic: perhaps this would be the material for a new book with a brief explanation of HYPERID and the presentation of its suitability for small projects.
    And you are absolutely right: it needs more than the definition of the methodology itself. Therefore – as you also noted – training and certifications are currently being prepared and will be published soon.
    And thank you for the call to your readers: Yes, anyone is welcome to contact me who would like to participate as a first mover in trainings, consultations, etc. to help significantly improve the success rate of projects with HYPERID.

    • I think that once you have a training program in place and have stress-tested your ideas with a live group of experienced practitioners, you will have an even better product. I wish you all the best for your rollout of training and certification.

  • {"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}

    Never miss an article or video!

     Get notified of every new article or video we publish, when we publish it.

    >