Sprint Requirements

Sprint 1

Objective: For every team member to write code that accesses a single database table. Team members use a versioning system.

Grading

Grading useful projects is sort of like the old story of losing one’s keys and searching under the street light. Here is my grading criteria and a rough point distribution.

• How well did the team follow Scrum methodology (gauged from listening to the Scrum meetings and Scrum meeting attendance) (20 points)
• For this sprint, I am looking to see if every Scrum team member wrote code that accessed a single database table (as opposed to combining info from tables as discussed in ch 7) and the work was well distributed. (25 points)
• Use of github. (can clone a working demo) (20 points)
• One click install plus instructions on how to install. (10 points) An sql file that you need to source is worth 5 points.
• Demo works & quality of demo. By quality I don’t mean that a larger percent of backlog items is better quality. I mean that what you did implement works well and looks reasonably good. (25 points)

Sprint 2

Objectives

• Add functionality that uses updates to tables. For example, you might want to allow people to edit band info.
• When multiple rows are displayed they should be arranged in a sensible order (for ex., alphabetical).
• PHP session is implemented.
• Add at least one table to the database and implement code to use it (for example, a CD table). This isn’t necessary but it may reduce the work load for the next sprint.

Grading

• Scrum Process 25%
• Git – I will examine the git history of your project to see if you are using Git in a sensible way. 20%
• One click install – 5%

• Demo works and quality of demo. 50%
  • Multiple team members have checked in code that uses the SQL update command 15%
  • Displays of multiple rows are ordered in logical way 15%
  • Session implemented 15%
  • added one table

Sprint 3

Objectives

• all tables in 3NF
• all developers demonstrate that they can write queries that use joins.

Grading

• Scrum Process 25%
• Git – I will examine the git history of your project to see if you are using Git in a sensible way. 20%
• One click install – 5%

• Demo works and quality of demo. 50%
  • tables in 3NF 20%
  • queries that use joins 20%
  • general quality 10%

Sprint 4

Objectives

You are to implement 2 new features based on material in the rest of the textbook. For example:

• updates using a subquery (chapter 9)
• outer joins, self joins and unions (chapter 10)
• indexing to speed up queries (p 539)