Lab Overview


Lab 13 - Version 1.0.0 Release

Lab Date: Monday, April 29

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 on how to use your app. Please place this in the root of your GitHub repository in the README.md file.
  • Scrum Masters should complete their Scrum Master Report.

Today in Lab

  1. Arrive in OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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 for final grading.

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.

Each role has a different evaluation form with different questions. Fill out the appropriate form for every other person in your team.

PLEASE read the scales before answering the questions! 10 means doing well, 0 means doing poorly!

Action Items After Lab

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

Lab 12 - Beta Testing Complete -> Final Polish Begins

Lab Date: Monday, April 22

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 OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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 absolulte - 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 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
  • Write up some basic app documentation for Prof. Sherriff on how to use your app. Please place this in the root of your GitHub repository in the README.md file.
more ...

Lab 11 - Sprint 6 Ends -> Beta Testing Begins

Lab Date: Monday, April 15

Lab Objectives

  • Teams will present their beta apps to the TAs.
  • Teams will then prepare for public beta testing this week.

Before Coming to Lab

  • Polish your apps! Finish any remaining user stories!
  • At this point, your app should be "complete."

Today in Lab

  1. Arrive in OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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 perform the Sprint Check for Sprint 6 (see below for more info).
  4. Once your meeting is complete, the Testing Manager should take the lead in planning Beta Testing for this week. See the Beta Testing Report for more information: https://drive.google.com/open?id=1KJ-PIMBXJMIqdV3sYYj2JZhDCLk_JQtHFQezbykVfu0

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 complete working app on Heroku. There should be no instances of something that is "almost done." If there is functionality you still plan to add, it should not be visible to the user. This should be a "shippable product."
  • Have unit tests automatically passing on Travis-CI.

With each Sprint Check, you will also need to do evaluations for your team members. Each role has a different evaluation form with different questions. Fill out the appropriate form for every other person in your team.

PLEASE read the scales before answering the questions! 10 means doing well, 0 means doing poorly!

Action Items After Lab

more ...

Lab 10 - Sprint 5 Ends -> Sprint 6 Begins

Lab Date: Monday, April 8

Lab Objectives

SPRINT CHECK 5 TODAY

  • At this point, teams should have completed all major stories for the project.
  • Your main objectives for this sprint should be to finish up remaining user stories and overall polish.

Before Coming to Lab

  • Finish Sprint 5! See the Sprint Check for more information.
  • Configuration Managers need to finish the Configuration Manger Report!

Today in Lab

  1. Arrive in OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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 perform the Sprint Check for Sprint 5 (see below for more info).

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 studnet to login using their UVA email 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.
  • Have unit tests automatically passing on Travis-CI.

With each Sprint Check, you will also need to do evaluations for your team members. Each role has a different evaluation form with different questions. Fill out the appropriate form for every other person in your team.

PLEASE read the scales before answering the questions! 10 means doing well, 0 means doing poorly!

Action Items After Lab

  • Finish up your app! Next week, you will need to show a working end-to-end product that you will then show potential customers during beta testing.
more ...

Lab 9 - Sprint 5 Work

Lab Date: Monday, April 1

Lab Objectives

  • Teams will have their stand-up meetings to discuss how Sprint 5 is progressing.
  • TAs will informally check in with teams to see if everything is going okay.
  • Sprint Check 5 will be next week!

Before Coming to Lab

  • Work on Sprint 5!

Today in Lab

  1. Arrive in OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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. This is a working lab. Stay the entire time and work with your team on Sprint 5.
  4. TAs will informally check in with each to see if everything is going okay. Make sure to ask any questions you may have!
  5. Configuration Managers should continue working on the Configuration Manager Report found at: https://drive.google.com/open?id=1-_42-ezYzDx7vQbv-VMxvIWJPbDMta3AVDf6K_soWF8

Action Items After Lab

  • Work on the items you pulled for Sprint 5!
  • If you are ahead of pace, pull another story!
more ...

Lab 8 - Sprint 4 Ends -> Sprint 5 Begins

Lab Date: Monday, March 25

Lab Objectives

SPRINT CHECK 4 TODAY

  • Teams will show their login functionality along with whatever other features they have worked on to this point.
  • Teams will pull stories for Sprint 5.

Before Coming to Lab

  • Finish Sprint 4! See the Sprint Check for more information.
  • Software Architects need to finish the Architecture Design document!

