paceuniversity / cs3892015team6

0 stars 1 forks source link

Feedback on wiki, sprint 1 retro, sprint 2 planning #5

Open scharffc opened 9 years ago

scharffc commented 9 years ago

The feedback is available here.

https://docs.google.com/spreadsheets/d/1CftTZS1bn0vXUdgIJOpq_BRmra77w2eshohpuk1vZT8/edit#gid=0

@mrtrock @dheerm @kb14375n

scharffc commented 9 years ago

@mrtrock @dheerm @kb14375n

Hi,

I reviewed your Wiki, Sprint 1 Retrospective and Sprint 2 Planning. Your grade for this part is also posted. You got a notification through GitHub. 2 students are not on GitHub at this point.

Please take the comments into account and improve your work for the next time it will be reviewed.

General comments:

You are 3-4 students in a team and it is important that all team members contribute. You all need to commit code or documents in the GitHub code repository. You also need to review the work of your classmates. If one student begin then there are 2-3 students who are reviewing and improving. The work that is provided must be of better quality.

There are lots of confusion between the words: Scrum and Sprint. They mean different things. Please read the Scrum Primer.

Review also the meaning of Sprint Burndown Charts. If you are not doing the complete work you cannot reach 0. If you do not plan on day 1 of the Sprint (Sprint 2 was due on 4/5), it should be reflected on the Burndow Charts.

In Scrums you cannot use WE but you should use I.

Retrospective do not provide enough information about the difficulties you meet with process and product. Please allow more time for reflection during the retrospective.

Some of the apps are heavily subject to content. If your app requires content (that you need to provide), I would like you to put in your Sprint 2 Goal information about what content you will be delivering at the end of Sprint 2. For example, you must know if for examples there will be 1-x quizzes with 1-y questions each. You need to be very precise in what you will be delivering.

Best,

Dr. Scharff