Skip to main content

Project Baxecution

In addition to the very well-known techniques/lifecycles for project management, I found out that a new technique emerged lately. This new technique highly depends on performing project tasks and phases in a reverse non-organized order! This is known as the Project Baxecution (Project Backward Execution) concept. It embraces the following practices in addition to the Surprise factor which is a common factor at the end of each stage:

  • Deliver the project before getting the requirements (because it is not important!) –> Client is surprised
  • Test the project after receiving some of the requirements –> Testing team is surprised
  • Develop the project after reviewing bugs –> Development team is surprised
  • Plan for the project –> Top management is surprised
  • Gather the project’s requirements –> Client is surprised again
  • Restart the project in the same order, kind of Spiral Development model –> Everyone is surprised!!

ProjectBaxecution

Just to clarify, this is a stand-alone technique that has nothing to do with any of the following:

  • Agile Project Management model
  • Early Feedback concept
  • Test Driven Development methodology
  • Change Management process
  • Any other logical reason, model, process or methodology!

It is purely and literally a Client Driven Development process in which the client knows nothing about his project and the vendor follows him blindly while striving to please him.

Also, please take into consideration that the typical constraints of time, budget and scope should be met while the requirements keep changing and emerging!

Baxecution Projects Framework

  • Start with good hopes, intentions and wills to deliver a successful project (a common step projects start with)
  • Run with lies totally lacking transparency
  • End tragically with loss, kind of divorce like!

Tip: This is a very easy to apply process, all you have to do is to close your eyes!

Labels:

Comments

BLUE said…
Gamda geddan 3ala fekra...E7bat RAHIB lies behind it :)
May 2, 2011 at 4:54 PM
Post a Comment

Popular posts from this blog

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...
3 comments
Read more

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 ...
4 comments
Read more

To PMP or not to PMP?!

That is the question! As implied by its name PMP (Project Management Professional), to obtain such a certificate you should be a professional in the field of Project Management… To my surprise, almost 95% of the people I met holding this certificate know nothing about Project Management!! They think that studying for this certificate and obtaining it means they are professional, although they should be professional to deserve such a certificate. I understand that one of the prerequisites to get this certificate is to have some practical experience in the Project Management field. But for some odd reason, I discovered that the people I am talking about, which are a majority in the field now, don’t really have experience, some of them are even fresh graduates… I once had a very aggressive argument with a “ kid ” in my team, and by the word “ kid ” I am referring to his age and his attitude in despising my knowledge and experience due to his ignorance, he was very aggressive and arrogant...
2 comments
Read more