Getting to work
Leading an agile project
On this page
In this section
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
Ready to start working? You should have built a backlog and planned your version 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. Both Scrum and Kanban use boards (Active sprints/Kanban board) and wallboards to keep your team on track.
Overview
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 project, Checking the progress of a version, and Using Active sprints
Working in 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
Already finished work for the version?
Next: Release your version
Project lifecycle
NEW PROJECT → BACKLOG → NEW VERSION → WORK → RELEASE → REPORTING
In this section
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications