Online Team/TA Meeting 1 - Team Check-in

Week of: Monday, March 23

Objectives

  • No Sprint Check / No team evaluations
  • TAs will check in with each team to see if there are any questions

Before Meeting With Your TA

  • Continue working on Sprint 4

During the Team Meeting

  1. The goal of this meeting is for the TAs to get a feel for how everyone is doing and to help you prioritize moving forward.
  2. Remember: focus on core functionality!

Sprint 4

Remember, your goals for Sprint 4 are (at a minimum):

  • Show a working app running on Heroku that successfully allows login through a third-party API, such as Google or Facebook.
  • Show a "major feature" of your app. This feature should be a core use case of your app.
  • Show a more refined UI design and theming.
  • Show a full build process - pushing to GitHub's master branch triggers a Travis-CI test run that then deploys to Heroku.
  • Have all unit tests automatically passing on Travis-CI.

Action Items After The Meeting

  • Work on the items you pulled for Sprint 4!
  • Software Architects should begin working on the Architecture Design Document which is due next week by Monday at 2:00 PM EDT!
more ...

Online Team/TA Meeting 2 - Sprint Check 4

Week of: Monday, March 30

Objectives

SPRINT CHECK 4 THIS WEEK

  • Teams will show their work on Sprint 4 to the TAs to earn Sprint Check XP.
  • Teams will then pull their next set of user stories off the backlog for work during Sprint 5.
  • Remember to do your Sprint Team Evaluations sometime this week! - Find links for all of your evals in the Posted Feedback tool on the left side menu in Collab!

Before Meeting With Your TA

  • Finish Sprint 4! See the Sprint Check for more information.
  • Scrum Masters need to complete the Sprint Report for Sprint 4 and submit to Gradescope! Find the template here: https://drive.google.com/open?id=1n5n2Ti7h7shchTe67Hf_NzDTchJiaEObgQqB7LwrIUA
  • As long as the report is in to Gradescope before your meeting, it will be counted as "on time." If you forget or there are issues, talk to your TA.

During the Team Meeting

  1. The goal of this meeting is for the TAs to do your Sprint Check for Sprint 4 and to see how the team is doing.
  2. The TA will go over your sprint report with you while you demo your current system, either via screen share or by sending a link to the TA.
  3. Remember: focus on core functionality!

Sprint 4

Remember, your goals for Sprint 4 are (at a minimum):

  • Show a working app running on Heroku that successfully allows login through a third-party API, such as Google or Facebook.
  • Show a "major feature" of your app. This feature should be a core use case of your app.
  • Show a more refined UI design and theming.
  • Show a full build process - pushing to GitHub's master branch triggers a Travis-CI test run that then deploys to Heroku.
  • Have all unit tests automatically passing on Travis-CI.

Sprint 5

For Sprint 5, you should target the following things at a minimum:

  • Show a working app running on Heroku that successfully allows login through a third-party API, such as Google or Facebook.
  • Continue working on your core functionality and make obvious, observable progress from the last sprint.
  • Show a more refined UI design and theming.
  • Show a full build process - pushing to GitHub's master branch triggers a Travis-CI test run that then deploys to Heroku.
  • Have all unit tests automatically passing on Travis-CI.

Action Items After The Meeting

  • Work on the items you pulled for Sprint 5!
more ...

Online Team/TA Meeting 3 - Sprint Check 5

Week of: Monday, April 6

Objectives

SPRINT CHECK 5 THIS WEEK

  • Teams will show their work on Sprint 5 to the TAs to earn Sprint Check XP.
  • Teams will then pull their next set of user stories off the backlog for work during Sprint 6.
  • Remember to do your Sprint Team Evaluations sometime this week! - Find links for all of your evals in the Posted Feedback tool on the left side menu in Collab!

Before Meeting With Your TA

  • Finish Sprint 5! See the Sprint Check for more information.
  • Scrum Masters need to complete the Sprint Report for Sprint 5 and submit to Gradescope! Find the template here: https://drive.google.com/open?id=1n5n2Ti7h7shchTe67Hf_NzDTchJiaEObgQqB7LwrIUA
  • As long as the report is in to Gradescope before your meeting, it will be counted as "on time." If you forget or there are issues, talk to your TA.

During the Team Meeting

  1. The goal of this meeting is for the TAs to do your Sprint Check for Sprint 5 and to see how the team is doing.
  2. The TA will go over your sprint report with you while you demo your current system, either via screen share or by sending a link to the TA.
  3. Remember: focus on core functionality!

Sprint 5

For Sprint 5, you should target the following things at a minimum:

  • Show a working app running on Heroku that successfully allows login through a third-party API, such as Google or Facebook.
  • Continue working on your core functionality and make obvious, observable progress from the last sprint.
  • Show a more refined UI design and theming.
  • Show a full build process - pushing to GitHub's master branch triggers a Travis-CI test run that then deploys to Heroku.
  • Have all unit tests automatically passing on Travis-CI.

Sprint 6

