Lab Overview


Lab 13 - Version 1.0.0 Release Party!!

Lab Date: Monday, December 2

Lab Objectives

  • Teams will present the 1.0.0 version of their app to the staff and the rest of the lab!

Before Coming to Lab

  • Finish any remaining polish of the app that is needed.
  • Implement any changes from the beta testing and staff feedback as desired.
  • Write up some basic app documentation for Prof. Sherriff and Prof. Horton on how to use your app. Put anything and everything in here that you think we need to grade your app! This could include: help/instructions, information about creating accounts, any test accounts you have that we can use, any key/exciting features you want to make sure that we see and give you credit form, etc. Please place this in the root of your GitHub repository in the README.md file. This needs to include a link to your app!!!
  • Scrum Masters should complete their Scrum Master Report.

Today in Lab

  1. Arrive in lab and get into your teams.
  2. It's final demo day! Each team should set up a station where other students can come by to see their apps.
  3. All students and TAs will walk around, looking at the apps, and enjoying the fact that they are done :-).
  4. TAs will be taking notes on each app to report to Prof. Sherriff and Prof. Horton for final grading.
  5. Submit your herokuapp link and team info here!: https://forms.gle/qXSmpXsD4WABYUKw8

Final Team Evaluation

This is the final evaluations for your team members. This set of evaluations will be weighed heavier than the others and should be representative of how a team member worked throughout the entire semester.

Action Items After Lab

  • Don't touch your code or Heroku!!!!!
more ...

Lab 12 - Beta Testing Complete -> Final Polish Begins

Lab Date: Monday, November 25

Lab Objectives

  • Teams will present the results of their beta testing to the TAs.
  • Staff members will inform the teams of their current project evaluation level per the Project page.
  • Teams will plan any final adjustments to their app based upon the feedback gathered from beta testing and from the staff.

Before Coming to Lab

  • Complete the Beta Testing Report.

Today in Lab

  1. Arrive in lab and get into your teams.
  2. Start with your stand-up meeting! What did you accomplish last week? What will you accomplish this week? What problems do you need help with?
  3. While you are meeting, TAs will come around to review your Beta Testing Report and provide a preliminary evaluation of the project (see below for more information).
  4. Teams should then plan on what things they need to do during this week to finalize their app and get ready for the version 1.0.0 release.

Preliminary Grading

  • TAs will meet with each team for a full demo and discussion.
  • Each team should demo their app, pointing out things that were discovered during beta testing.
  • TAs will then provide a preliminary evaluation of the project along with concrete suggestions on how to move to the next evaluation level. The evaluation levels can be found on the Project page.
  • Any suggestions from the staff are not absolute - that is, depending on how the suggestions are implemented, a team still may not move to the next level. Quality software is still a requirement.
  • During the next lab, the projects will be demoed one more time.
  • Final scoring of the app will be determined by Prof. Sherriff and Prof. Horton after the final lab.

Action Items After Lab

  • Make any changes to your app necessary based upon beta testing and staff feedback.
  • Scrum Masters should complete the Scrum Master Final Report found at: https://drive.google.com/open?id=1jL69JlUKtlFv6-sx2kIXXlVprRUzEzajfmDDp-WyGks
  • The Scrum Master report is due at 2:00 PM, Monday, December 2nd so that it can be shown to the TAs in lab.
  • Also, write up some basic app documentation for Prof. Sherriff and Prof. Horton on how to use your app. This includes Heroku URL, any login information, what each page does, etc - basically anything you think we need to know in order to do a good job grading your app. Point out particularly awesome things you want us to see!
  • Please place this information in the root of your GitHub repository in the README.md file. Failure to do this will result in a reduction of XP for the entire team.
more ...

Lab 11 - Sprint 6 Ends -> Beta Testing Begins

Lab Date: Monday, November 18

Lab Objectives

SPRINT CHECK 6 TODAY

Before Coming to Lab

  • Finish Sprint 6! See the Sprint Check for more information.

Today in Lab

  1. Arrive in lab and get into your teams.
  2. Start with your stand-up meeting! What did you accomplish last week? What will you accomplish this week? What problems do you need help with?
  3. Begin working on your Beta Testing this week. Make sure to look at the Beta Testing Report to see how it should work.
  4. While you are meeting, TAs will come around to perform the Sprint Check for Sprint 6 (see below for more info).
  5. Get ready for Beta Testing!

Sprint Check 6

To earn a Pass on Sprint Check 6, your team must show the following to the satisfaction of the staff:

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • A fully complete app that has been polished to the requirements of the staff.
  • 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.

With each Sprint Check, you will also need to do evaluations for your team members. You must fill out the following form FOR EACH TEAM MEMBER. Thus, you will submit it four or five times at the end of each sprint.

