Possible layout for non-linear models… this will be your implementation chapter.

Initial Requirements

• A list of artefact goals based on the literature review and any which were directed by the company. These are likely to be in a user story format.
• Requirements need to be prioritised if you are using a SCRUM approach

Sprint One: Initial requirements

• Requirements of sprint
  • What is the purpose of the sprint
    • Tell me what you will do and why
  • Make a list of items like:
    • Objectives
    • Deliverables or outcomes
    • Initial requirements or goals for this sprint
• Implementation (create and test)
  • Testing
    • Test for feasibility and suitability
    • Test to prove it work and/ or test to refine it
    • Must provide testing evidence and display in graph where possible
• Decision making (Scrum)
  • Consider using a SWOT Analysis (Strength, Weaknesses, Opportunities, and Threats)
  • Determine requirements for the next sprint
  • Update design diagrams and documents
  • Update list of requirements
  • Confirm which top level (report) success criteria\ objectives were achieved.

Sprint Two: Interface Specification

• What is the purpose of the sprint
  • Tell me what you will do and why
  • Make a list of items like:
    • Objectives
    • Deliverables or outcomes
    • Initial requirements or goals for this sprint
• Implementation (create and test)
  • Testing
    • Test for feasibility and suitability
    • Test to prove it work and/ or test to refine it
    • Must provide testing evidence for this sprint and display in graph where possible
• Decision making (Scrum)
  • Consider using a SWOT Analysis (Strength, Weaknesses, Opportunities, and Threats)
  • Determine requirements for the next sprint
  • Update design diagrams and documents
  • Update list of requirements
  • Confirm which top level (report) success criteria\ objectives were achieved.

Sprint Three: Database Development

• See sprint two