-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting April 19, 2016
Absent: #Agenda
- Check that the system is capable of everything it should be so far.
- Decide our next action items.
- What is next due of Mike's class?
- What is the status of Ashley's new UI?
#Discussion Our meeting started with testing the current master branch of the website to make sure the functionality we needed for our next deadline and that everything worked as planned. Here is a list of issues we found.
- New instructors cannot be created.
- It is not possible to select any class other than the first.
- After an instructor creates a new assignment they are kicked out of the class to the instructor home page.
- There is much difficulty backing up/moving forward in web page history due to post request dependencies.
- New group dropdown shouldn’t populate with students already in that group.
- Two groups shouldn’t be able to have the same group number.
- Removing a user from a group removes the person from EVERY group within that assignment.
- A new criteria should not be automatically populated with the previous criteria's values.
- Creating a new evaluation for an assignment already with an evaluation of the same type causes the previous evaluation to be overwritten.
There are possibly more errors than this so Thursday will be dedicated to further testing while Friday and Monday are dedicated to fixing the highest priority errors we find.
We've decided that after Tuesday (the next evaluation date for Mike's class) we will focus on moving the site over to a better UI and workflow as well as make it mobile friendly by May 5th.
By the end of the semester we want to provide a better and more in depth experiences to students and instructors while they view their cumulative results of evaluations they've received.
#Upcoming Meetings
- 4/26/15 SCRUM Meeting
#Action Items
- Thursday: Test the system for errors/mistakes.
- Friday: Fix errors.
- Monday: Fix any remaining errors and create the groups/evaluations for the class's Tuesday evaluation.
- Next Sprint: Move to new UI/workflow and make the site mobile friendly.
- Before the end of the semester: Develop better method of users viewing their cumulative results of received evaluations.
Kick Off, Feb 20
SCRUM, Feb 22
Functional Requirements, Feb 23
SCRUM, March 3
SCRUM, March 8
SCRUM, March 15
SCRUM, March 22
SCRUM, March 29
SCRUM, April 5
SCRUM, April 12
SCRUM, April 19
SCRUM, April 26
User Accounts
Assigning Evaluations
Assignment Management
Project Evaluation Report
Groups
Class Rank
Definition of Done
[Evaluation MVP (Haggis) Functional Requirements](Evaluation MVP-(Haggis)-Functional-Requirements)
Laravel Resources List
Reading List
Terminology