cs350

General Description

Throughout the semester you will be developing a music website that provides information on local bands and venues. Every 2 weeks you will have a release and a working demo. You need to follow Scrum methodology. In the section below labeled Product Backlog I list some possible features of such a site. Feel free to add to this list. You will elect one person in your team to be the product owner whose task it is to maintain the product backlog as a prioritized list. For each sprint (2 week interval) the team will select a set of backlog items that will be in the next release.

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)
  • by the end of class ea. team is to send me email containing:
    • name of the Scrum Master
    • name of the Product Owner
    • the set of backlog items that will be implemented in this sprint along with who is assigned to that item.
• 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)

Product Backlog

• main page (see wireframe below) showing featured artist and venue
• ability to search for artist and display basic info
• ability to search for venue and display basic info
• ability to create an entry for a band
• validation - when a user enters info into a form make sure things that are NOT NULL in the db have values in the form.
• ability to create an entry for a band
• ability to delete an entry
• ability to make changes to an entry
• create an account page
• implement only people with accounts can log in and make changes.
• show upcoming shows for a band
• show upcoming events at a venue
• show related artists for a band
• show popular albums for a band
• allow people to add comments to a band page.
• design basic layout/style for site
• wireframe all pages
• have a link from venue description to google maps.

Wireframes

The site doesn't need to look like this. This is only intended to start you thinking.

Main Page Example

large image here http://www.gliffy.com/publish/1979591/

Band Page Example

large image http://www.gliffy.com/publish/1982851/

Need to wireframe other pages yourself.