Home > Undergraduate > Professional Computing 3200 > Project > Sprint 2  

 

Definition of Sprint 2

Given the Agile methodology that we are using in this unit, there is some abiguity in the deliverables due at the end of this Sprint. In essence, what your team should deliver (or demonstrate, as appropriate) are the set of interim goals you proposed at the end of Sprint 1. While the final system has to be delivered on the Client's system, for this Sprint's deliverables it is sufficient that the goals be demostrated on the development platform.

In addition, the team should submit the minutes of a Project Retrospective. This comes in two parts. The first is where the team has demostrated the project as it currently stands to the Client. The minutes should record the team's and the Clients thoughts about the system. The second part records the team's thoughts (without the Client) about how the project is tracking versus the goals that were set, and in particular how the project is tracking with regard to the expected timeline given on the timesheet. Don't worry if your estimates are out; that is part of the learning experience. Just discuss what you expected, what you observed and why any discrepancies you observe may have arisen.

Finally, the team has to create the final set of stories to see the project to completion. If the team is tracking ahead of where it expected to be at this stage, the new stories could include extensions to the project as originally envisaged. On the other hand, if difficulties have emerged, the new stories may involve reduction in project scope. Both situations need to be negotiated with the Client.

 Group Submission: Each team must submit:

  • Any documents (if required by the Client) for Sprint 2 to the client.
  • Descriptions of the new stories sent to Client via email and Project Auditor via OneDrive.
  • Minutes of the Client Project Retrospective and the internal Project Retrospective should be sent to the Project Auditor via OneDrive. (They can be combined into a single document for convenience.) The Client Project Retrospective should also be sent to the Client.

 Individual Submission:  As in Sprint 1, in addition to your participation in the team submission, you must also submit a reflection on your experiences in the unit thus far. To guide you in this task, a form (a MS-Word document) can be found here. Complete the form (MS-Word or PDF only, please) and submit the completed form via cssubmit. As with Sprint 1, CITS5206 Teams please use the CITS3200 submission portal.

Please also remember to log into your SPARK+ account and complete the group assessment survey for this sprint.



Department of Computer Science & Software Engineering
The University of Western Australia >
Last modified: 1 July, 2020
Created by: Michael Wise
UWA