Reference no: EM133859948

Applied Software Engineering

Intro

You now have your team and finalized an idea for the group project - and it's time to lay the foundations! Your Software Requirements Specification (SRS) is where your ideas become clear, structured, and ready for action. Think through your use cases, features, and goals carefully - this document will guide the rest of your project.

Instructions

This is a group task.
Start creating the SRS document for your group project as a team, this document can grow over time. You are expected to refine this document as the project progresses. This initial version will serve as the foundation for Sprint Planning in Task 7.4P.

The SRS should be
Not ambiguous
Straight forward

Please use the guidelines provided to you in Lecture 2 on how to write an SRS. All of the sections given in the Lecture 2 SRS structure are required (all of the 4 sections and their sub sections).

Ensure that all team members are contributing - this is a collaborative document. At the end of the SRS, there should be a brief section titled ‘Member contributions to the SRS' and each member's contributions to the SRS document should be listed. Note that as the SRS evolves, the team may add more contributions. Each member should keep a record of how they contributed to the SRS throughout the project as this will be taken into consideration for their group project contributions (see Task 7.5P rubric).

7.4

Intro

You now have your team and the SRS- it's time to start planning like pros!

This is where the real teamwork begins. Channel your inner project managers and get ready to turn ideas into action!

Instructions
This is a group task.
Step 1

Hold a Sprint Planning Meeting. All members of the team must attend the Sprint Planning Meeting and actively contribute to the planning:

Use the user stories from your SRS (submitted in Task 7.3P) to build your Product Backlog.
Review and prioritise the user stories.
Select a set of stories to implement in Sprint 1 (Weeks 7, 8, and 9).
Decompose each selected user story into smaller, actionable tasks. Each task should:

Be clearly defined (what exactly needs to be done?)
Be independent (can be completed by one person)
Have an estimated time (max 8 hours). If a task seems too large to fit within 8 hours, break it down further.
Include the estimated hours in the task name, e.g., Express bootstrap [2], meaning it should take at the most 2 hours.

Step 2
Create a Trello board for your group using at least the structure "Product Backlog, Sprint 1 Backlog, Sprint 2 Backlog, Doing , Done, Cancelled " and add the tasks you created in Step

1. Remember to make the Trello board public so that unit staff can access it. Here is a sample Trello board:
Each team member should contribute at least ~50 hours of work for each group project.
Each task requires a name, a description, an allocated person.
You must update your board during the sprint. Make sure it reflects your current progress.

Note: Please do not use content from the examples given as is (eg. The StreamFlix SRS), because our submission would then be flagged for high Turnitin similarity and may be cause for an academic integrity allegation.

7.5

Introduction
This task is intended to help you achieve your target grade by making it clear what you need to do in the group project.

By now, you would have had your first sprint planning (for sprint 1) and have a good idea about the app you are building and the features planned.
Now, you need to think about how you will contribute individually, and how that will help you get to your target grade.
Note that there is no separate grade for the project or group grade. Your grades are individual and will depend on 1) the completion of your OnTrack tasks and 2) your individual contributions to the group project.

In this task, you need to meet with your team and discuss your project and your target grade expectations, and plan how each member will contribute. All the members need to be present in the planning sessions.