Home
Welcome to the sprint-graph wiki!
Scrum is as difficult framework, often coupled with tools like Jira, Jenkins, Sonar. Even if these tools are great and do a lot of job, no one is providing clean interfaces that just display the data that you need when you use Scrum.
How to convince your boss that work is done, visually.
Delivery date: 05/02/2017 : release is v1.0.1
Goal : know the workload of each sprint in SP (Story points)
Contains a list of "stool pigeons":
- start date
- end date
- working days (e.g: "15")
- SP a.k.a "story points" (e.g: "102")
- velocity (e.g: "0,93")
- Team capacity (e.g: "112")
The last 4 data are not editable and are computed like this: working days = (number of days between start date and date) - (non working days) SP = sum(stories.points) capacity = working days * members.count - sum(members.vacationDays.count) velocity = SP / capacity
Dependency of this item : calendar/vacation (see below)
Goal : handle members in order to know the capacity of the team (number of workdays per sprint)
Store minimal information about members:
- First name
- Last name
- pseudo ?
- avatar or email (see gravatar.com)
- role (SM, DEV, PO)
No authentication as each member should be confident in others (it looks simpler to implement as well ;-))
Mockup: sprint-graph/tree/master/project_assets/png/Members.png
Goal : handle vacations in order to know how many work days are expected within a sprint
Store list of vacations days for each member "As a member, I want to enter a new day off to allow the scrum master to get an estimation of the capacity of the team for the next sprint"
Each member can display the list of its day off. all members can display the list of all day off during a period of time.
Only SM can create a day-off on behalf another member (low priority feature)
Dependency of this item : member (see above)
Mockup: sprint-graph/tree/master/project_assets/png/Vacations.png
Goal : display visually burndown and burnup charts
"Nice to Have" feature : annotations related to graph points (stories added, removed, story closed during the day...) see: http://jsfiddle.net/gh/get/jquery/3.1.1/highcharts/highcharts/tree/master/samples/highcharts/members/renderer-label-on-chart/
Goal : define and execute periodically functional rules of your project. A rule is defined by a description and a state. A rule session defines a new test or acceptance session.
Goal : settings should be reduced to minimum but some elements need to be configured like the connection to Jira if we want to import the stories from this tool.
Goal : Keep an eye on historical statistics of a project (evolution of velocity, number of stories handles per sprint...and so on)
Goal : allow members to have their own space to allow them to edit their own calendar. Roles might be:
- scrum member (permission to edit vacation)
- stakeholder (permission to view and edit charts)
- scrum reporter (permission to edit stories)
use the API https://holidayapi.com/ to get the list of "public" holidays (depends on country)