Lab Overview

Lab 1: Project Pitches (09/03)

Lab 2: Meet Your Team (09/10)

Lab 3: Project Requirements (09/17)

Lab 4: Environment and Requirements (09/24)

Lab 5: Project Start (10/01)

  • http://cs3240.cs.virginia.edu/lab-5-project-start.html
  • SPRINT CHECK 2: Teams must show three distinct, complete instances of the Django tutorial, pushed to GitHub
  • Teams have their first stand-up meeting and decide on what to work on in the first weeks of the project
  • Scrum Masters and Requirements Managers need to indicate on the Project Management spreadsheet what will be worked on and by whom during the next two weeks as there is no lab on 10/08 due to Fall Break

Lab 6: Your First Page (10/15)

Lab 7: Major Feature 1 (10/22)

Lab 8: Major Feature 2 (10/29)

Lab 9: Logging In (11/05)

Lab 10: Polish (11/12)

Lab 11: Beta Version Ready! (11/19)

Lab 12: User Testing (11/26)

Lab 13: Demos (12/03)

  • http://cs3240.cs.virginia.edu/lab-13-demos.html
  • SPRINT CHECK 9: Teams must present a User Test Report, showing what students said about their apps and how they addressed those comments, along with a nearly-final version of their app to demo

FINAL VERSION OF PROJECT IS DUE (12/10)

more ...

Lab 13 - Demos

Lab Date: Monday, December 3

Lab Objectives

  • Demo day! You will show your apps to the staff for "preliminary" grading!

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

In-Lab Activities

  • SPRINT CHECK 9: To pass this final sprint check, have the following:
    • A completed Beta Testing doc in your Google Drive folder
    • A fully-working demo of your final project ready to go
  • DEMOS AND PRELIMINARY GRADING:
    • You will perform a full end-to-end demo for the staff
    • This is your chance to show off EVERYTHING your app can do!
    • If the staff determines that your app as it is right now meets the criteria for "Complete and Well-Reviewed," then your final project is done! Sherriff will look over the code later as a final check, but that's it for you!
    • If the staff determines that your app as it is right now meets the criteria for "Complete," you will be given a list of things you need to fix by Monday, December 10. You can then opt to either demo the changes to Prof. Sherriff or allow him to grade on his own. You will be informed whether your app is upgraded to "Complete and Well-Reviewed" via email.
    • If the staff determines that your app as it is right now is "Insufficient," you MAY receive a No Pass for Sprint Check 9 (depending on how far behind you are) and will be given a list of things you need to fix by Monday, December 10. You can then opt to either demo the changes to Prof. Sherriff or allow him to grade on his own. You will be informed whether your app is upgraded to "Complete" or "Complete and Well-Reviewed" via email.
  • TEAM EVALUATIONS - FINAL EVALUATIONS!!!:

Post-Lab Activities

  • Fix your app if needed!
  • Get ready for the final two KA Core Days!

Sprint Check

To earn a pass for this sprint (SPRINT CHECK 9), have the following:

  • A completed Beta Testing doc in your Google Drive folder
  • A fully-working demo of your final project ready to go
more ...

Lab 12 - User Testing Week

Lab Date: Monday, November 26

Lab Objectives

  • Plan your user testing for this week!

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

In-Lab Activities

  • NO SPRINT CHECK THIS WEEK
  • STAND UP MEETING:
    • What went well the past week?
    • What do we need to do this coming week to be successful?
    • Who is going to work on what tasks?
    • Make sure to take notes on these things!
  • Plan your your user testing for next week!
  • IF YOU FORGOT TO DO YOUR TEAM EVALUATIONS LAST MONDAY ONLY!!!:

Post-Lab Activities

Sprint Check

No Sprint Check this week!

more ...

Lab 11 - Beta Version Ready!

Lab Date: Monday, November 19

Lab Objectives

  • This is it! Beta versions! You should have a fully-functional app! May not be completely polished, but still...

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

In-Lab Activities

  • SPRINT CHECK 8: Beta Version - We want to see an end-to-end system, free from obvious show-stopping defects that you can show to potential users starting next week. Period. There is no Pass with Reexamination today. It's all or nothing.
  • STAND UP MEETING:
    • What went well the past week?
    • What do we need to do this coming week to be successful?
    • Who is going to work on what tasks?
    • Make sure to take notes on these things!
  • Plan your your user testing for next week!
  • TEAM EVALUATIONS:

Post-Lab Activities

  • Go home for break!

Sprint Check

To earn a pass for this sprint (SPRINT CHECK 8), teams must have an end-to-end system, free from obvious show-stopping defects that you can show to potential users starting next week. Period. There is no Pass with Reexamination today. It's all or nothing.