Today in Lab

  1. Arrive in OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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. This sprint really needs to target the rest of your "major" functionality, while Sprint 6 will be polish and minor additions. The end is closer than you think!
  4. While you are meeting, TAs will come around to perform the Sprint Check for Sprint 4 (see below for more info).
  5. Once you have your requirements pulled for Sprint 5, 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 studnet to login using their UVA email account.
  • Show a "major feature" of your app. This feature has to be one of the core use cases of your app, something like "creating a profile and searching for a student" or "searching all properties, selecting one, and giving it a rating."
  • Show a more refined UI design and theming.
  • Have unit tests automatically passing on Travis-CI.

With each Sprint Check, you will also need to do evaluations for your team members. Each role has a different evaluation form with different questions. Fill out the appropriate form for every other person in your team.

PLEASE read the scales before answering the questions! 10 means doing well, 0 means doing poorly!

Action Items After Lab

  • Work on the items you pulled for Sprint 5!
  • Configuration Managers should start work on the configuration report! Find it in the Student Resources folder or here: Configuration Manager Report
more ...

Lab 7 - Sprint 4 Work

Lab Date: Monday, March 18

Lab Objectives

  • Teams will have their stand-up meetings to discuss how Sprint 4 is progressing.
  • TAs will informally check in with teams to see if everything is going okay.
  • Sprint Check 4 will be next week!

Before Coming to Lab

  • Work on Sprint 4!

Today in Lab

  1. Arrive in OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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. This is a working lab. Stay the entire time and work with your team on Sprint 4.
  4. TAs will informally check in with each to see if everything is going okay. Make sure to ask any questions you may have!
  5. Software Architects should continue working on the Architecture Design document found at: https://docs.google.com/document/d/1sKclBQB2FJOY6cLeCU62aZZJps7wyoZrvMSV_FforI4/edit

Action Items After Lab

  • Work on the items you pulled for Sprint 4!
  • If you are ahead of pace, pull another story!
more ...

Lab 6 - Sprint 3 Ends -> Sprint 4 Begins

Lab Date: Monday, March 4

Lab Objectives

SPRINT CHECK 3 TODAY

  • Teams will show their login functionality along with whatever other features they have worked on to this point.
  • Teams will pull stories for Sprint 4.

Before Coming to Lab

  • Finish Sprint 3! See the Sprint Check for more information.
  • Testing Managers need to finish the Testing Plan document!

Today in Lab

  1. Arrive in OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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, which will take you up to March 25. We will expect you to complete another major piece of functionality for your project during this sprint. Something on the line of the entire student profile and searching for the Student Skills app or the viewing, searching, and commenting on housing options for the Off-Grounds app.
  4. While you are meeting, TAs will come around to perform the Sprint Check for Sprint 3 (see below for more info).
  5. Once you have your requirements pulled for Sprint 4, start working!
  6. Software Architects should note that the Architecture Design Document for your team will be due at the end of Sprint 4. See the Architecture Design Document Template in the Student Resources Google Drive folder.

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 studnet to login using their UVA email account.
  • Show at least the beginnings of your UI design and theming.
  • Have unit tests automatically passing on Travis-CI.

With each Sprint Check, you will also need to do evaluations for your team members. Each role has a different evaluation form with different questions. Fill out the appropriate form for every other person in your team.

Action Items After Lab

  • Work on the items you pulled for Sprint 4!
  • Software Architects should work on their testing plans!
more ...

Lab 5 - Sprint 3 Work

Lab Date: Monday, February 25

Lab Objectives

  • Teams will have their stand-up meetings to discuss how Sprint 3 is progressing.
  • TAs will informally check in with teams to see if everything is going okay.
  • Sprint Check 3 will be next week!

Before Coming to Lab

  • Work on Sprint 3!

Today in Lab

  1. Arrive in OLS 009 and get into your teams. You'll split between 001 and 009 per normal to meet and have attendance taken.
  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. This is a working lab. Stay the entire time and work with your team on Sprint 3.
  4. Make sure that you work on Travis-CI today! Your repos should be visible at http://travis-ci.com. Note that this is the .com not the .org - this is because your repos are private. If you login with your GitHub credentials, the UVA-CS3240-S19 organization should be on the left. Info on setting up your project to run on Travis can be found at: https://docs.travis-ci.com/user/tutorial/. We suggest setting up Travis and Heroku to work together: https://docs.travis-ci.com/user/deployment/heroku/
  5. TAs will informally check in with each to see if everything is going okay. Make sure to ask any questions you may have!

NOTE: Please see the post on Piazza at https://piazza.com/class/jpyxy8eezyh6v?cid=140 regarding clarification on using the library described at http://cs3240.cs.virginia.edu/category/project. In short, this is a constraint requirement. If you have questions about this, please talk to your TAs or post on Piazza.

Action Items After Lab

  • Work on the items you pulled for Sprint 3!
  • If you are ahead of pace, pull another story!
more ...