Risk management plan The table below is the risk management plan lists the possible risks in the project, what it might happen and how to reduce the impact of the risks. RISK THE RISK WHAT CAN HAPPEN? SOURCE HOW CAN THIS HAPPEN? IMPACT FROM EVENT HAPPENING TREATMENT STRATEGIES EFFECTIVENESS OF CURRENT TREATMENT LIKELIHOOD CONSEQUENCE CURRENT RISK RATING ACCEPTABLE / UNACCEPTABLE 1 Development tool is no longer available The open source IDEs decided to be paid IDE is subjected to change or pay Change to another free IDE and apply for student discount if available A marginally effective control Unlikely Minor L Acceptable 2 Changes in development team Team member failed Project 1 Less people in the team Change the development techniques to meet the schedule An inadequate effective control Possible Major H Acceptable 3 More features to be added Client requires more features Project delays or low quality Discuss with supervisor A marginally effective control Possible Major M Acceptable 4 in team Team member the project Project does not meet client Weekly meetings and updates in team A marginally effective control Possible Minor H Unacceptable
5 Client acceptance Client might reject the project Project does not achieve the project goals Keep client involves and discuss with client during Scrum sprints A marginally effective control Rare Major L Unacceptable 6 End user size increases End user size gets larger with time The server and backend might not able to afford Outsourcing An inadequate effective control Possible Moderate M Acceptable 7 Low quality for interface Users do not like the interface on the website Needs some time to design Programmers might need to learn website design A marginally effective control Rare Minor L Acceptable 8 Source code lost Local computer failure Lost the source code Apply version control and keep the backup online A marginally effective control Possible Major L Unacceptable Table 5: Risk management plan Risk Matrix The table below is the risk matrix that highlighted the likelihood of the risk indifferent colours. Red is high, yellow is medium, and green is low. Likelihood Minor consequence Moderate consequence Major consequence
Easy to use Language Assumptions The details which are being entered to check the output are not the actual ones. Test Environment A new server is required for the application for web server, application and the database. Test schedule Task name Start date End date Test planning 17/04/2018 18/04/2018 Initial understands, review, estimation Functionality testing(phase 1) 19/04/2018 20/04/2018 Integration testing(sprint 1) 21/04/2018 22/04/2018 Understand the tests for Sprint 2 27/05/2018 28/05/2018 Functionality testing(phase 2) 28/05/208 29/05/2018 Integration testing(sprint 2) 30/05/2018 30/05/2018 Regression testing(phase 2) 01/06/2018 02/06/2018 Understand the tests for sprint 3 01/09/2018 01/09/2018 Functionality testing(sprint 3) 01/09/2018 02/09/2018 Integration testing(sprint 3) 02/09/2018 02/09/2018 System testing(sprint 3) 03/09/208 05/09/2018 Acceptance testing(sprint 3) 06/09/2018 08/09/2018 Understand tests for sprint 4 12/10/2018 12/10/2018 Functionality testing(sprint 4) 13/10/2018 15/10/2018
Integration testing(sprint 4) 15/10/2018 16/10/2018 System testing(sprint 4) 17/10/2018 18/10/2018 Acceptance testing(sprint 4) 19/10/2018 22/10/2018 Performance testing(sprint 4) 22/10/2018 27/10/2018 Deployment 30/10/2018 30/10/2018 Deliverables Deliverables For Test plan Team members Traceability matrix Team members Test result Client, Team members, Supervisor Software Development Milestones Task Name Start Date End Date Duration (Days) Milestone Sprint 1 1/03/2018 6/05/2018 66 Prototype I Create Navigation bar 1/03/2018 4/03/2018 3 Create Course Page 4/03/2018 7/03/2018 3 Design page structure 7/03/2018 13/03/2018 6 Create CRUD for Course 13/03/2018 20/03/2018 7 Create CRUD for Assessment 20/03/2018 27/03/2018 7 Create Tutor Page 27/03/2018 29/03/2018 2 Create CRUD for Tutor. Database with all the entities and values. 29/03/2018 5/04/2018 7