Website development progress report template

Our main objective is to make a good website 2 using advanced new technologies and advanced coding 4. Qualit is ou fi st p io it. Ou team has only 6 members and they are skilled i thei field, so e a a hie e Lo ost a d ette i teg atio ad a tage. Ma i u suppo t to ea ette se i e with relatively low cost 8. As most of the members are young, they have a better understanding of new advanced technologies and we are looking forward to use those 9.

Customers 2. Products 3. Market 4. Technology 5. Profitability 6. Philosophy 7. Self-concept 8. Concern for Public Images 9. Concerns for Employees. To predict we need to use any analytical matrix. Here we used simple SWOT matrix. As all the members are of same age, lack personnel. Specialized only in Website building. Relatively less experienced team. Better team communication. Use of the latest advanced IV.

Lack of Human Power. Large IT firms offerings. Low cost and almost no investment. No initial hosting space for testing. Can hire specialist on demand. Greater fluctuations in project costs. Less bureaucratic procedures. Domain frauds. Direct supervision of client. Price hike of components required. Open for any strategy change. Restrictions given by University that will limit data access. The project manager must define and understand the nature of the priorities of the project.

The project must meet the completion date, specifications and scope of the project or budget. Conversely, with regard to performance, enhancing means adding value to the project. When trade-offs have to be made, is it permissible for the schedule to slip, to reduce the scope and performance of the project or to go over budget? Time is considerable as we have enough time to buffer.

The performance of the site should be enhanced and is the first priority. WBS is best suited for projects that are tangible. For process oriented projects such as this project Website WBS is difficult to apply. Here the project is divided in to several steps or phases. The projects evolves with one phase affecting other phases.

For the purpose of padding or buffer time the deadline is set to be done in days. So we have a buffer time of 16 days. In case of any delays we have enough buffer time to overcome any unexpected events. We have used Apportion method under Top-Down Approaches. The details of the cost is included in Appendix 7: Budget Report.

It is assumed that payment is sanctioned at the beginning of each activity. Key project management responsibilities include creating clear and attainable project objectives, building the requirements and cost management, schedule and the quality of project. Determining and implement the needs of the department is also his major focus.

Ide tif optio s fo i p o e e ts a d ho to a hie e these requirements and how to bridge these with the project. He will play the supporting role to the technical development of the website.

He must have expertise both in graphic design and required programming skills. Upon creation a web designer has to play the role of maintain and add new additions to the website. While the site is under construction web designer has the role of making outlook and after the site is constructed he works with the team that maintains the website.

After testing if any problem arises that is related to the back end programs the database specialist is the one responsible to fix. A database specialist should be hired carefully. Trust and having a written agreement is important for the security of the website. The project team has a tradition of using updated technologies which is unique. Member Identity Job Organization Team Emphasis Individual Group People Focus Task People Unit Integration Independent Interdependent Control Loose Tight Risk Tolerance Low High Reward Criteria Performance Other Conflict Tolerance Low High Means-ends Orientation Means Ends It is a guide of communication for the project.

It will update as the communications needs to perform. It is regularly assessed and updated throughout the project life span. The roles of each individual is identified and defined in it. It includes a communication matrix. A communication matrix defines the communications requirements in the project. It describes communications rules and the process of holding meetings.

It ensures every meeting successfully serves the purpose of holding it and get desired result. While communicating with the stakeholders the structure of the project team should be presented. The Communications Matrix has defined the communications requirements. To determine what information to present the communication matrix will be used. What to communicate, to whom to communicate and when to communicate is described in the matrix. The communications should be short and brief unless they want more information.

Project manager and members should only communicate if the sponsor asks for. Technical designs, implementing design and documentation. He will communicate closely with the project manager and project team. He will communicate with supervisor and project manager. They need know whole project plan, progress over the time and possible changes in the system the department now work with. They will be kept in touch by the supervisor and project manager. Also the CPanel they think better should be chosen.

In these regards the need to be in close touch with project team. Also enough training should be given to them. They will be briefed by the senior web-designer. This will be used as the address directory. It should include the topics, presenter and time required. A review and comments on last meeting should be discussed at the beginning of every meeting. Additional time should be kept after the presenters time requirements. It will also take into account the discussion time and review time.

