Let’s talk about ROP (Return On Project), a ‘Project Management & Business analysis’ concept I am working on; ROP is all about efficiency and effectiveness: if the goal of your project is attained without wasting resources (…I think of time & money, of course…), then ROP is very high – don’t worry, we will work later on a significant measure for ROP…
A low ROP means angry project stakeholders, due to (…typically…) over-time (“We are late!!!”), over-budget (“Lower margins!?!”), low-quality (dysfunctional UX-User experience, bugs, low performance, disappointed users, etc.).
On the contrary, a high ROP makes your Clients smile, improves your company P&L and helps your ‘Project Management & Business analysis’ career take off (…interested…?).
Please note: ROP is strictly related to the ‘success’ of your building activities, not to the ‘success’ of what you built; in other words, if your team did a great job creating a product (or a service), the Return On Project is very high even if the product (or service) actually is useless and a failure from a business point of view.
My ‘original’ idea: if we categorize the most common causes of wasted resources in the life-cycle of a project, we will be able to reduce them and consequently improve ROP (…and your career, as I told you before…).
Here is my priceless list of the most significant wastes that affect – more or less – any project (…yes, I confess, I was somewhat inspired by the philosophy behind TPS-Toyota Production System…):
1) Over-convoluted project workflow (“I hate burocracy! I hate overhead!”)
2) Too many ‘Not-yet-in-Production’ (that is, not yet ‘usable’) COMPLETED features
3) Uncontrolled piling up of new feature-requests (“…doesn’t it remind you of a bad game of TETRIS?”)
4) Project workflow bottlenecks (“Hurry up, Andy!! I’ve got five people waiting for your deliverable!!”)
5) Implementation over-complication (“‘Simple’ and ‘elegant’ is most often than not better than ‘fancy’ and ‘sophisticated’”)
6) Bad ‘feature-implementation’ prioritization (“Who cares that we can back-up our DB? We don’t have a DB yet…!”)
7) Bug-proliferation (“What does HTTP500 mean?”)
In my next seven Posts, I will talk about each one, so please be patient and follow me – don’t hesitate to subscribe to my blog [http://meetingofideas.wordpress.com] to receive them in your inbox.
One more thing: your feedback is very appreciated!
Andy Cavallini – Business Analyst & Project Manager