but I'm not sure if this is the right way to go. We have a tool that we use at work called Zenhub which adds a Kanban board and Epics so I feel like there's a nicer way to structure our user stories. Saving Changes...
Scrum is a framework.
It tells you what you should do, but not how you should do. The "How" is open to you and your team decide.
So, for me the article is valid, and gives an excellent view of "How" to implement Scrum using a simple tool as gitHub.
Regards Saving Changes...
M. Sahir A. Shatiry, PMI-RMP, PMPSenior Hook-up and Commissioning Engineer| Petronas Carigali Sdn BhdIpoh, Perak Darul Ridzuan, Malaysia
what is Github? Saving Changes...
Bret PiontekSenior Project Manager, Global eCommerce| Tacit KnowledgeOakland, Ca, United States
Github could work if the project leader (or Scrum Master) is a technical lead and the team doesn't communicate outside it's own technical area. If the project team is cross functional between technical and business though, Github could pose problems for non-technical folks, because it's primary function is as a code repository, not a task management tool.
Tools like JIRA (and countless others) have all kinds of integration abilities that can tie Github commits back to user stories and defects. A tasking tool such as this is far better suited for a more diverse set of project team members that may use business language while others are more technical. Saving Changes...
