Group Project

During this period we will run 2 development sprints from 26/01/21 to 12/02/21. There are assignments for this period. From the start of the development sprints the MSwDev, MUXD, and MBusAn students will work together to deliver working software to the industry partner according to their requirements. Teams are expected to use agile methods, so diversions from the provided plans are allowable in consultation with product owners and/or supervisors. The schedule is as follows:

Tuesday 26 January - Tuesday 2 February: Sprint 1

  • Perform daily standups
  • At the end of the sprint, demo your work to the industry partner
  • At the end of the sprint, conduct a team retrospective
  • Submit your learning log for this sprint in the ECS submission system by 23:59 Tuesday 2 February

Wednesday 3 February - Friday 12 February: Sprint 2

  • Perform daily standups
  • At the end of the sprint, demo your work to the industry partner. This takes the form of the group presentation and will be assessed - see Part1: Group presentation below.
  • At the end of the sprint, conduct a team retrospective
  • Submit your group report in the ECS submission system by 23:59 Friday 12 February
  • Submit your learning log for this sprint in the ECS submission system by 23:59 Sunday 14 February

Assignments

The assignments during this period will contribute 25% to your overall course mark. There are three parts to the assessment:

Part 1: Group presentation (5% of course mark, marked as individual)

This will take the form of a demonstration of the project with Q&A from the lecturers and the client. The presentation should include:
  • an overview of the system targeted to the industry partner.
  • a live demonstration of what has been developed.

Due: Demonstrations will be arranged for either Thursday 11 February or Friday 12 February, depending on the team and the client.

Requirements: This will be marked on the following criteria:PresentationCriteria.pdf

Part 2: Group report (15% of course mark, marked as a group)

This is a system report that should be targeted at a knowledgeable software developer who needs to understand the produced system from a technical point of view. It should also be clear who has been contributing to the various parts of the system. The report will be shared with the industry partner, together with produced source code. It should therefore not include reflective considerations about the group work (see Part 3: Individual learning logs). The report will include the work of the MUXD and MBusAn students, but MSwDev students will only be assessed on the technical aspects of the report. The report will be marked on the following criteria:
  • Quality of the report, e.g. language, structure, diagrams etc.
  • Clarity of the presented system, e.g. can a software developer understand the system, e.g. for maintenance or expansion purposes.
  • Appropriate solution to solve the problem, which includes
    • Validation of technical decisions
    • Explanation of known issues, including
      • Explaining that a decision was a suboptimal choice by evaluating the impact and limitations of the choice. If done appropriately this will be as valuable as validating a good decision.

Further guidance on the technical documentation can be found here: TechDoc_Guidance.pdf

Due: 23:59 Friday 12 February

Requirements: Submit as a single PDF or Zip file in the ECS submission system.

Part 3: Individual learning logs (5% of course mark, marked as individual)

One of the purposes of the group projects is to give you an opportunity to learn new technologies and software development methods. Learning is therefore a key component of the project iterations. There are 2 individual learning logs to submit - Learning Log A and Learning Log B:

Learning Log A: Learnings and reflections on development sprint 1
Learning Log A must include:
  • A list of what you have learned during the first sprint.
  • A reflection on how this was achieved (including help received, challenges, issues, surprises).
  • A reflection on how this will impact the way you work in the next sprint.

Due: 23:59 Tuesday 2 February

Requirements: Page limit (max): 2 pages (this includes everything, any further pages will be ignored) AND 12 point font.

How to submit: Upload as Word or PDF in ECS submission system

Learning Log B: Learnings and reflections on development sprint 2
Learning Log B must include:
  • A list of what you have learned during the second sprint.
  • A reflection on how this was achieved (including help received, challenges, issues, surprises).
  • A reflection on how this will impact the way you work on future agile projects.

Due: 23:59 Sunday 14 February

Requirements: Page limit (max): 2 pages (this includes everything, any further pages will be ignored) AND 12 point font.

How to submit: Upload as Word or PDF in ECS submission system
Topic attachments
I Attachment Action Size Date Who Comment
PresentationCriteria.pdfpdf PresentationCriteria.pdf manage 57 K 10 Feb 2021 - 10:43 Main.jennifer Marking Criteria for presentation
TechDoc_Guidance.pdfpdf TechDoc_Guidance.pdf manage 1 MB 03 Feb 2021 - 12:07 Main.jennifer Guidance for system documentation