Developing a format

Create a project progress report format for this project.

You have just become the project manager for a project to combine three separate insurance software applications. There are two different types of front-end applications and a database application where most of the data is stored. One application is ten years older than the other and handles the client data for three of the insurance packages. The other application is three year's old and handles the client data for six insurance packages. The database provides information to both of the other two systems. This has led to problems in keeping all the data synched especially for clients who are on both systems. It has also been inefficient to maintain three separate systems. So the goal of this project is to develop an application where all the data can reside with one front-end. There are customer service representatives (CSRs) for each of the two front-end applications, and each set of customer service representatives is trained only in the application they work on. So your project also includes training for the new system.

The personnel resources on your team include the content experts from the CSRs, developers, designers, business analysts, trainers, technical writers, and database engineers. Several members of the project team are internal to the company's IT department, and several have been contracted from outside companies to participate for the duration of the project. The two CSR managers want to make sure the CSRs' day-to-day work won't be affected by the conversion to the new application, but they are willing to let two CSRs participate on the project part-time as content experts.

Your project sponsor, the director of Customer Relations, likes to have a lot of control and likes to see details, but he is sponsoring several large projects and isn't a very detail-oriented person so he doesn't remember all the details. He also wants to make sure good relations are maintained between his department and IT.

The company has a standard project progress report format, shown below, but your project sponsor thinks it is too hard to find the most important information. He has asked you to give him the reports in a format that highlights the critical information while also giving him some of the less critical details.

Reporting period

Project ID

Major achievements in last period:

Major issues and difficulties encountered in the last period:

Activities planned for the next period:

Risks and expected difficulties for the next period:

Decisions to be taken:

topic

comments | decisions | actions

responsible

due date

comment |
decision |
action |

comment |
decision |
action |

topic

state of affairs | decisions | actions

responsible

due date

[topic]
state of affairs |
decision |
action |

[subtopic]
state of affairs |
decision |
action |

[subtopic]
state of affairs |
decision |
action |

[topic]
state of affairs |
decision |
action |

[subtopic]
state of affairs |
decision |
action |

The following format provides the minimal information plus the information on team members since your project sponsor should be kept aware that there are resources on the project from several different departments including his own. There is enough space to provide details, but you can also provide your project sponsor with supporting documents, that is the project charter, issues log, risk log, and change log instead of putting the details in the report. This way the important information will be highlighted and easier to remember, while your project sponsor will still have access to more details.

Project ID

Week

Project Manager

Budget Status

Projected Completion Date

Schedule Status

Team members


Milestones


Issues


Risks


Change Requests