1

I have this figure of "Project Control Cycle" from a book, Software Project Management by Bob Hughes:

enter image description here

It comes under a section "Management Control". There seems to be less description of what is the point of view to look at this diagram.

I want to understand what this diagram is about just by looking at it. I can see that you are making collection of some data from real world, processing information, then "implementation" [?] how are you actually implementing it? and what actions are taken on real world?

2

The title "Project Control Cycle" gives a clue: here's how I would read it.

The point of the diagram is that it is a feedback cycle for project control. Let's start in the middle: in order to make project decisions, you need objectives (what you're trying to accomplish) and information (how you're doing so far, what your users want, what the competition is like, etc etc).

Defining what you're trying to accomplish is pretty straightforward, but you can't get information from the world - you can only get data. You collect raw data from the real world (eg, keyclicks), and then you probably process it iteratively (eg, turn it into analytics). Now it's useful information.

In order to decide what to do in order to accomplish your goal given that information, you probably have to do some modelling, whether formal or informal. EG, "People are only spending 2 min on my website, and I want them to spend 5 min. What will probably happen if I add a rotating gallery? What about an article with a comment box? What if I rearrange what's there?"

That modelling process will eventually lead you to a decision: in your models, the article with a comment box was most likely to get people to spend 5 min there. So now you have an informed decision and/or plan: "We will add an article with comment box to the website. This will require (assorted task breakdown and schedule)."

The "Implementation" stage is "implement the plan". Do the thing you decided to do.

And now... it's done... it's deployed out in the real world.. and you start gathering data from the real world again. Are people now spending 5 min on your website? What else has changed? What's your next objective? And so forth. Lather, rinse, repeat.

0

It appears that in the diagram the boxes represent steps to be taken in the process, and the text on the arrows represents what you are carrying from the previous step into the next step. This chart does not specifically explain what steps are taken in implementation, that varies greatly by project. What this chart emphasizes is the four phases, "Data Collection" > "Data Processing" > "Making Decisions / Plans" > "Implementation", and the fact that these four phases lead up to actions that carry over from your project plan to the "Real World" for the process to be continually repeated as an organization/project evolves and you continue to refine what was already put in place.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.