-
Notifications
You must be signed in to change notification settings - Fork 0
Leader ToDos
Bronte Lee edited this page Feb 26, 2015
·
4 revisions
Really, for the leader or anyone who wants to make sure we're on track.
- client demo is ready
- whatever we have by Thursday midnight(?) will be the demo pretty much.
-
iteration plan for next sprint
- update previous sprint's chart
- add this sprint's chart
-
update release plans (make sure the description of each release and the corresponding user stories are correct)
- update story map
- meeting minutes are all where they should be for that sprint
-
Requirements documentation is updated, whatever was not mentioned above such as:
- mockup storyboard matches product (each screen may not be accurate to the actual product?)
- glossary
- release burndown and iteration charts and tables
- update Architecture document
- update Acceptance Tests document
- arranging meetings - send out an email to all group members, TA, and client about:
- where - can be CSC 3-50 (bi-weekly developer meeting) or Tory 9-15 (bi-weekly client meeting)
- when - Noon for the Friday meetings.
- the agenda (a quick summary is fine)
- writing meeting minutes, put them on your repository and send to all members
- (Nice to have) A summary of the work in the past week, who did what?
- TODOs for the coming week. (Apparently will be checked on this in every meeting).
Table of Contents
- Home
- Requirements
- Acceptance Tests
- Architecture
- Meeting Agenda and Minutes
- Developer Group Notes and To Dos
- 3rd Party Libraries and Resources