CIS 2250 Lecture Notes - Lecture 16: User Story

• School: University of Guelph
• Department: Computing and Information Science
• Course: CIS 2250
• Professor: Deborah Stacey

Document Summary

You can accurately plan in detail only for nearby tasks. The people doing the work must be actively involved in scheduling. People should (cid:272)hoose their work, they shouldn"t (cid:271)e assigned it. Organize the project into short iterations: remember that the only measure of progress is working software have working software after each short iteration, user involvement is easier with working software. Choose an approach which reflects your environment. Ignore the calendar (wednesday to tuesday not monday to friday) Have as many iterations as you need readjust as necessary. But you can still have a firm delivery date prioritize and always iterate around working software. During a sprint, it is important to know what the objectives are in terms of tasks to be completed. A visual representation of this, called the scrum task board, can help the team keep track of what it is doing. Before or during the daily stand up meeting, the scrum board is updated.