ITC309_ Iteration 03 (PRM) - Amel94/ITC309 GitHub Wiki

Resource Allocation System Product Release Milestone

Iteration 03

  1. Key milestones

Milestone Date Iteration start 30/04/2020 Group members Pramodi/Amel

Iteration stop 08/06/2020

  1. High-level objectives and Outcomes

β€’ Participants must be committed to working as a team member to accomplish the goal of the project.
β€’ Frequent interactions will occur during the project.
β€’ Will participants must work collaboratively to assess each other's efforts, inspire and empower each other. β€’ The deadlines for Milestones are carefully observed, checked and reported.

  3. Work Item assignments

Work Item ID Name or keywords of description Status Assigned to (name) Estimated Hours Hours worked Estimate of hours remaining 1.1 A deployment of the 'beta ready' software to the intended deployment environment Incomplete Pramodi 3 0 3 1.2 The conducting of user acceptance tests. Incomplete Amel 2 0 2 2.1 The rectification of any defects or issues uncovered in the acceptance tests Incomplete Pramodi 2 0 2 2.2 The completion of any programmer documentation to the 'hand off' stage. Incomplete Amel 1 0 1

  1. Issues

Name or key words of description Status Notes Issues in Documentations Completed Getting advice from the lecturer Version control issues (GitHub) completed Assign the tasks within the team members and working on that completed Divided tasks between members and work on that

  1. Assessment

Assessment target A deployment of the 'beta ready' software to the intended deployment environment, the conducting of user acceptance tests, The rectification of any defects or issues uncovered in the acceptance tests, The completion of any programmer documentation to the 'hand-off' stage. Assessment date 08/06/2020 Participants Pramodi and Amel Project status Project commencement and project advancement commitment between the team members.

β€’ Assessment against objectives Next meeting time, date and venue has been finalized.

β€’ Work Items: Planned compared to completed

οƒ˜ Every task updated on proper documentations has been planned in the meeting. οƒ˜ An Implementation Model that embodies the final production version of the completed software. οƒ˜ A successful demonstration of the software to the project sponsor resulting in sponsor signoff. οƒ˜ A Test Model including completed user acceptance tests for the final product οƒ˜ Programmer documentation sufficient to pass on to a separate development team to maintain the product. οƒ˜ A Transition Phase Project Status Assessment - which assesses project progress against the overall aims of the project, and against the specific aims of the Transition Phase

β€’ Assessment against Evaluation Criteria Test results

οƒ˜ uploading and updated contents on our group wiki. Moreover, all the contents and resources required for the project progress has been provided. οƒ˜ All the Revised Documents has been corrected by the lecturer. οƒ˜ Alpha and beta User acceptance testing

β€’ Other concerns and deviations

οƒ˜ Issues might arise relating health, personal etc. on the team members which results team meetings failure, unable to contribute one’s part etc. οƒ˜ Communication might be obstructed due to various reasons such as non-attendance in meetings etc. οƒ˜ Project merger may be delayed. οƒ˜ Assigned tasks for each member might be misunderstood