It should be suitable for every participant. The ideal place should be in the campus of Jahangirnagar University. Action items are recorded as per agenda and time duration.

Meeting should start with the review of the action items of the previous meeting and end with the decisions taken on the current action items. The owner of the action items should be identified at the review of each new action items. All the important items discussed in the meeting should be well documented. The record keeper will hand over the record to 47 the chairperson.

The project member will then pass it to the project manager and other members if needed. The project manager will then take necessary steps to resolve the issues. Before making any changes the team should discuss with the stakeholder. It also suggests that p oje t management team is well aware of the risks and it is possible to take actions to prevent these.

The site will be used both by students and non-students. So there is a great uncertainty whether the outside users will get what they are looking for. The project team will work with limited resources and time.

To finish the project on time and efficiently, risk mitigation is an important task. The risks that are most probable and has highest impacts is stated here in this schedule so that the persons responsible can take preventive measures early to reduce the risk. The meetings are arranged to give updates on the risks to the stakeholders and the sponsors. It is necessary to provide reports on the risk management if it is significant. The project manager and the members are responsible for these reporting.

Once completed the project team will assess what risk factor arose and how they handle the risk. They will also analyze the outcome and check if there is any scope for improvements. He will be responsible for monitoring the project risks and plan strategies to mitigate the risks. Project performance such as budget, scope and milestones.

The senior web programmer is an experienced professional in the field of web programming. He will take strategies to mitigate risks related to technology and web development. These risks are mainly the performance of the web site and backend programming. The central role of risk manager will be mainly played by the Project Manager. To get desired result it is important that all the actions taken is rationalized in the meetings and other form of o u i atio.

Also the p oje t is highl depe de t o the sepa ate tasks. It is also required to clarify the requirements by the next phase. There are five main areas to consider:. People who may need to be updated might include:. It may be that one update will be suitable for all involved lucky!

Start by making a list of all the people that will require project updates. Establish what people want to know and share only that. Do they need an update on:. These range from the very specific daily tasks to the top-level headlines of a project. Does someone want to know what stage the project is at and what is left to achieve or do they need precise information on what was agreed about a typeface, piece of content or functionality?

Find out and provide only that information. If you are producing one large report, pull out the relevant information for the individuals you are reporting to. Make it as easy as possible for them to get the information and answers they need. Understand why people need to be updated so you don't spam them with unnecessary information.

Considering the 'why' also means that relevant actions and information can be surfaced from the noise. They might require:. There's little point in emailing someone regularly if they just want to know where things are at the end of each month. Similarly, if someone needs to be keep in the loop regularly, they may become anxious and concerned if they only hear from you every four weeks. Making the updates timely, for instance if the updates are also requesting actions, will ensure the recipient has enough time to do the required action too.

There are plenty of options available, including, but not limited to:. Some people just love a slide deck or a whomping great PDF! But what they want doesn't mean that's what you should provide. Not to cause friction unnecessarily, but you have to consider the value of the time spent creating the report in relation to who is receiving it and why. The information they need may influence the format it is provided via.

If someone just wants the latest progress headlines then perhaps a quick phone call though it can be good to have a paper trail for projects or email should suffice. Written updates might be supported by Gantt charts, visuals, or other supporting information. Sometimes a picture is all that's needed!

Effective progress report writing is about knowing your audience and being realistic about the time and resource it would take to provide different types of reports and updates. Make it as easy as possible for stakeholders to get the information they need and they are more likely to stay engaged with the project, be able to provide any sign-off, feedback, approval, answers you need in a timely manner too. One of the biggest challenges of website projects is managing the expectations of all those involved but when you achieve this, the path to the finish line should be less bumpy.

Well written and communicated progress reports will help you get there. Rob is Founder of Fourth Wall Content working with clients on content strategy, creation and marketing. Previously, in his role as Head of Content at GatherContent he managed all of the organisation's content output and content operations.

Product Marketing Manager, GatherContent. Product Content Design Manager, Shopify. Why GatherContent? Increase productivity. Content Hub. It involves tracking of the actual project progress, including its performance based on the identified metrics and in terms of risks, issues, changes.

The frequency of reporting usually depends on the size of the project. For small projects which have a duration of fewer than three months, this report is usually weekly or bi-weekly. Medium-sized projects would require monthly reporting while larger projects need monthly or quarterly reports.