Beta Testing

  • See the Beta Testing Report for information on performing Beta Testing.
  • The Beta Testing Report is due at 2:00 PM, Monday, November 25th so that it can be shown to the TAs in lab.

Action Items After Lab

  • Beta Testing!
more ...

Lab 10 - Sprint 5 Ends -> Sprint 6 Begins

Lab Date: Monday, November 11

Lab Objectives

SPRINT CHECK 5 TODAY

  • 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 (which should be minimal).
  • Remember to do your Sprint Team Evaluations during lab today! - Fill them out at Student Team Evaluation Form @ https://forms.gle/MRJXyDThCGBEVtFn6 !

Before Coming to Lab

  • Finish Sprint 5! See the Sprint Check for more information.

Today in Lab

  1. Arrive in lab and get into your teams.
  2. Start with your stand-up meeting! What did you accomplish last week? What will you accomplish this week? What problems do you need help with?
  3. Begin identifying the requirements you will work on during Sprint 6.
  4. Sprint 6 is primarily a "final polish" sprint. There should be no major stories that will be started here (if there are, you need to refocus what you are doing).
  5. Sprint 6 lasts only one week, but we expect to see some definite UI / polish improvements.
  6. While you are meeting, TAs will come around to perform the Sprint Check for Sprint 5 (see below for more info).
  7. Once you have your requirements pulled for Sprint 6, start working!

Sprint Check 5

To earn a Pass on Sprint Check 5, your team must show the following to the satisfaction of the staff:

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • Show a nearly feature-complete app. All major functionality should be present. The app should basically only need polish and minor features at this point.
  • 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.

With each Sprint Check, you will also need to do evaluations for your team members. You must fill out the following form FOR EACH TEAM MEMBER. Thus, you will submit it four or five times at the end of each sprint.

Sprint 6

For Sprint 6, you should really only be working on "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.

During this sprint, we highly recommend that the Testing Manager begin working on recruiting folks for Beta Testing next week.

Action Items After Lab

  • Work on the items you pulled for Sprint 6!
  • Get ready for Beta Testing!
  • The Configuration Manager needs to begin working on the Configuration Report.
  • The Confguration Report is due is due at 2:00 PM, Monday, November 18th so that it can be shown to the TAs in lab.
more ...

Lab 9 - Sprint 5 Work Continues

Lab Date: Monday, November 4

Lab Objectives

  • No Sprint Check today / No team evaluations today
  • Your team will spend the entire lab meeting and working on Sprint 5
  • TAs will check in with each team to see if there are any questions

Before Coming to Lab

  • Continue working on Sprint 5

Today in Lab

  1. Arrive in lab and get into your teams.
  2. Start with your stand-up meeting! What did you accomplish last week? What will you accomplish this week? What problems do you need help with?
  3. Continue working on Sprint 5!
  4. As you are meeting, TAs will come around to check in with each team to make sure everyone is doing okay.

Sprint 5

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

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • Show a nearly feature-complete app. All major functionality should be present. The app should basically only need polish and minor features at this point.
  • 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 Lab

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

Lab 8 - Sprint 4 Ends -> Sprint 5 Begins

Lab Date: Monday, October 28

Lab Objectives

SPRINT CHECK 4 TODAY

Before Coming to Lab

  • Finish Sprint 4! See the Sprint Check for more information.

Today in Lab

  1. Arrive in lab and get into your teams.
  2. Start with your stand-up meeting! What did you accomplish last week? What will you accomplish this week? What problems do you need help with?
  3. Begin identifying the requirements you will work on during Sprint 5. Sprint 5 ends in two weeks.
  4. We expect that at the end of Sprint 5, you will have a nearly feature-complete app.
  5. While you are meeting, TAs will come around to perform the Sprint Check for Sprint 4 (see below for more info).
  6. Once you have your requirements pulled for Sprint 4, start working!

Sprint Check 4

To earn a Pass on Sprint Check 4, your team must show the following to the satisfaction of the staff:

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • Show a "major feature" of your app. This feature has to be one of the core use cases 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.

With each Sprint Check, you will also need to do evaluations for your team members. You must fill out the following form FOR EACH TEAM MEMBER. Thus, you will submit it four or five times at the end of each sprint.

Sprint 5

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

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • Show a nearly feature-complete app. All major functionality should be present. The app should basically only need polish and minor features at this point.
  • 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 Lab

  • Work on the items you pulled for Sprint 5!
  • Software Architects should begin working on the Architecture Design Document
  • The Architecture Design Document is due is due at 2:00 PM, Monday, November 4th so that it can be shown to the TAs in lab.
