-
Notifications
You must be signed in to change notification settings - Fork 2
Sprint 3
The objective of the milestone should be clearly stated, outlining the purpose of the milestone and the specific goals to be achieved.
The following section includes the list of requirements that were considered for Sprint #3. Moreover, for each, it is indicated whether it was completed or not.
TODO: add functional and non-functional requirements that correlate with the user stories that were defined as part of the sprint planning.
TODO: The deliverables of the milestone should be listed in detail, including the features or functionality that will be completed during the milestone.
TODO: The timeline for the milestone should be clearly defined, including the start and end dates, and any important dates in between.
TODO: Any risks associated with the milestone should be identified, along with any plans for mitigating those risks.
TODO: The communication plan for the milestone should be described, including the frequency and method of communication, and the stakeholders who will be kept informed.
TODO: The roles and responsibilities of each team member involved in the milestone should be clearly defined, including who is responsible for each deliverable and who will be involved in each task.
Terminarium Wiki 2023, DIT113, University of Gothenburg | Chalmers University of Technology, Sweden