Project Updates

• 1: Sprint Updates
• 1.1: Sprint 1
• 1.2: Sprint 2
• 1.3: Sprint 3
• 1.4: Sprint 4
• 1.5: Sprint 5
• 1.6: Sprint 6
• 1.7: Sprint 7
• 1.8: Sprint 8

1 - Sprint Updates

1.1 - Sprint 1

• Group members met for the first time & completed introductory activities to get to know each other.
• Create a group Jira board to help organise the planning of the project.
• Get everyone signed up for Jira.
• Get everyone signed up for Github.
• Create a group Google Drive for sharing & creation of documentation.
• Assign overall roles for everyone in the group & their responsibilities going forward.
• Ensure every overall role has a backup person.
• Look at the project brief and decide on an overall timeline of each deliverable.
• Ensure all group members know their way around Jira.
• Jira has been organised in a way that means it works smoothly.
• Jira has ‘Epics’ implemented (timeframes where specific jobs should be completed).
• Started a risk assessment document detailing possible risks the group may face during the project and any - relevant mitigations to solve problems faced.
• Summarised requirements understood from the brief, ahead of the customer meeting later in the week.
• Created a team identity; team name, logo, tagline etc.

1.2 - Sprint 2

• Read through the already given brief and summarised requirements given to us.
• Created a list of questions ahead of the customer meeting, so we can gauge a better understanding from the brief of what exactly is required for us to implement.
• Discussed our method of formatting documentation going forward (markdown/Google Docs).
• Decided on using Google Docs as easier to collaboratively work on, and then can convert to markdown at a later date.
• Met with customer to go over the assignment brief.
• Questions were asked to confirm our understanding of the brief.
• Customer informed us of further requirements that were not listed in the brief.

1.3 - Sprint 3

• 2 Website assets have been created (ocean-bg, map-bg)
• ‘Arrrgh’ logo created (in colour & b&w version for documentation)
• ‘Arrrgh’ logo added to the footer of documentation.
• Requirements list has been completed (both User Requirements & Functional Requirements).
• Game Engine/Library has been decided on (Using IntelliJ and LibGDX)
• Method of writing deliverables decided on (Using Google Docs to collaboratively write, then convert to markdown on GitHub later on).
• Website has been created and a background asset + logo has been added.
• Work has been planned for the following weeks over holidays.

1.4 - Sprint 4

• Drafted a systematic plan for the project; ensuring the plan has all relevant detailed information (key tasks, start/finish dates, priorities etc.)
• Gantt chart created with overview of systematic plan implemented.
• Sprint summaries added to the website.
• Website landing page icons updated to match pirate theme.
• Cleaned up the notes from the customer meeting.
• Drafted a class diagram for the architecture of the game.
• Sea Shanty written & post-reviewed.

1.5 - Sprint 5

• Scheduled catchup meetings for future weeks & booked relevant rooms.
• Created website section for assessment documentation.
• Created website section for sprint updates.
• Written up the requirements for the game formally into assessment documentation.
• Created an abstract representation of the game’s architecture & class structure.
• Drafted an outline for the justification of software development/engineering methods that will be used during the implementation phase.
• Reviewed risk assessment and developed it to explain terminology in detail.

1.6 - Sprint 6

• Ship sprites created for each college (4 in total).
• Port sprites created for each college’s base.
• College, Ship & Port classes created and implemented.
• Basic map layout created.
• Map world sprites created
  • Background tiles (land/water)
• Graphics for main menu & end screen created.

1.7 - Sprint 7

• Updates to account for colour blindness;
  • Added unique shapes/icons on each team’s boat.
  • Added college names above each base on the map.
• Created title screen
• Created losing screen
• Created winning screen
• Added ability to select team for player to play as
• Implemented goals and sub-goals (e.g. visit each college’s base).
• Implemented variables to track game progress (points, time, gold, health).

1.8 - Sprint 8

• Implemented tooltips for each stage of the game.
• Implemented collisions between boats and land that affect health.
• Implemented replay button so the game resets when its over.
• Added game end state when the ship’s health is zero.
• Updated graphics for each game screen.
• Update all documentation to match current state of the game.