Assessment item 1 Initial Operation Capability Milestone

Value: 40% Due date: 24-Apr-2016

Return date: 17-May-2016 Submission method options Alternative submission method Task

The goals of the Initial Operational Capability Milestone (IOCM) are:

• To demonstrate that product is sufficiently stable and mature to be deployed in the user community for beta testing.

• To demonstrate that all planned functionality has been developed and successfully passed alpha testing • To produce a user manual to support beta testing

The primary task for this assessment is to complete development of your project to 'beta ready' status using an iterative incremental approach. 'Beta ready' is defined as 'feature complete, no known bugs'. In addition to the beta ready software implementation, you are required to produce a User Manual to accompany the beta test software. The manual should include installation and configuration instructions if required for testing, and also document how to use the features implemented in the software. It should be possible for users to install and operate the software with the aid of the manual, without intervention from project developers. While the manual should be comprehensive, it is accepted that some changes may be necessary as a result of user feedback. The submission for IOCM includes the following artefacts

• A 'beta ready' Implementation Model of the final application. (40 marks) • A Test Model that: o demonstrates 'beta' readiness of code (10 marks)

o supports user acceptance testing during beta. (20 marks) • A User Manual that will support end users during beta testing (20 marks) • A Project Status Assessment (10 marks) Assessment item 2

Product Release Milestone Value: 30% Due date: 22-May-2016 Return date: 15-Jun-2016 Submission method options

Alternative submission method Task The goals of the Transition Phase are: • To ensure the project is ready for release into a production environment • To obtain user testing feedback and product acceptance

• To obtain stakeholder acceptance of final project. The main emphasis in the Transition Phase is on deployment of the finished software artefact, completion of user acceptance testing and res

ponding to any defects found. The primary tasks involved in the Transition Phase are: 1. A deployment of the 'beta ready' software to the intended deployment environment. 2. The conducting of user acceptance tests. 3. The rectification of any defects or issues uncovered in the acceptance tests. 4. The completion of any programmer documentation to the 'hand off' stage.

The Product Release Milestone (PRM) represents the completion of the Transition Phase. Deliverables for the PRM include: 1. An Implementation Model that embodies the final production version of the completed software. (30 marks)

2. A successful demonstration of the software to the project sponsor resulting in sponsor signoff.(20 marks) 3. A Test Model including completed user acceptance tests for the final product (30 marks) 4. Sponsor signoff agreeing that the delivered product substantially meets the product Vision. (satisfactory/unsatisfactory)

5. Programmer documentation sufficient to pass on to a separate development team to maintain the product. (20 marks) Due to the limitations imposed by the university semester timetable, beta testing is truncated. An initial round of testing is conducted and all issues and bugs uncovered in that round must be addressed and resolved. This must be verified in a second round of testing. However, once all iossues uncovered in the first round are resolved, the project is deemed complete for submission purposes. It is not required that you address any additional issues uncovered in the second round of testing. Conducting a round of testing and resolving the issues uncovered for the basis of Transition iterations. Please note that if you are developing a real application for a real sponsor, beta testing may continue for as many rounds as required to meet sponsor's requirements. In this context, please note the utility of a clear Vision document to set a well defined end point for the project. Assessment item 3 Project Management Assessment Stream

Value: 30% Due date: Variable

Return date: - Submission method options

Alternative submission method

Task The project management assessment stream assesses a number of different artefacts throughout the semester that help organize development, track project progress, and reflect on project success or otherwise on project completion. Task 1 Project Plan (10 marks)

The project plan is a UP artefact (project document) which gives a high level plan for the iterations for the Construction and Transitions phases of UP (seven iterations in all). The plan accounts for work items and deliverables for each iteration, and works towards having a completed software project by the end of the Transition Phase. The following documents are to be delivered as part of Assignment 1 - LCAM Resubmission.

• An updated Project Plan outlining high level objectives for Construction and Transition Phases Task 2

Iteration Planning & Status Reporting (70 marks) There will be regular fortnightly reporting corresponding to the beginning and end of each iteration. There are four iterations for the Construction Phase and three iterations for the Transition Phase. The general reporting requirements are to devise an iteration plan on the first Monday of an iteration and then to report on the status of the project on the last Friday of the iteration, as shown in the table below. For each iteration for the duration of the project the following artefacts are to be delivered:

• An iteration plan setting out iteration objectives and detailed work items to be completed on the first Monday of each iteration. • An updated iteration plan containing an assessment of progress against the iteration objectives and completion of work items to be completed on the last Sunday of the iteration. Any concerns and deviations from the iteration plan, and the overall project plan should also be identified and discussed. Task 3

Project Post-Mortem (20 marks) The final component in this assessment item is a project review consisting of 8 short answer questions. Answers are expected to be between 100-200 words for each question. Question 1 – How well did your project meet its initial aims? Discuss what modifications were made to the initial aims and why.

Question 2 – How well did the estimated schedule correspond with the actual implementation times? Discuss any differences. Were there any tasks that took a significant amount of time that did not appear in the work item list? Discuss these tasks in terms of project scheduling and budget. Question 3 – What went right? Discuss those aspects of the project that you think went well.

Question 4 – What went wrong? Discuss those aspects of the project that you think went badly. Question 5 – What would you do differently next time? Discuss those aspects you would change in undertaking another project and why.

Question 6 – What have you learnt? Discuss what you have learnt by completing the project. Include discussion of 'people' skills such as negotiation and liaison, as well as project management and technical computing skills. Question 7 – How did the project management framework help or hinder in execution of the project? Discuss the impact of the project management framework adopted for the project. Question 8 – Was the project economic? Discuss the value of the project to the client and compare that with the value of the labour used to produce it. Was the project cost-effective? Discuss what factors might have affected this, and any implications there might be Rationale

The rationale for this assessment is • To finalize the project plan and provide a framework for monitoring project progress, and evaluating final project success.

• To monitor project progress. • To plan and assess each iteration. • To gain an idea of individual contribution to a group project