Getting to work

You should have built a backlog and planned your versions and epics by this stage. Time to get your team working!

The documentation in this section will help you use Jira Software to coordinate your team's work. For Scrum, these tasks include planning and running sprints. For Kanban, these tasks include monitoring work in progress. In both Scrum and Kanban projects, you can use boards (Active sprints/Kanban board) and wallboards to keep your team on track.

Search the topics in 'Getting to work':

 

Working in a Scrum project

Scrum projects are based around working in sprints. A sprint is an iteration of work (two to four weeks) that is typically part of a version. Each sprint starts with a planning meeting where the work is estimated and assigned to the sprint. At the end of each sprint, a retrospective or review meeting is held before the next sprint is planned.

In Jira Software, sprints are planned using the Backlog of a board. Once a sprint has started, the sprint is monitored using the Active sprints of a board.

Learn more: Running sprints in a Scrum projectChecking the progress of a version, and Using Active sprints

Working in a Kanban project

Unlike Scrum, Kanban doesn't use the concept of sprints. Rather, a Kanban project is based on the continuous delivery of work. When tasks are completed, more tasks are pulled into the work-in-progress pipeline. Constraints are placed on the amount of work that can be done at one time, so that the team is not overburdened.

In Jira Software, work is managed and monitored using the Kanban board

Learn more: Monitoring work in a Kanban project and Using your Kanban backlog

Already finished work for the version?

Next: Release your version

Project lifecycle

  NEW PROJECT   BACKLOG    NEW VERSION    WORK    RELEASE    REPORTING

Last modified on Jan 30, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.