more ...

Lab 7 - Sprint 4 Work Continues

Lab Date: Monday, October 21

Lab Objectives

  • No Sprint Check today / No team evaluations today
  • Your team will spend the entire lab meeting and working on Sprint 4
  • TAs will check in with each team to see if there are any questions

Before Coming to Lab

  • Continue working on Sprint 4

Today in Lab

  1. Arrive in lab and get into your teams.
  2. Start with your stand-up meeting! What did you accomplish last week? What will you accomplish this week? What problems do you need help with?
  3. Continue working on Sprint 4!
  4. As you are meeting, TAs will come around to check in with each team to make sure everyone is doing okay.

Sprint 4

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

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • Show a "major feature" of your app. This feature has to be one of the core use cases 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 Lab

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

Lab 6 - Sprint 3 Ends -> Sprint 4 Begins

Lab Date: Monday, October 14

Lab Objectives

SPRINT CHECK 3 TODAY

Before Coming to Lab

  • Finish Sprint 3! See the Sprint Check for more information.

Today in Lab

  1. Arrive in lab and get into your teams.
  2. Start with your stand-up meeting! What did you accomplish last week? What will you accomplish this week? What problems do you need help with?
  3. Begin identifying the requirements you will work on during Sprint 4. Sprint 4 ends in two weeks. This is another major push forward in functionality and we will expect a good bit to be done during this time.
  4. Note that for Sprint 4, you must pull stories that implement a "major feature" in your app. There is obviously some interpretation here, but basically we want to see something working in your app, not just infrastructure.
  5. While you are meeting, TAs will come around to perform the Sprint Check for Sprint 3 (see below for more info).
  6. Once you have your requirements pulled for Sprint 4, start working!

Sprint Check 3

To earn a Pass on Sprint Check 3, your team must show the following to the satisfaction of the staff:

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • Show at least the beginnings of your 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.

With each Sprint Check, you will also need to do evaluations for your team members. You must fill out the following form FOR EACH TEAM MEMBER. Thus, you will submit it four or five times at the end of each sprint.

Sprint 4

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

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • Show a "major feature" of your app. This feature has to be one of the core use cases 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 Lab

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

Lab 5 - Sprint 2 Ends -> Sprint 3 Begins

Lab Date: Monday, September 30

Lab Objectives

SPRINT CHECK 2 TODAY

  • Teams will show their initial setup of their development environment for the project.
  • Teams will then pull their next set of user stories off the backlog for work during Sprint 3.
  • Your first set of team evaluations will be done during lab today! - Fill them out at Student Team Evaluation Form @ https://forms.gle/MRJXyDThCGBEVtFn6 !

Before Coming to Lab

  • Finish Sprint 2! See the Sprint Check for more information.

Today in Lab

  1. Arrive in lab and get into your teams.
  2. Start with your stand-up meeting! What did you accomplish last week? What will you accomplish this week? What problems do you need help with?
  3. Begin identifying the requirements you will work on during Sprint 3. Sprint 3 ends just after Fall Break on October 14 and is your first major push at real functionality. Assign these items to team members in the Project Management spreadsheet.
  4. Note that for Sprint 3, you must pull stories that implement your user model and login. You can have other features as well, but we will explicitly be looking for this for Sprint Check 3. See the information on the Project page regarding Login requirements.
  5. While you are meeting, TAs will come around to perform the Sprint Check for Sprint 2 (see below for more info).
  6. Once you have your requirements pulled for Sprint 3, start working!
  7. Testing Managers should note that the Testing Plan for your team will be due at the end of Sprint 3. See the Testing Plan Template in the Student Resources Google Drive folder.

Sprint Check 2

To earn a Pass on Sprint Check 2, your team must show the following to the satisfaction of the staff:

  • Show that your team has created a base Django app and it is pushed to GitHub. Your team should all be added to the repo (i.e. they have accepted the assignment - we will check this!) and everyone can work with the code.
  • Show you have at least started on some feature of the app. With the quiz this week, we are not looking for a major amount of work to have been completed beyond project setup... but there should be at least something.

With each Sprint Check from here on out, you will also need to do evaluations for your team members. You must fill out the following form FOR EACH TEAM MEMBER. Thus, you will submit it four or five times at the end of each sprint.

Sprint 3

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

  • Show a working app running on Heroku that successfully allows a UVA student to login (with their UVA / Google account).
  • Show at least the beginnings of your UI design and theming.
  • Have unit tests automatically passing on Travis-CI.

More information on Heroku and Travis-CI will be coming soon.

Action Items After Lab

  • Work on the items you pulled for Sprint 3!
  • Testing Managers should work on their testing plans!
more ...