Iterations and Milestones
Milestones can represent a variety of deadlines, depending on what process you are running on Assembla. In ScrumClub, we use iteritive releases:
CurrentRelease milestone
This is the milestone for the CurrentRelease. We will add tickets to this milestone to define the scope of the first sprint. Anything that is left unfinished at the end of the sprint is either sent to the ProductBacklog or forward to the NextRelease. We will leave the tickets that are completed here as our ProductRecord. As we move forward, we open up a new milestone... and repeat successively. The easy mistake is to move tickets around between the CurrentRelease and the ProductBacklog because people are used to moving post-it notes around. We want to create new milestones for each release:
- Alpha
- Beta
- Theta
or
- November
- December
- January
Product Backlog
This is all the stuff we need to do to get a product and running. Anyone can add to this backlog at any time. Think of it as a giant suggestion box. We may or may not decide to do it, but please submit your idea.
Space Home