In this course, students work in groups to finish the development of their CAPSTONE projects. These projects were proposed and initialized in the BTS530 course. Now, students will continue to add features to their projects, during the course of four sprints, to meet all requirements that were previously set. Afterwards, the full project will be presented to an audience, during the course of two days of Final Presentations.
| Item | Qtd | Marks |
|---|---|---|
| Documentation (Issues) | 4 | 2%/8% |
| Documentation (Weekly Scrum) | 4 | 2%/8% |
| Documentation (PRs) | 4 | 2%/8% |
| Meeting Performance | 8 | 2%/16% |
| Implementation | 4 | 10%/40% |
| Final Presentation | 1 | 20%/20% |
During this week, a lecture will be presented and recorded. In this lecture, the instructor will explain all evaluation criteria for this course. Moreover, new groups will be managed, and existing groups will be given an opportunity to re-evaluate their prototypes and update their documentation.
SlidesPrior to sprint planning meetings, all students must create issues on their teams repositories. During meetings, clear expectations are set with regards to what needs to be implemented for each issue to be considered succesful.
During student help weeks, groups are welcomed to request extra meetings. These meetings can be used to clarify expectations or to suggest changes on what needs to be implemented. At this time, each student must update their issue with a weekly scrum.
Prior to sprint review meetings, all students must have closed their issues with proper comments on the original issue, and merged their work into their team's main repository (or repositories). During the meetings, each student demonstrates the work that they have done during the sprint.
Prior to sprint planning meetings, all students must create issues on their teams repositories. During meetings, clear expectations are set with regards to what needs to be implemented for each issue to be considered succesful.
During student help weeks, groups are welcomed to request extra meetings. These meetings can be used to clarify expectations or to suggest changes on what needs to be implemented. At this time, each student must update their issue with a weekly scrum.
Prior to sprint review meetings, all students must have closed their issues with proper comments on the original issue, and merged their work into their team's main repository (or repositories). During the meetings, each student demonstrates the work that they have done during the sprint.
Prior to sprint planning meetings, all students must create issues on their teams repositories. During meetings, clear expectations are set with regards to what needs to be implemented for each issue to be considered succesful.
During student help weeks, groups are welcomed to request extra meetings. These meetings can be used to clarify expectations or to suggest changes on what needs to be implemented. At this time, each student must update their issue with a weekly scrum.
Prior to sprint review meetings, all students must have closed their issues with proper comments on the original issue, and merged their work into their team's main repository (or repositories). During the meetings, each student demonstrates the work that they have done during the sprint.
Prior to sprint planning meetings, all students must create issues on their teams repositories. During meetings, clear expectations are set with regards to what needs to be implemented for each issue to be considered succesful.
During student help weeks, groups are welcomed to request extra meetings. These meetings can be used to clarify expectations or to suggest changes on what needs to be implemented. At this time, each student must update their issue with a weekly scrum.
Prior to sprint review meetings, all students must have closed their issues with proper comments on the original issue, and merged their work into their team's main repository (or repositories). During the meetings, each student demonstrates the work that they have done during the sprint.