...
- We should track tickets by release and sprint, not just sprint.
- We should default to putting the current release in the “Fix Version” field in JIRA, and remove it later if the work is to be deferred.
- We should define Rnnnnx-Sprint-Final as the time between Feature Complete and Code Freeze; and number all sprints before Feature Complete
- We should have defined terminology for what should go in the “Fix Version” field for JIRA; all tickets should have one of the standard values. A notional set for discussion:
- CCB incoming – new tickets for CCB disposition
- Rnnnnx – assigned to a release
- Near Term backlog – needs to go in next release
- Long Term backlog – needs to go in some future release (I’ve seen “someday” in the Fix Version field, this is equivalent
- Backlog – tickets to review to see if they are overtaken by events or should be put in some other category.
- (SPH) We need to complete complex features earlier in the development cycle and get out to users for beta testing. We have too many bugs slip through, because we are assuming that our system tests, which are quite rigorous will catch everything. But that is not the case. A few months of user testing will find things that we missed.