Version 12 (modified by sriggins, 16 years ago) (diff) |
---|
Analysis
Overview
The RELEASE_SCHEDULE needs to be reviewed by the team.
Task requirements
- Each team member should read the release schedule. It can be found RELEASE_SCHEDULE.
- Each team member should submit their input as a comment on this wiki page (see link at top of this page)
Task result
The result of this task is a Release Schedule that has taken into account the comments made during this review.
Implementation idea
I think the best way to collect comments would be in the comments of the ticket. Those comments can then be copied to this wiki page.
Related
How to demo
Show the comments on this page
Design
- This is the schedule that the customer will use to evaluate our productivity.
- Each reviewer should feel comfortable with these dates.
- Do not feel as though you need to make comments just for making comments sake.
- Please only give constructive feedback if you feel there is an fatal error in the schedule.
- Remember that the dates are approximately 5 weeks after the sprint date, to allow for testing.
- The exception is the last few releases, which have closer release times
- Leave your comments in the comments section below in the form:
- <USERID> - <COMMENT>
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
N/A
Comments
(Leave your RELEASE_SCHEDULE comments here)