About Myself

Brazilian, Canadian, and French

Father of two little honey badgers tasmanian devils beautiful children

Electrical Engineer by trade - ScrumMaster by option

+20 years of experience in Software Development

Teaching CAPSTONE Project courses since 2014

Technologies

→ Meetings at: MS Teams

→ For reaching out: Teams or email

→ For asynchronous messaging: Blackboard

→ For submissions and tracking issues: Github

Sprints

Each sprints consists of three weeks:

Sprint Planning: Discuss sprint plans

Student Help: Per request

Sprint Review: Demonstrate functionality

Sprint Planning

Each group needs only to attend their own meeting

Prior to the meeting: Create issues on GitHub using this layout

Elmo: further questions can be asked over Teams

Be prepared!!!

Student Help

Time provided for students to work on their tasks

The instructor will be available for help via email or Teams

Each student must update their issue with a comment, called weekly scrum, in which current progress is reported. See this example

Sprint Review

Each group will present the tasks they worked on during that sprint

Focus will be on demonstrating functionality

Missing features and bugs will result in deductions

At this point, each student must close their issue with a comment, called Retrospective. See this example

Also, document your PR! Or, link it to the issue.

Final Presentation

Each group will present the whole project in a formal setting

Cover all functionality, from all sprints

Feel free to talk about tech, but focus on end-user

Imagine you are selling it!

Evaluation - Final

Implementation 10 marks

Presentation 10 marks

Evaluation

Marks are NOT group based

A clear division of the work will be discussed during Sprint Planning

Further deductions might occur:

  → Missing meetings

  → Violating the WA

  → Not delivering