Lab 4 - Environment and Requirements

Lab Date: Monday, September 24

Lab Objectives

  • Teams will show the TAs their current progress on the requirements document
  • After getting feedback from the TAs, teams will put the finishing touches on the documents, then begin working on learning the development environment
  • This week, your team will learn the basics of Django and build a simple test app

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 complete the requirements documents, with the Requirements Managers taking the lead

In-Lab Activities

  • SPRINT CHECK: TAs will come by and check your requirements documents (see bottom of lab for more info)
  • Once you have had your documents checked by the TAs, you can continue to work on the requirements documents ahead of the final versions being accepted tonight
  • After you are done with your requirements documents, move on to the Django Practice activity in the Post-Lab section

Post-Lab Activities

Django Practice Activity

  1. Split your team into pairs and give each pair a number (1, 2, etc.)
  2. If you have an odd number, you can have one solo or one set of 3
  3. One person in each pair should accept the assignment on GitHub Classroom and setup your partnership at https://classroom.github.com/g/345qo3Xu with your full team name + pair number (something like Resources Are Awesome 1, etc.)
  4. The partner(s) should go and find the team and join it at the same link above
  5. The pair should now together work on creating the example Django app found here: https://docs.djangoproject.com/en/2.1/intro/tutorial01/
  6. There are seven steps to this tutorial, and yes, you need to do all seven
  7. I have applied for credits for us to use Google App Engine to host our apps and once I have more information about that, I will post here and let everyone know
  8. Your full team will need to show that all tutorial apps are working next week to earn a Pass on the Sprint Check

Sprint Check

To earn a pass for this sprint, teams must:

  • Have a nearly complete requirements document, including all sections, with some information in each section
  • Have a nearly complete set of user stories
  • These documents do not have to be "final" versions, but must demonstrate to the TA that the bulk of the work was done over the course of the week and care was taken in the creation of these docs
more ...

Lab 3 - Project Requirements

Lab Date: Monday, September 17

Lab Objectives

  • Teams will meet and begin working on a plan for eliciting requirements from other UVA students for their projects
  • Requirements managers will be responsible for coordinating this effort, documenting the results, and creating the final requirements document for the team
  • Requirements managers will be responsible for managing the requirements and making decisions on any ambiguities throughout the semester
  • The entire team will be a part of the elicitation efforts

Pre-Lab Activities

  • Requirements managers should carefully read the documents in your team's Google Drive folder
  • Other team members (especially the Scrum Master) probably should look at them so you are familiar with the overall assignment

In-Lab Activities

  • TAs will choose which teams they will be working with for the rest of the semester
  • Your team's TA will introduce themselves and let you know that they will be your main contact on the staff
  • Requirements managers should take the lead with teams in planning how to do requirements elicitation for the project this week
  • Please post questions about this activity to Piazza

NOTE: Starting today, we are giving you the lab period as dedicated teamwork time when you know that all team members are available. You should not leave lab early except under specfic extenuating circumstances after you have cleared it with the TAs. You can and will be docked lab attendance points for not staying for the entire lab!

Post-Lab Activities

  • Work on the requirements elicitation activity!

Assessment

  • Attendance will be taken and will count toward your total number of labs
  • Make sure to beep in at the beginning of lab
more ...

Lab 2 - Meet Your Team

Lab Date: Monday, September 10

Lab Objectives

  • Teams will meet each other for the first time and will start getting setup for the semester project
  • Students will have an opportunity to begin learning about Django, the environment we will be using for the project

Pre-Lab Activities

  • Make sure to bring your UVA ID to lab this week!

In-Lab Activities

  • TAs will announce the teams to the lab and give you time to get organized with your team
  • Once in your team, you need to accomplish the following:
    • Confirm which of the three projects your team will do (Used Textbook Marketplace, Universal Scheduler, Resource Finder)
    • Pick who on the team will take on the following roles: Scrum Master, Requirements Manager, Testing Manager, Software Architect (it is possible for 2 people to take on Requirements Manager, Testing Manager, and Software Architect, but not Scrum Master)
    • Determine your team's primary form of communication - we recommend a Slack channel instead of email, etc.
    • Once you have made all of these decisions, fill out the form here: https://goo.gl/forms/eMzsCV7hnPO2jSh52
  • The TAs will come around and get everyone's ID registered while you are doing all of this
  • Once you have spoken to the TAs and the form is filled out, there is a tutorial on Django we expect everyone to be able to do
  • You can work on the tutorial here, or leave lab and do it on your own time, but we exect everyone to know the material in it

Post-Lab Activities

Assessment

  • There are no assessments for this lab
  • Attendance will not be taken for this lab and it does not count toward the 10 labs in the Specification Grading Chart
more ...

Lab 1 - Project Pitches

Lab Date: Monday, September 3

Lab Objectives

  • Each lab will nominate up to 3 total projects for consideration by the entire class on Tuesday, September 4, in lecture
  • Individuals who have a project that is nominated should be ready to say something about it in lecture

Pre-Lab Activities

  • Come up with an idea for the team project for this semester
  • The idea must meet the following prompt: "My life as a UVA student would be so much better if I just had _."
  • The project must be a web app of some kind, be usable in both desktop and mobile browsers, and have just a couple major features
  • The scope you are looking for is a project that could be completed in one month

In-Lab Activities

  • Students will get the opportunity to pitch their ideas to the lab
  • TAs will write the ideas on the board and will conduct a vote
  • By whatever procedure the lab decides, up to 3 projects can be nominated by that lab for class consideration on Tuesday, September 4

Post-Lab Activities

  • Nominated studetns / projects will be contacted if they will be called on in class on Tuesday, September 4

Assessment

  • There are no assessments for this lab
  • Attendance will not be taken for this lab and it does not count toward the 10 labs in the Specification Grading Chart
more ...