Question

RISK ASSESSMENT RISK LOW/MODERATE/HIGHT MITIGATION FOR STUDENT WEBSITE PROJECT

Answer 1

Let me explain some risk assessment for student website project as follows.

Too many decision makers (stakeholders, committees)
This can cause bottlenecks within the call and approval method. make sure that project managers/representatives are sufficiently sceptered and supported to form selections.

Custom-coding to induce options “just right”
Sometimes compromise is critical. generally, ninetieth of a feature is sweet enough if delivering on it last 100% goes to require 100s of hours of custom writing and testing and cause giant time and budget overruns. KISS!

Staff turnover
Ensure that project communications and standing coverage ar clear, up-to-date and accessible to new project members.

Scope creep
Both consumer and provider should air the lookout for the fearsome scope creep. Scope creep is wherever new project options are being requested that didn’t type a part of the initial transient, and can’t have moderately been expected to be enclosed. further feature requests should be evaluated in terms of seemingly project impact, and selections then ought to be created in terms of whether or not to incorporate or not include the new feature requests within the current section.

Underestimation of the time/resource commitment
On average, we have a tendency to observe that purchasers underestimate the number of your time they themselves can ought to invest within the project for it to stay on moving forwards promptly. After all, many consumers ar already doing a regular job, and therefore the web site project is additionally to it. All project members ought to be granted comfortable time aboard their traditional duties.

Misunderstandings regarding what a “normal” project entails
Perhaps the foremost typical misunderstanding is that “bugs” (or “issues” as we have a tendency to like better to decision them!) aren't a traditional a part of the event lifecycle. the fact is that they're, particularly once you’re handling complicated systems, innumerable lines of code, and custom needs. the aim of the testing section is for the consumer to figure with North American country to spot and resolve outstanding problems – of that there can be several on an outsized, refined project.

Inaccurate project estimating by the supplier/agency
Estimating the time it takes to develop software package development is notoriously difficult. It’s not a definite science, even armed with extremely elaborated useful and/or technical specifications. though we have a tendency to use tried and tested techniques, they continue to be “estimates only”. Regular project updates make sure that the consumer is unbroken knowing within the event that estimates and actuals are divergent considerably.

3rd Party Systems (integration with)
Integrating (synchronizing, importing/exporting) a brand new system with one or a lot of third party systems will appear easy on the surface, however will generally prove terribly difficult. If such integration is mission-critical for overall project success, then the necessities should be absolutely known and tested/prototyped, and sooner instead of later.

Data migration / population
Similar to the on top of, time and energy is usually underestimated to supply the content, and to populate the new web site therewith content. It’s necessary to completely determine and specify all knowledge that's to be provided for the new site, whether or not it exists nonetheless, who has it, what format it’s in, etc.

Cross-platform compatibility
It’s more durable than you're thinking that to induce websites to appear and performance absolutely on each version of each browser (old and new) on every screen size and orientation (portrait or landscape). The mixtures ar nearly infinite. Optimising for a particular combination will cause de-optimisation for one more. try and make sure that your websites are standards-compliant and optimised for a minimum of the foremost latest/current platforms and versions. however, settle for that excellent consistency across all is nearly not possible.