Sunday, August 17, 2008

How to Create a Clear Project Plan

http://www.cio.com.au/index.php/id;767465578

Hi Guys,

This is a project plan structure, which I think we put too much focus on SWOT, SWOT and Smart should be a part for supporting not as main topic, I think we will have to make the breaking down of our project plan again here are some topics we should cover but not in the list of our previous plan.

Step 1: Explain the project plan to key stakeholders and discuss its key components.

Step 2: Define roles and responsibilities.

Step 3: Develop a scope statement.
This part should link with our SWOT and SMART
should this part also include Research

Step 4: Develop the project baselines.
Schedule and cost baselines

1. Identify activities and tasks needed to produce each of the deliverables identified in the scope baseline. How detailed the task list needs to be depends on many factors, including the experience of the team, project risk and uncertainties, ambiguity of specifications, amount of buy-in expected, etc.

2. Identify resources for each task, if known.

3. Estimate how many hours it will take to complete each task.

4. Estimate cost of each task, using an average hourly rate for each resource.

5. Consider resource constraints, or how much time each resource can realistically devote to this one project.

6. Determine which tasks are dependent on other tasks, and develop critical path.

7. Develop schedule, which puts all tasks and estimates in a calendar. It shows by chosen time period (week, month, quarter or year) which resource is doing which tasks, how much time each task is expected to take, and when each task is scheduled to begin and end.

8. Develop the cost baseline, which is a time-phased budget, or cost by time period.

This process is not a one-time effort. Throughout the project, you will most likely be adding to and repeating some or all of these steps.

Step 5: Create baseline management plans.

Step 6: Communicate!


I think we will have to consider this as our sturcture of our assignment.

1 comment:

A Dekker said...

Hi All,

Good that you are thinking outside of just what is required. That being said, remember to make sure you clearly cover the criteria. Just to reiterate the steps that you have covered in an order that may flow alright:

1. Project description (as a smart goal) and project plan description (inc. key stakeholders and key components)

2. Scope of the project - what is and isn't covered in the project (this probably should be a summary of the tasks you have listed)

3. Roles & responsibilities for team members (a blurb about each would be good, as well as how you integrate work together)

4. Tasks - Lists of tasks needed to complete the project would be good here (inc SWOT/smart perhaps) and as definite as possibly

5. Plan - When are the tasks done, how long and by who (Gantt chart would be useful here)

6. Cost Summary - Costs (link this to the plan and the tasks)

7. Expectation Management - How will you communicate between youselves, clients, users to manage the expectations of the system (this will most probably be covered tomorrow).

8. Appendicies - If there is any information you have that doesn't necessarily fit in the end.

Something like that (which is a culmination of your tasks + the criteria sheet) could work well. I would create a professional report if possible (it just looks better and makes it less throw-away as you go through the project). Definitely google each of the sections independently (there should be articles on each), may help you streamline what is required.

Hope that helps, yell if there are any problems understanding my spam.

cheers
Dekker