Work Guidance - Yellow-Spotted-Lizard/SERLER GitHub Wiki

Here are provided guidance materials for working on the project.

Initial ideas about SERLER is on Blackboard

You should read this as a team and get shared understanding with each other and the PO and work out how to incrementally and iteratively deliver the product to Peter you PO so he is blown away! (Using an Agile system of collaborating in a small team - based on Scrum)

For week 7 start of sprint, each team should have...

  1. An initial Product Backlog (PB) using user stories and success criteria - stored in a shared workflow/user story board (e.g. Trello or Asana) with the ones the PO thinks are most important at the top
  2. A list of sized user stories from the PB YOU ARE COMMITTING TO DEFINITELY finishing (code/test/deploy) in sprint 1 (Sprint backlog) - stored in Trello or similar - Sprint plan
  3. A shared Trello board (or similar)to monitor progress - needs some columns that are the main work steps for your team
  4. A burndown chart template - fill in as you do work for each sprint - to monitor progress, identify issues, track team velocity
  5. A system of sharing appropriate information between team members - daily, weekly, sprint, ad hoc
  6. A system to handle changes to product requirements
  7. An initial list of possible risks
  8. An initial list of quality (non-functional) requirements for SERLER
  9. An initial roadmap plan
  10. An initial Team Agreement
  11. A local development environment for every team member based around using Git and sharing code in a shared GitHub repository with appropriate branching structure
  12. A system of continuous coding/testing and integration in the shared code base.
  13. A system to deploy your product in the cloud using Heroku
  14. A system to collect , store and structure evidence for the academic portfolio of evidence and learning

[email protected] should be invited to be part of your shared team artefacts (GitHub, Trello, etc)
[email protected] could be invited to be part of Trello if appropriate

You can use a Blackboard team wiki to gather portfolio evidence