Loading Profile...
Time-based Sprints/Releases
From my limited understanding of sprints and releases, I think it's best to make them time-bound. That means that when a sprint has reached its end date, it's safe to assume that any unfinished stories will automatically be moved to the next sprint. Same with releases. This could probably be made automatic rather than manual otherwise it won't feel so close to the philosophy of Scrum. I'm also basing this on my observation of a few open-source projects where they are time-bound rather than feature-bound.
I’m hoping this makes sense
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Mark,
What you said does make sense. One of the reasons for scrum'd is to have a tool that does follow the scrum framework pretty closely. We are also trying to keep the tool flexible enough so that it doesn't 100% force you into a certain way of doing things. Having said that though, your idea is here for the community to vote on. Let's see what others think about it as well.
Thank you for the idea.
I’m happy
EMPLOYEE
