Most employees and contractors who work on software projects are required to file status reports. Regular status reports can make the difference between the success or failure of a software project. Since managers cannot gauge the progress of a software project just by oberservation alone, they depend on regular feedback from software builders like programmers, system analysts, instructional or game designers, technical writers and graphic artists to know if a project is going well and if not, why.
Basically, staff members file status reports to inform supervisors and managers about the progress of ongoing software projects. Since status reporting is not an exact science, the required information varies with the company and even with the manager, but most status reports include some or all of the following:
A status report is not just a copy of your daily activities for the past week. Status reports describe the work you’ve completed and forecasts how close you are to finishing the project. Ultimately, these reports indicate whether your work is on schedule and if anything threatens your meeting the deadline.
Because status reports vary in format, length and delivery, it is difficult to nail down what to include in them. This is due to the communication format preferred by managers, which is dependent upon individual preferences. Some companies require verbal status reports every week. These verbal reports may be given in a group or one-on-one. Generally the staff member knows in advance the type of questions that will be asked or the format their group delivery should follow. While the verbal report is given, the manager writes down the salient points. Some employees like delivering verbal reports because it saves
Project stakeholders want to know if the software project is going to be completed on time and within budget. Team managers, project managers and department heads combine their employee status reports into a broader report that is submitted to their next-level managers. This upper-level manager then forwards the essence of these reports to the stakeholders. On every level, status and progress reports depend on the information gathered from other managment levels, a process resembling dominos. For instance, if a project manager needs status reports from 10 people working on a project, but only receives 8, the report prepared will not be complete, nor will the ensuing reports.
Creating and filing a status report dosn't have to be painful. Actually, periodic status reports give you, the creative person, a chance to shine. If you work on a software project you probably spend hours and days alone, working on the computer. Creating a positive, upbeat status report gives you an opportunity to show how good you are and what you have done. If you have solved a problem, helped a coworker, posted a procedure, or passed a milestone be sure to put it in your status report. It’s like writing a little bio of yourself and the work you've done.
This article is Part 1 in a 4-part series on Creating Status Reports for Software Projects. Here are links to the rest of these articles:
Part 2: Creating Status Reports for Software Projects: Use MS Word
Part 3: Creating Status Reports for Software Projects: Use MS Excel
Part 4: Creating Status Reports for Software Projects: Use MS Visio
)