Sprint Planning and Management using Task Boards in GitHub

We look at how to set up a Task Board to plan and manage a Sprint in a project following an agile development process. Sprint planning involves picking which features - i.e. User Stories - will be addressed during a given Sprint, and how each of those User Stories can be broken up into units of work known as Tasks that are then assigned to and implemented by members of the team. Spikes - additional units of work that are not directly related to any User Story can be added onto the Task Board where necessary to make it into a tool for realistically tracking everything that every team member is working on at all times.

[OgenBertrand]

Thank you Mr Barstein this video has thought me a lot

[victoria-exito]

Hi where do we register the Daily stands up and Retro meetings? Thank you!

[balsbalubalu]

Is there provision for entering story points and create epics and give a hierarchical view of epic and the taskss/stories/issues under the epic

[shynsky]

Nice video. Without actual connection of User Story to Tasks it's really hard to track what's going on from sprint to sprint, especially if you work with the bigger team. If all tasks are resolved, there's no way for User Story to update itself as "Done", right?

[dud]

Can you use task boards on iOS (iPad)?

[hligfl]

Are most of AGILE Github developpers working with this method ? Because it seems like a good standard. For example is the github Angular organized in this kind of manner ?

[johnhartley]

Hi, nice practical demo, but I note github has changed the layout, .eg. I can't create a new label by clicking on it :( any ideas?

[VISHALRAMESHRAOGAYAKAWAD]

how to add Add cards or user stories in board because it's not visible for me.

[wheatonrecurrence]

Would you use the milestone as user stories?