In this course, we will collaborate in groups to initiate the development of our CAPSTONE projects. Students will simultaneously create a prototype/demo for a proposed system while documenting the entire process. This prototype/demo will serve as the foundation for the subsequent project implementation course, BTS630.
There will be no regular lectures in this course. Rather, each group will have a sequence of meetings with their instructor over the course of four Scrum Sprints. These meetings will take place at timeslots chosen by the students. Attendance is mandatory, but students can choose to meet either in person via MS Teams.
It is essential to note that the prototype/demo will not include all the functionality expected in the final project implementation. It may exclude certain required scenarios and incorporate several simplifications, which will be refined in BTS630. Nevertheless, it is crucial to understand from the outset that the prototype/demo represents a functional version of the final product. In other words, the majority of the work you do in this course will involve coding and documenting your code.
| Item | Qtd | Marks |
|---|---|---|
| Documentation | 4 | 8%/32% |
| Meeting Performance | 8 | 2.5%/20% |
| Implementation | 4 | 12%/48% |
In this lecture, students are welcomed to the BTS530 course. The course delivery format and evaluation criteria are then discussed. Finally, the expected behavior for
This week, we will have Sprint Planning meetings. Before the meetings, all students must create issues in their team's repositories, following the provided template. During the meetings, clear expectations will be set regarding what needs to be implemented for each issue to be considered successfully completed.
This week is dedicated to allowing students to work on the issues they have assigned to themselves. Groups are welcome to request additional meetings during this week if needed. These meetings can be used to clarify expectations or suggest changes to what needs to be implemented. During this time, each student must update their issue with a comment entitled weekly scrum.
This week, we will hold Sprint Review meetings. Before these meetings, all students must resolve their issues, close them with a comment entitled Sprint Retrospective (following the provided template), and merge their work into their team's main repository. During the meetings, each student must demonstrate the work they have completed during the sprint.
This week, we will have Sprint Planning meetings. Before the meetings, all students must create issues in their team's repositories, following the provided template. During the meetings, clear expectations will be set regarding what needs to be implemented for each issue to be considered successfully completed.
This week is dedicated to allowing students to work on the issues they have assigned to themselves. Groups are welcome to request additional meetings during this week if needed. These meetings can be used to clarify expectations or suggest changes to what needs to be implemented. During this time, each student must update their issue with a comment entitled weekly scrum.
This week, we will hold Sprint Review meetings. Before these meetings, all students must resolve their issues, close them with a comment entitled Sprint Retrospective (following the provided template), and merge their work into their team's main repository. During the meetings, each student must demonstrate the work they have completed during the sprint.
This week, we will have Sprint Planning meetings. Before the meetings, all students must create issues in their team's repositories, following the provided template. During the meetings, clear expectations will be set regarding what needs to be implemented for each issue to be considered successfully completed.
This week is dedicated to allowing students to work on the issues they have assigned to themselves. Groups are welcome to request additional meetings during this week if needed. These meetings can be used to clarify expectations or suggest changes to what needs to be implemented. During this time, each student must update their issue with a comment entitled weekly scrum.
This week, we will hold Sprint Review meetings. Before these meetings, all students must resolve their issues, close them with a comment entitled Sprint Retrospective (following the provided template), and merge their work into their team's main repository. During the meetings, each student must demonstrate the work they have completed during the sprint.
This week, we will have Sprint Planning meetings. Before the meetings, all students must create issues in their team's repositories, following the provided template. During the meetings, clear expectations will be set regarding what needs to be implemented for each issue to be considered successfully completed.
This week is dedicated to allowing students to work on the issues they have assigned to themselves. Groups are welcome to request additional meetings during this week if needed. These meetings can be used to clarify expectations or suggest changes to what needs to be implemented. During this time, each student must update their issue with a comment entitled weekly scrum.
This week, we will hold Sprint Review meetings. Before these meetings, all students must resolve their issues, close them with a comment entitled Sprint Retrospective (following the provided template), and merge their work into their team's main repository. During the meetings, each student must demonstrate the work they have completed during the sprint.
To pick a timeslot, you will need to use a unique group ID that will be provided to your group via email. Ensure that you confirm with your teammates that the selected timeslot works for everyone. Students are expected to attend all meetings, either in person or online using a computer capable of demonstrating their work.