Skip to content

ITC309_Iteration 2 (IOCM)

Jump to bottom
pramodi1995 edited this page Apr 9, 2020 · 1 revision

Resource Allocation System Initial Operation Capability Milestone Iteration 02

  1. Key milestones

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

Iteration stop 27/04/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 participant 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 key words of description Status Assigned to (name) Estimated Hours Hours worked Estimate of hours remaining 1.1 A 'beta ready' Implementation Model of the final application Incomplete Pramodi 3 1 2 1.2 Test Model that: demonstrates successful completion of 'alpha' stage user acceptance testing supports user acceptance testing during beta Incomplete Amel 2 1 1 2.1 User Manual that will support end users during beta testing Incomplete Pramodi 2 0 2 2.2 Project Status Assessment Incomplete Amel 1 0 1

  1. Issues

Name or key words of description Status Notes Issues in Push communication method Completed Using a proper push communication method 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 'beta ready' Implementation Model of the final application, Test Model that: demonstrates successful completion of 'alpha' stage user acceptance testing supports user acceptance testing during beta, User Manual that will support end users during beta testing, Project Status Assessment Assessment date 27/04/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.  To develop the product to be sufficiently stable and mature that it can be deployed in the user community for beta user acceptance testing.  To demonstrate that all planned functionality has been developed by successfully passing alpha user acceptance testing  To produce a user manual to support beta testing • 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.  Revised ER diagram and UML diagram corrected by the Lecturer.  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

Clone this wiki locally