more ...

Lab 10 - Polish

Lab Date: Monday, November 12

Lab Objectives

  • Teams will show off the progress on their app, specifically how it looks on laptop AND mobile

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

In-Lab Activities

  • SPRINT CHECK 7: TAs will check two things -
    • 1) we are looking to see how your app looks on laptop AND mobile - the mobile view should be reasonably easy to use and not have any glaring usability issues (if you have to convince yourself that something "isn't that bad," then that's probably an issue...)
    • 2) your Travis-CI build/test log, showing the latest run was complete and passed all tests
    • Basically, we are expecting you to have been working on all of the major features up to this point
    • The app is of course not "done," but you should be on track to have something 95% complete next week! (November 19)
  • STAND UP MEETING:
    • What went well the past week?
    • What do we need to do this coming week to be successful?
    • Who is going to work on what tasks?
    • Make sure to take notes on these things!
  • Plan your sprint! Add your next major feature to the mix.

Post-Lab Activities

  • Work on your app!

Sprint Check

To earn a pass for this sprint (SPRINT CHECK 7), teams must have:

  • 1) a "working" app up on your Heroku space, showing how the app looks on both laptop and mobile
  • 2) your Travis-CI build/test log, showing the latest run was complete and passed all tests
  • 3) your TA MUST be convinced that you are on track to have your beta version ready by November 19; if there is any doubt here, you will receive a No Pass and will need to catch up this week before next Monday
more ...

Lab 9 - The Login

Lab Date: Monday, November 5

Lab Objectives

  • Teams will show off the progress on their app, specifically pointing out their login

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

In-Lab Activities

  • SPRINT CHECK 6: TAs will check two things -
    • 1) a "working" app up on your Heroku space, showing good progress on your login; the feature does not have to be "done," but should be enough that the TA is convinced you are making solid progress
    • 2) your Travis-CI build/test log, showing the latest run was complete and passed all tests
    • Basically, we are expecting you to have been working on all of the major features up to this point
    • The app is of course not "done," but you should be on track to have something 95% complete in two weeks (November 19)
  • STAND UP MEETING:
    • What went well the past week?
    • What do we need to do this coming week to be successful?
    • Who is going to work on what tasks?
    • Make sure to take notes on these things!
  • Plan your sprint! Add your next major feature to the mix.

Post-Lab Activities

  • Work on your app!
  • Architects should turn in their docs tonight!

Sprint Check

To earn a pass for this sprint (SPRINT CHECK 6), teams must have:

  • 1) a "working" app up on your Heroku space, showing good progress on your login; the feature does not have to be "done," but should be enough that the TA is convinced you are making solid progress
  • 2) your Travis-CI build/test log, showing the latest run was complete and passed all tests
  • 3) your TA MUST be convinced that you are on track to have your beta version ready by November 19; if there is any doubt here, you will receive a No Pass and will need to catch up this week before next Monday
more ...

Lab 8 - The Second Feature

Lab Date: Monday, October 29

Lab Objectives

  • Teams will show off the progress on their app, specifically pointing out their second major feature

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

Pre-Lab Activities

In-Lab Activities

  • SPRINT CHECK 5: TAs will check two things -
    • 1) a "working" app up on your Heroku space, showing good progress on your second major feature; the feature does not have to be "done," but should be enough that the TA is convinced you are making solid progress
    • 2) your Travis-CI build/test log, showing the latest run was complete and passed all tests
  • STAND UP MEETING:
    • What went well the past week?
    • What do we need to do this coming week to be successful?
    • Who is going to work on what tasks?
    • Make sure to take notes on these things!
  • Plan your sprint! Add your next major feature to the mix.

Post-Lab Activities

  • Work on your app, adding in another feature
  • Architects should continue work on the Architecture Document - Architecture Template or found in the Student Resources folder linked on the right side menu of the course website.

Sprint Check

To earn a pass for this sprint (SPRINT CHECK 5), teams must have:

  • 1) a "working" app up on your Heroku space, showing good progress on your second major feature; the feature does not have to be "done," but should be enough that the TA is convinced you are making solid progress
  • 2) your Travis-CI build/test log, showing the latest run was complete and passed all tests
more ...

Lab 7 - The First Feature

Lab Date: Monday, October 22

Lab Objectives

  • Teams will show off the progress on their app, specifically pointing out their first major feature

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

Pre-Lab Activities

