Scrum Board POLICIES - sarayu-pr11/team-narks GitHub Wiki

We are using the Kanban style of scrumboard. We found this to be the most useful because the different columns allow us to organize issues and add mobility. We can easily see all of our issues and we are able to quickly move them to another column whenever we want. We also like all the different variety of columns we have. From "To DO" to "Backlog" any member of our scrum team is able to see where we are at our project, and add their own issues or move it around if they also want to.

Policies:

Scrum Master Policies:

• Each Scrum Member must commit and label their commits accordingly to their work, so it is EASIER for scrum master to create issues and add to read me.
• Each Scrum Member should make sure they complete and commit all work so that Scrum Master can add issues
• It is each Scrum Member's responsibility to move their own issues on the board to certain columns - Scrum master just creates and facilitates
• Any questions about issues/read me/scrum board, ask Scrum Master
• API's must be completed by Next wednesday so we have time to check and make sure everything is running
• IMPORTANT!! if issue you committed has bugs, needs enhancment, etc. use the tags and colors Git provides to label accordingly