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

The Bus Driver

They took some time to plan for the trip… They drew the road map, bought some food and beverages… and got equipped with the necessary tools… They were going to travel through the woods to draw the magnificent scenes which were observed by their neighbors early this year… This wasn’t their first trip together as a team, though they were all excited… The bus driver was in charge for making the big decision in the trip while taking care of the travellers’ team while of course driving the bus and communicating daily with his supervisor in the station. The map was clear, the weather was very well studied, though the bus driver expected to pass by some pitfalls in the road as there were some reparation in the way. He reported this to his supervisor and requested to take some more supplies just in case they have to camp one or two days more, but the supervisor refused “ the trip has to be completed on time and the painting should be ready for sale by the end of the week ” Anyways, ...

The Triangle is missing The Circle

By experience -the bad one of course- I discovered that the famous Project Management triangle is missing a very important containing circle… The Strategy Circle . The Strategy Circle is my simple explanation for many of the catastrophic situations projects end up with. I totally believe that this should not happen and that Strategy exists to set goals and directions for the benefit of organizations and accordingly for the benefit of projects and teams. Unfortunately, I witnessed many cases where it was exactly the opposite. I was an eye witness of the failure of many projects and sometimes companies because of misunderstanding the meaning of Strategy and how to use it to bring companies to success. Some companies bankrupted because of this! De-formation Effect The Strategy Circle is sometimes surrounding the Project Management triangle and thus imposing pressure on it and suppressing it and some other times it is pushing on the triangle from the inside and thus inflatin...

A Project Manager's Diary

Search This Blog