Failure Story

Some people consciously choose to fail!

Usually people write about their success stories… Well, I decided to write about what I call my failure story. You can consider this blog as part of a documentary book on the quickest steps and worst practices to attain failure smoothly!

From my point of view, a good and very fast way to failure starts with having to deal with uneducated not willing to learn people who reinvent the wheel in everything they do while thinking they are making great achievements for humanity, which is of course by going many steps backward! Such people highly rely in their work on the concept of pretending to be smart and on applying theories in very wrong ways. This always ends with catastrophic failures in projects accompanied by huge financial losses.

In our contemporary life, these people are not rare, I think they invaded and dominated the fields of Software Development and Software Development Management, though there are still many many good people who try to rectify things and save the world!

There Is Always Hope

I am not pessimistic… To look at the bright side of the picture, you can consider that avoiding the mentioned above steps may lead you to success.

For a couple of years now, I’ve been thinking about early retirement as my work-life is a series of hard work in conjunction with stressful projects and circumstances which keep escalating from a project to another.

I finally decided to take some time for myself to rest and to take my breath while re-evaluating the past years’ experience. I’ve also decided to share my experience with the world hoping it can be of use for anyone. The only thing I regret is writing from memory, as I forgot lots of events and details.

I think this blog is the only deed I’ve done in my practical life, though it may be considered as some kind of a black sarcastic diary!

If I still exist, I guess I’ll have about some other 20-25 years to go… and I want to make them different!

Hopefully, there will be light at the end of the tunnel… I really hope!

Comments

The Triangle of Tactics

Sometimes referred to as the Triangle of Horror… where the PM tries his best to maintain his balance while walking on the very thin project rope between this triangle and the Project Constraints Triangle (time, cost & scope). The triangle sides represent: The Team, The Client and The Management Every side of this triangle is obsessed by the sole idea that the other two sides want him dead, i.e. the team thinks that the client and the top management want him dead and vice versa. Usually a good PM gets lost while trying to maintain this triangle in good shape to keep all parties satisfied and happy while making them think they are his first and only priority to get out what is needed from them for the sake of the project. From my perspective, this is a much harder balance to keep rather than maintaining and managing the Project Constraints Triangle… It highly depends on people, their culture, maturity level, and on the PM’s ability to understand this and deal with it in a ...

RPM Technique

I once used a very weird technique with my team to get things done in a short duration in a project that was very far away from being on schedule… For a while I’ve been asking my team for their progress, following up heavily and on daily basis, staying late with them in the office and sometimes staying till the next morning (online from home), trying to dig deeper by developing and testing with them…. And still we were very late in achieving any of our internal milestones… By time, I was empathizing them and I was trying my best to reduce the effect of the pressure under which they were put for a long time. We started a weekly game competition with some funny yet work-related rules, amongst which was “ each member in a sub-team should finish his work before the day of the competition ”… it went fine for about 3 weeks, then the situation became worse… and we all stopped participating in the competition… I then tried another technique… I started buying them either lunch or dinner in ...

5 Reasons not to listen to a PM (for Managers)

Usually a PM cares about his projects and is keen to develop them as per the planned budget, time and scope. However, managers should not listen to their PMs for the following reasons: 1. PMs are Time Wasters PMs plan… They study and mitigate risks and project issues in proper ways to guarantee the smooth execution of the project. Planning is a bad practice that PMs should stop using and referring to whenever they discuss a project related issue. Plans are not really needed and in most of the times they are useless because no one follows them (all gratitude and respect reserved for PJs). Also, it is preferable to face risks when they fire. Anyways, who really cares for risk mitigation and contingency stuff! Let’s face surprises when they arise and use panic mode to push on teams to solve their issues! 2. PMs Forecast PMs track their projects and use trends, issues, project and client historical data to forecast project status and use corrective actions properly to maintain thei...

A Project Manager's Diary

Search This Blog