Modello di approvazione del documento

You can decide whether you want your scrum projects to be managed by your team (team-managed projects) or centrally by an admin (company-managed projects).

Team-managed projects are ideal for autonomous teams who want to get going quickly and control their own projects and workflow. They can be set up and maintained by anyone.

Company-managed projects are the best choice if you want to standardize configuration across multiple Jira projects in your organization. These are set up and maintained by a centralized admin.

Before a sprint can start, you will need to populate your backlog with all the work your team needs to do. The items in your backlog (which might be user stories, design changes, bugs, etc.) will become the building blocks for the features or products you are starting to build in your board and timeline.

Once you’ve built your backlog, it’s time to prioritize what work items the team will complete in its first sprint. Sprints are fixed time periods (typically two weeks) in which your team completes a set amount of work. While your board may be as simple as “To do,” “In Progress,” and “Done,” you can change the workflow to mirror your team’s own unique way of working.

Now that work is humming along, use the timeline included in your scrum template to view the big picture, track dependencies, and easily adjust priorities. This helps your team plan and track how you’re making progress on your project, stay ahead of potential blockers and communicate the status of work to stakeholders.

Deliver value to customers faster with real-time insights at your fingertips. Jira Software enables teams to make data-driven decisions with agile reports including burndown charts, sprint reports, dashboards, and more.