CITS5206 Information Technology Capstone Project 2023

Home About Roles Projects-Offered-2023 Project-Deliverables Professionalism-Assessment Skills-Workshops Resources Unit-Outline

Deliverable 2 Submission (20% individual)

Deadline: 4pm Friday 22 September 2023 (week 8).

Submit Deliverable 2a (submit 1 document per student) in cssubmit. Make sure you choose the correct submission area for this deliverable.

Deliverable 2a: Project Feature (15% individual)

Agile software projects aim to Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. and assert that Working software is the primary measure of progress. [agilemanifesto.org/principles.html]. Deliverable 2 focusses on these two aspects.

Often it is difficult in a team setting to showcase individual contributions. This can be challenging for the instructors (who wish to ensure fair marking), and for students (who wish to ensure that their contributions are "seen"). This assessment item is intended to let you share an individual contribution to your team project.

Each submission should be a single pdf document of no more than 2 pages. No zip, rar, word or other formats please. In the submission you can include text, images, technical drawings or any other information that will convey your contribution. Your presentation should be readable by a general audience: something you could take to an interview to showcase your work. You can also include hyperlinks to additional material (e.g. GitHub, Trello or ms-teams channel) as required.

The contribution you pick for Deliverable 2a must satisfy three things:

  1. It must be a technical contribution to the project (usually a software feature for your project, but it could be a test suite, or software to manage e.g. deployment workflow)
  2. It must be visually engaging and attractive - something you might proudly show to a 3rd party e.g. at a job interview. Part of the rubric will reference an image, so make sure you use one.
  3. It must be your own work. If you worked with someone else on the task, that's fine - but the text with the contribution statement should read "I did X" and not "we did X". The task could be undertaken any time during the project so far (ie up to week 8). The developed code, testing and documentation need not be final, but there should be a clear commits and reviews in GitHub for each contribution. As for deliverable 1, remember that agile methodologies "preference brevity over long documents" [agilemanifesto.org/principles.html]. Provide hyperlinks to project documents where relevant.

Client Review. The group should continue to seek feedback from your client on the project deliverables for this phase and to agree on the plan for the final phase of the project. This client feedback is for formative feedback to improve your project. It does not contribute to your mark for Deliverable 2a.

Submission Submit a summary document (no more than 2 pages) that describes your chosen individual technical contribution. Submit to cssubmit (Deliverable 2a). Submit a single PDF document (no other formats please) including your student number in the file name, e.g., Deliverable2a-22233301.pdf.

Marking Rubric for Deliverable 2a CITS5206-Individual-Deliverable-2a-Marking-Rubric.xlsx

Deliverable 2b P1/P2: Professionalism Assessment (10% individual)

See the web page Professionalism Assessments for the requirements for Deliverable 2b.

Version 2022-06-12 Semester 2 2023

UWA   Department of Computer Science and Software Engineering