In-Lab Activities

  • SPRINT CHECK 4: TAs will check two things -
    • 1) a "working" app up on your Heroku space, showing good progress on your first major feature; the feature does not have to be "done," but should be enough that the TA is convinced you are making solid progress
    • 2) your Travis-CI build/test log, showing the latest run was complete and passed all tests
  • STAND UP MEETING:
    • What went well the past week?
    • What do we need to do this coming week to be successful?
    • Who is going to work on what tasks?
    • Make sure to take notes on these things!
  • Plan your sprint! Add your next major feature to the mix.
  • Architects need to start on the architecture document - Architecture Template or found in the Student Resources folder linked on the right side menu of the course website.

Post-Lab Activities

  • Work on your app, adding in another feature
  • Architects should start on the Architecture Document

Sprint Check

To earn a pass for this sprint (SPRINT CHECK 4), teams must have:

  • 1) a "working" app up on your Heroku space, showing good progress on your first major feature; the feature does not have to be "done," but should be enough that the TA is convinced you are making solid progress
  • 2) your Travis-CI build/test log, showing the latest run was complete and passed all tests
more ...

Lab 6 - Your First Page

Lab Date: Monday, October 15

Lab Objectives

  • Teams will begin by showing off their first build of "something" working on Heroku and Travis-CI
  • Teams will then have a stand up meeting to plan for the creation of their first major feature for this sprint

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

Pre-Lab Activities

  • The team should have "something" showing up in Heroku and Travis-CI and can show this to the TAs

In-Lab Activities

  • SPRINT CHECK 3: TAs will come by and check four things: your GitHub repo with your current version of your project, your Heroku info page, your Heroku deploy URL, and your Travis-CI info page
  • STAND UP MEETING:
    • What went well the past two weeks?
    • What do we need to do this coming week to be successful?
    • Who is going to work on what tasks?
    • Make sure to take notes on these things!
  • Plan your sprint! Target one primary feature, but not login. For now, just hardcode login credentials.
  • Testing Managers need to start on the testing plan - Test Plan Template or found in the Student Resources folder linked on the right side menu of the course website.

Post-Lab Activities

  • Work on your first primary feature
  • Testing Managers should also be writing the test plan

Sprint Check

To earn a pass for this sprint (SPRINT CHECK 3), teams must:

  • Show a basic, skelleton app in four places: your GitHub repo, your Heroku info page, your Heroku deploy URL, and your Travis-CI info page
more ...

Lab 5 - Project Start

Lab Date: Monday, October 1

Lab Objectives

  • Teams will begin by showing their progress learning the Django platform
  • Teams will have their first official stand-up meeting and will do their first sprint plan
  • Teams should leave today with assignments for each team member to begin work on the project

Attendance

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
  • You should not leave lab early without first speaking to the TA to explain any special cirucumstances
  • Leaving lab early without discussing with the TA could negate your lab attendance point

Pre-Lab Activities

  • The subteams should have completed the Django tutorial and have the final version pushed up to GitHub

In-Lab Activities

  • SPRINT CHECK 2: TAs will come by and check your Django tutorials - each team should have 3 tutorials to show (see bottom of lab for more info)
  • While waiting for the TAs to come around (and after they have done the check), the team should start with a stand-up meeting
  • As this is the first meeting and you haven't done anything yet for the project, everyone should tell the rest of the team the following:
    • what their availability for working on the project is for the next two weeks (remember: no lab next week due to Fall Break)
    • how they feel about working with Python / Django (please be honest with your team as this is a chance to get help and work with someone during this sprint to learn what you need to learn!)
    • what they would like to work on during the next two weeks
  • Here are some suggetions on what to split up among the team members (or even better - pairs of team members):
    • Pushing things to Google App Engine (More on this coming soon)
    • Investigating how to do continuous integration (More on this coming soon)
    • Working on theme / design / layout / UX / wireframes
    • Working with GitHub and getting the project environment ready
  • The Scrum Master should go to GitHub Classroom, accept the project assignment, and create the team: https://classroom.github.com/g/3BtabUAS
  • The team MUST be named with your lab number then your team name with special characters removed and dashes inserted in place of spaces
    • EXAMPLE: (Seal) Team 6 should sign up as 101-Seal-Team-6 as the team name
  • The rest of the team should then go and join the assignment in GitHub Classroom
  • Once all team members have accepted the primary Project GitHub Classroom assignment, you should all also have access to a Practice Project after you accept this assignment: https://classroom.github.com/g/AWjy18qo
  • Feel free to use this repo for whatever you like for practice purposes or testing things out

Post-Lab Activities

  • You have two weeks until the next sprint check on 10/15
  • Understand that people will be traveling and potentially have midterms in other classes
  • Set reasonable, achievable goals for what you can accomplish, making sure you hit at least the minimum for the next sprint check

Sprint Check

To earn a pass for this sprint (SPRINT CHECK 2), teams must:

  • Show three distinct, working instances of the Django tutorial, establishing that all team members have had experience learning the platform
more ...