Skip to main content

Algorithm for Successful Project Management...

Any project planning and execution should follow the steps given below to be successful.

#1. Understand the goal (why)  and the scope ( what ) of the project.
#2. Understand the external and internal constraints (factors) that impact the project
#3. Plan (Who, does What, When and How) to reach the goal, considering #1 and #2.
#4 Once planning is done, execute steps #5, #6 and #7, till #8 is satisfied.
#5 Execute the plan.
#6 Keep checking for changes in #2 and #1.
#7 Modify the plan as needed.
#8a Do the above till the goal is reached.
#8b Drop the project if the project is no longer feasible due to changes in internal and external constraints.


I call the above Project Management Algorithm.

While this can be very obvious and looks very simple, experience tells me that it is not so obvious or as simple :)

And don't be taken in by the simple steps. Each of the steps given above can be elaborated and a lot can be written.

The attached image was part of an article that described an algorithm that physicists have come up with that only quantum computers could use.

I have added it to remind ourselves that project management may not be simple, but at the same time, it doesn't have to be as complex as quantum computing.

Comments

  1. This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …