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!!

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!

Comments

BLUE said…

Gamda geddan 3ala fekra...E7bat RAHIB lies behind it :)

May 2, 2011 at 4:54 PM

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

I am a Project Manager

I am a Project Manager and I love my job… I am a project Manager and I love doing my work! I am nothing more but a Project Manager amongst many others. I got married to my work (not job) after a great love story which started from early childhood ( coming soon ). I started my career as a Software Developer in the late 90s, then held many positions in the field of Software Development, some were promotions and some were kind of additional assignments due to my performance. Among the positions I held are Developer, Team Leader, Project Manager, Project Leader, Senior Project Manager, Senior Project Leader, Program Manager, Business Analyst… though I was dreaming about becoming an Architect! But seriously the job I loved the most is Project Management. The things I hated the most in my early years were politics and economics/finance, which both became the core of my daily work for some years now! 94% of my experience was built by working in Software Houses as a vendor/provider and

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