Section 6.4

Sprint #1

Learning Goals

Students will gain experience with Agile product development by working in sprints to complete the Unit Challenge

AAP-2.E: Students will write and evaluate expressions using relational operators.

AAP-3.A: Students will use abstraction to manage complexity in a program.

AAP-3.A: Students will determine the result of code segments.

CRD-2.C: Students will identify inputs to a program.

CRD-2.C.5: Students will learn how to execute program statements through even triggers rather than through the sequential flow of control.

CRD-2.F.3: Some ways investigation can be performed are as follows:

collecting data through surveys
user testing
interviews
direct observations

Objectives and Description

The purpose of Sprint 1 is to serve as the first checkpoint for students for this Unit's ARC Challenge. Using the tools they have learned about so far in this Unit (event-driven programming, lists, and list operations) as well as coding knowledge from Unit 5, student groups must at the end of the sprint deliver a rough outline of their Lo-fi MP3 player application. Over the course of the sprint, they should structure their work into design, coding, and test phases.

Activities

Activity 6.4.1 (budget 180 minutes)

Design

- Student groups should make a mockup on paper of what they want their interface for their Lo-fi MP3 player to look like
- Student groups should also make a short list of user stories: general explanations of features of their application written from the perspective of the user.

Code

- Student groups will set up the framework for their Lo-fi MP3 player application. The following is a list of features that should be a part of this sprint's final deliverable:
  - A file directory that contains the songs that will be played by the Lo-fi MP3 player application
  - A list in the script that contains the file names of each song as strings
  - Configurations for the layout of the application
  - At least one button that plays a song when pressed

Test

- Student groups will share their mockups and prototypes with other groups to collect feedback.. Feedback can be in the form of collecting data through a survey, interviewing the user, user testing with the prototype, and through direct observation with the prototype. There should be a period of time where iterating upon their mockups and script based on feedback is allowed.

Deploy

Student groups will submit any UI mockup materials they produced
Student groups will submit a list of user stories
Student groups will submit a .zip file of the folder that contains the following:
- A file directory that contains the songs that will be played by the Lo-fi MP3 player application
- A script that contains:
  - a list that contains the file names of each song as strings
  - configurations for the layout of the application
  - At least one button that plays a song when pressed

Resources

Report abuse