Risk Management

Development Risks

Risk: Fail to deliver working product
Solution: If team will be unable to deliver working product at the end of the development cycle, development time will be extended to meet the development requirement and Back Up budged will be used to provide funding.

Risk: Fail to manage development cycle.
Solution: If problem in management will occur, team meeting will be called to discuss occurred problem and find solution, which may include change of Team Leader, hire additional help for the management of the project or .

Risk: Fail to meet target dates.
Solution: If team will fail to meet target dates, feature with low priorities will be cut down. Later it can be added as a patch or add on to the game. To deliver as much features as possible extra time for development might be requested by the team. No more then two weeks of extra time will be requested during this project.

Risk: Fail to meet target budget.
Solution: If team fail to fit into the target budges, a Back Up budget will be used to continue development. If it will be inefficient, extra budget might be requested from the publisher. No more then 10% extra budget will be requested during this project. To fit into the allowed budged some low priority feature may be cut down.

Risk: Fail to fulfil project objectives.
Solution: If game will be released without all planned feature, an additional patch or add-on can be released to bring back missing parts. As game is online it will have automatic update system, therefore delivery of new patcher and features will be fast and easy.

Disaster Recovery/Contingency Plan

 

List of the potential threats:

 

 

 

Detailed set of procedures for preventing and recovering

 

Disaster	Resources	Recovery	Cost/Time
Fire, Flood, Tornado/Earthquake	Have all the insurance documentation ready for claiming Have back ups data ready for use as soon as possible IF: Office is out of use, have a plan to find new or temporary office. Have an extra workstation stored off site.	File insurance as soon as possible to cover the damages. Fix the office problem: Find new location and if needed purchase new furniture Bring extra workstation to new site and install it Get the back ups Restore back ups Wait until insurance will be claimed and all damages to the building and office can be restored Order new workstations and server Build new network Restore all back ups on the new network Insure all Resources for new recovery is ready	One extra workstation stored offsite - $2000 Rent new office as soon as possible - $200 per week Claim insurance - $500 – up to few weeks Put together temporary office – 2 days Get new workstations and server – 2 days Recover fully – 1-3 weeks (depends on insurance claim)
Theft	Have an extra workstation stored off site. Have all the insurance documentation ready for claiming Have back ups data ready for use as soon as possible	File insurance as soon as possible to cover the damages. Bring extra workstation and set it up Brink back ups and restore them on new extra workstation Order new workstations and server Build new network Restore all back ups on the new network Insure all Resources for new recovery is ready	One extra workstation stored offsite - $2000 Claim insurance - $500 – up to few weeks Put together temporary workstation – 2 days Get new workstations and server – 2 days Recover fully – 1-3 weeks (depends on insurance claim)
Virus/Spy-ware	Have back ups data ready for use as soon as possible Anti-virus software and anti-spyware	Run anti-virus software (must be fully updates) Run anit-spyware (must be fully updates) IF: System still act strangely re-install all software Get back ups ready for use If any data lost or corrupt restore all back ups Insure all Resources for new recovery is ready	Buy anti-virus and anti-software products - $150-$200 Run all diagnostics (anti-virus and anti-software) – up to 1 day Re-install all software – 1day Restore back ups – 1-2 hours
System failed	Have back ups data ready for use as soon as possible Have an extra workstation stored off site.	Replace failed system with extra workstation Bring all data to temporary system (from back up or hard drive of failed system) Purchase new system Replace temporary system with new system Restore all data (from back up or hard drive) Remove temporary system Insure all Resources for new recovery is ready	Replace failed system with extra workstation – 2 –5 hours Bring all data to temporary system – 2 hours Purchase new system - 1- 2 days - $2000 Replace temporary system with new system – 5 – 7 hours Restore all data – 2-4 hours Remove temporary system – 1 hour One extra workstation stored offsite - $2000

 

 

Test Strategy

 

Testing of the Sand Auto War will occur in the series of rounds. First round is when testers will start on testing of the software. When testing is finish or any of exit exiting criteria is met, all documented defects will be submitted to the development team for the fixing. After testing team will receive new version of the software new round of testing will occur. At this point all the technical documents and testing plan changes have to be made. New test round is setup and performed again. Same steps if followed until no errors found, development team or the project manager says that testing is complete.

 

