We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The auto-scheduler works fine for large multi-team organizations that have epics that belong to only one team.
However, this doesn't work as well for smaller teams that have epics that span multiple individuals.
And, the scheduler doesn't handle a "Team" working on multiple epics at once.
This issue are ideas on how this situation could be handled.
Things to think about:
Maybe initiatives and epics help "sort" the stories. Initiatives and epics aren't "planned", they are just sorted.
Then we plan out stories for the first epic.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The auto-scheduler works fine for large multi-team organizations that have epics that belong to only one team.
However, this doesn't work as well for smaller teams that have epics that span multiple individuals.
And, the scheduler doesn't handle a "Team" working on multiple epics at once.
This issue are ideas on how this situation could be handled.
Things to think about:
How it might work ....
Top down, then bottom up?
Maybe initiatives and epics help "sort" the stories. Initiatives and epics aren't "planned", they are just sorted.
Then we plan out stories for the first epic.
The text was updated successfully, but these errors were encountered: