ScrumBut is a web app, built with Yesod, that adds Scrum features to GitHub Issues.
Despite Scrum’s focus on synchronous, co-located sprint meetings, ScrumBut will try to support asynchronous, distributed workflows as much as possible, to make it easy for remote workers to collaborate as well. This is why the project’s name comes from a derogatory term referring to teams that don’t use “true Scrum.”
A particular team could start using one of their repositories by following these steps:
- Everyone on the team signs in using their GitHub account.
- One of the collaborators sets up that repository in ScrumBut, enabling Scrum features for it.
Once set up, any issue can be assigned story points as follows:
- Collaborators submit story point estimates for the issue, along with an optional rationale for their estimate.
- Once all team members have estimated the issue, a middle ground is automatically chosen if the estimates are close enough to each other.
- If there are any big outliers in estimation, those users will get a notification and an opportunity to adjust their estimate, or else talk with the rest of the team about adjusting theirs.
ScrumBut will treat GitHub milestones as sprints if they contain estimated issues.
After at least one issue in a milestone has been estimated, anyone can see the total number of story points in that milestone, as well as how many have been completed so far.
After a milestone with estimates has been completed, the total number of points will automatically be incorporated into a velocity that can be used to predict how many story points can be accomplished going forward.
Although there are many possible ways to deploy ScrumBut, the only supported method is the Haskell on Heroku buildpack:
After the template has been deployed, you’ll need to set up private storage then build on a one-off PX dyno before the app can be used.
ScrumBut is released under the MIT License.