Below is an example of the one round of the testing process.

o       Black box testing technique will be used.

o       Start of the testing – tester will start testing each form one by one.

o       All the defects have to be documented.

o       All documents submitted to the Tester Team Leader.

o       At this stage testing might stop if any exiting criteria are met.

o       Tester Team Leader submits documented defects to the development team for the correction purposes.

o       After receiving new version of the program new round of testing will start.

o       Continue until of the exit criterion met.

 

Tester Assignments / Roles and Responsibilities

 

Name	Role	Responsibility	Position
Daniel Golitsyuski	Tester Team Leader	§         Testing of the forms. §         Documentation of the testing. §         Communication with management and development team. §         Changes in Test Plan. §         Management of the testing process.	Full-time
N/A (will be hired closer to testing period)	Tester	§         Testing of the forms. §         Documentation of the testing.	Casual
Michael Chivers	Tester Analyst	§         Testing of the forms. §         Documentation of the testing. §         Changes in Test Plan. §         Make sure all the testing done with company standards. §         Coordinate QA activities for assigned projects. §         Develop any scripts or new documentation for the testing.	Full-time

 

Test Schedule

 

There will be no day-to-day schedule for the testing, for the reason that testing forms and material will be changed depending on the occurred errors. Each new day or round of testing Tester Team Leader with help of the development team leader will analyse what have to be tested first, which errors are most critical and develop rough plan test for the upcoming day or round.

 

Testers and development team possibly will have to work over time to meet the test schedule.

 

All the testing will start when developing team will submit first version of the SAW. Testing team will be given a week to complete the test of the game. If testing is not complete in given time, it will be stoped nevertheless.

 

At the end of every day all defect logs and reports will be submitted to the Tester Team Leader for evaluation. He will created plan for next day of testing and by communication with development team, analyse what have to be tested next.

 

At the end of the last day of the week of testing all the reports and logs have to be documented and submitted to the project manager.

 

Test Constraints

 

o       Testing cannot continue past submission date.

o       Testing cannot continue if exit criteria are met.

Bug Reporting / Problem Reporting

 

Bug reporting and tracking will consist of following:

 

When new bug is found it will be documented in the defect log. There will be one defect log for each bug or error. Tester will use multiple defect logs to document all found bugs. Then this defect log will be given to the development team to work on it. After error is fixed, developer fills the result sheet where he specified what have been done to fix each error. Then result sheet goes to the Tester Team Leader, who will analyse it and make sure that everything is correct. By doing so, he can make sure that there no misunderstanding between developer and tester. For example if error wasn’t error at all or by some means should be overseen. Tester Team Leader will know about it and will inform all the team members or when tester think that this error should be fixed, Tester Team Leader can communicate with developer to resolve the conflict. After each round of testing tester fill the Test log where he documents everything what happed during the round of testing and Tester Team Leader will make sure that every bug recorded is fixed or at least have been review by the development team. Test log then will be submitted to the project management for further analyses and testing control.

 

Hence Tester Team Leader will be one responsible to make sure that all defect logs and result sheet is filled correctly. Test log will contain all the information collected from defect log and result sheet. This way it will be easily seen what have been fixed and what have been missed.

 

At the end of each week Tester Team Leader will communicate with developers to gather information on what has been fixed and what will be fixed soon. This way no conflict will occur between test team and development team.

 

 

 

 

 

Bug Log – Developers

 

Bug Log – Developers
Problem Name:			ID:
Description:
Developer Name		Priority:	1.High
			2.Moderate
Date:			3.Medium
			4.Low
Further Action
	Developer Signature:

 

 

Bug Log – Tester

 

Bug Log – Tester
Problem Name:			ID:
Steps to Problem:
Error message:		Priority:	1.High
			2.Moderate
Date:			3.Medium
			4.Low
Assigned To:
Fixed:	Yes:	No:
Follow On:
	Developer Signature:_________________________

Maintenance Service Log

 

Maintenance Log
Version Number:		ID:
Description:
Name of the class/file/function:
Assigned To:
Date:
Additional Notes:
	Developer Signature:_________________________