For Sprint 6, you should be completing your core functionality and putting on your "finishing touches." We expect that your app will still be working at the end of Sprint 6 (as it was from Sprint 5), but any remaining suggestions from the staff should be addressed.

At the end of Sprint 6, will we score you on both Sprint 6 (5000 XP) as normal, along with your Beta version of your app. This will count for half of your overall project score (25000 XP). To earn these points, you need to have a feature complete, working app ready for Beta testing. It does not need to be your final version - we expect changes and polish to be done over the last two weeks! This is your incentive to have a fully working app at this point in order to do successful beta testing.

Action Items After The Meeting

  • Work on the items you pulled for Sprint 6!
  • The DevOps Manager needs to begin working on the DevOps Report which is due next week by Monday at 2:00 PM EDT!
more ...

Online Team/TA Meeting 4 - Sprint Check 6

Week of: Monday, April 13

Objectives

SPRINT CHECK 6 THIS WEEK

  • Teams will show their work on Sprint 6 to the TAs to earn Sprint Check XP.
  • Teams will then get ready for Beta Testing this week.
  • Remember to do your Sprint Team Evaluations sometime this week! - Find links for all of your evals in the Posted Feedback tool on the left side menu in Collab!

Before Meeting With Your TA

  • Finish Sprint 6! See the Sprint Check for more information.
  • Scrum Masters need to complete the Sprint Report for Sprint 5 and submit to Gradescope! Find the template here: https://drive.google.com/open?id=1n5n2Ti7h7shchTe67Hf_NzDTchJiaEObgQqB7LwrIUA
  • As long as the report is in to Gradescope before your meeting, it will be counted as "on time." If you forget or there are issues, talk to your TA.

During the Team Meeting

  1. The goal of this meeting is for the TAs to do your Sprint Check for Sprint 6 and to see how the team is doing.
  2. The TA will go over your sprint report with you while you demo your current system, either via screen share or by sending a link to the TA.
  3. The TA will then give an overall scoring of the app at this point, which Sherriff will verify later.

Beta Version Score

After lab, with consultation from the TA staff, Prof. Sherriff will award up to 25000 XP (from the 50000 XP for your project) for having a fully-featured, working app at this point. It does not need to be your final version - we expect changes and polish to be done over the last two weeks!

Beta Testing

  • See the Beta Testing Report for information on performing Beta Testing.
  • TESTING MANAGERS - Go look at the spreadsheet found here: https://docs.google.com/spreadsheets/d/1BanhCTuYEQ-dycLdJnoJddUqGexoKQvrP2RwMytiQwk/edit#gid=0 (it is also in the Student Resources folder).
  • Find your name in the sheet. The two teams listed as "Beta Test Team 1" and "Beta Test Team 2" are the teams that will be beta testing your team's app. Look up the testing managers for those teams and provide them with the info on how to do the beta testing of your app so they can share with their team.
  • EVERYONE - Look through the list of teams under "Beta Test Team 1" and "Beta Test Team 2" and find your team name. The testing manager to the left will be the person contacting you about how to do the beta testing.
  • The Beta Testing Report is due before your meeting next week!
  • TESTING MANAGERS - Once everyone has finished testing your app, report who successfully completed the beta testing here so I can give them attendance XP: https://forms.gle/ewSXsJd6aKYw9DwCA

Action Items After The Meeting

  • Beta Testing!
  • Testing Managers should begin working on the Beta Testing document as soon as possible!
more ...

Online Team/TA Meeting 5 - Beta Testing Reports

Week of: Monday, April 20

Objectives

  • Teams will discuss the results of their beta testing with the TA, explaining what they will do to finish up over the next week.
  • No evaluations this week. Final team evaluations will be next week.

Before Meeting With Your TA

  • Finish the Beta Testing document and turn it in!
  • Finish beta testing for other teams!
  • Testing managers need to make sure to report who all successfully completed their beta testing!

During the Team Meeting

  1. The goal of this meeting is to discuss the results of the beta testing with the TA and determine what needs to happen between now and meeting with Sherrif for the final demo.
  2. TAs should take detailed notes and send those notes to Sherriff to reference during the demo!
  3. If your team has not done so yet, select a time to demo your final project to Sherriff over Zoom!

Sign up here!: https://docs.google.com/document/d/1GLrDPofN-wdwbAbKJdnpSacb5nbRIsFfFGpjuxXRPjM/edit?usp=sharing

Action Items After The Meeting

  • Finish up your app!! :-)
more ...

Online Team/TA Meeting 6 - Final Projects Due!

Week of: Monday, April 27

Objectives

  • Demo your final app for Sherriff!

Before Meeting With Prof. Sherriff

During the Demo w/ Sherriff

  1. During the demo, focus on showing off your major functionality. (For example, show the stuff that makes your app yours... not necessarily going through all the ins-and-outs of logging in...)
  2. The meeting will only take around 15 minutes.
  3. Sherriff will score the app that day and post the XP later that night! (hopefully...)

Action Items After The Meeting

  • Celebrate the end of CS 3240!
more ...