CS632 Project Blog - Group 3 Team B

 

Communications

Communications is a critical risk in the project. If communication breaks down the project can halt, features will not be implemented, and team members can lose touch with each other and their deliverables.

·    There is a high risk of communication breakdown

 

Avoidance

·    Proper communication with the project manager at the team meetings

·    Regular visitation of the blog with comments

·    Regular status reporting

·    Regular attendance of team meetings

 

 

Acceptance – There is a risk that the key constituencies will not accept the new system.

• There is a moderate risk of this happening.

 

Avoidance:

• The business users need to be educated and involved in the UAT to ensure that there is full acceptance on the inside of the organization.
• Regular surveys and feedback loops must be established to maintain contact with the business community and affect any changes that may crop up during development.
• Acknowledge business process changes and incorporate them into the scope.

 

Budget

There is a risk that there will be a cost over run or that the business will decide not to support the project after a certain milestone due to cost.

·    This is a moderate risk

 

Avoidance:

·    Stay within the initial scope as much as possible

·    Use several different cost estimation tools

·    Keep clear lines of communications open with business and their support for the project

 

Documentation

Documentation pertains to keeping clear and concise records of the project and its progress.

·    There is a moderate to high risk that proper documentation will not be kept

 

Avoidance:

·    Use standardized modes of communication such as blogs, wiki’s, and COTS software tools such as Sharepoint and Groove to keep track of documentation and versioning.

·    Demand regular feedback from business and project teams and document it.

·    Maintain records of all communications, including emails, IM conversations, and discussion posts that pertain to the project.

 

Time

Time is a risk because a project that takes too long can become irrelevant by the time it is completed.

·    This is a moderate risk

 

Avoidance:

·    Follow the scope closely

·    Ensure any business changed are incorporated into the scope so that the relevance of the project remains current

·    Adopt a development methodology that allows for the delivery of small usable part of the project so that at anytime the project can be halted and still have some use to business