Jira Work Items Tutorial
In this tutorial, we'll explain how to work with work items in Jira. Note that the team rituals you do outside Jira - like sprint planning meetings, retros, and daily standups - won't be covered here. You can read up on those in How to do scrum with Jira.
Durata lettura:
10 minuti.
Destinatari:
Nuovi utenti di Jira che non dispongono di alcuna conoscenza della soluzione
Prerequisito:
- Hai creato un account Jira
-
Aver creato un progetto Jira
In Jira, teams use work items to track individual pieces of work that must be completed. Depending on how your team uses Jira, a work item could represent a project task, a helpdesk ticket, a leave request form, etc. In Jira, work items typically represent things like big features, user requirements, and software bugs.
Create a work item
There are a few different ways to create work items:
Dalla barra di navigazione in alto, in qualsiasi posizione in Jira
Nel backlog
Sulla tua board (solo progetti gestiti dal team)
Opzionale: creazione di sottotask
Work items can also have sub-tasks that are assigned and tracked individually. You might create sub-tasks for any of the following reasons:
- To split a work item into even smaller chunks
- To allow various aspects of a work item to be assigned to different people
- To create a to-do list for a work item
Per creare un sottotask:
- Navigate to a work item, and select more ( ••• ) > Create Sub-Task.
- Inserisci i dettagli necessari, quindi clicca su Crea.
Estimating work items in your backlog helps you to predict how long portions of the backlog might take to be delivered.
Why estimate work items? Estimation is all about velocity.The primary purpose of applying estimates backlog items is to use that information to work out how long it will take to deliver portions of the backlog.
Nei team di sviluppo tradizionali, i manager stimavano gli elementi in termini di "ore uomo". Potevano quindi contare le ore nel backlog, suddividerle per il numero di persone nel team e le ore della settimana e definire in questo modo una data prevista. Naturalmente, queste stime si rivelavano spesso estremamente imprecise perché non tenevano conto delle caratteristiche naturali del team (in termini di sovrastima/sottostima), delle interruzioni impreviste o dello sviluppo delle prestazioni del team nel corso del tempo.
So in the Scrum world, most teams don't try to achieve estimation accuracy; instead they aim to achieve a reliable velocity. Velocity is a measure of the number of estimation units that a team tends to complete from sprint to sprint. After their first few sprints, most teams will achieve a reasonably consistent velocity. Armed with velocity and estimates on backlog work items, teams can predict how long portions of the backlog will take to complete.
Ad esempio, se un team ha una capacità "ore uomo" di 120 ore in ogni sprint ma una velocity di 60 ore, la velocity di 60 ore può ancora essere utilizzata per stimare il numero di sprint che saranno necessari per completare parti del backlog. A questo punto, potresti legittimamente chiederti che fine abbiano fatto le altre 60 ore e ipotizzare che siano presenti dei problemi nella produttività del team. Tuttavia, i due aspetti di solito non sono correlati: le stime di un team rappresentano semplicemente un'immagine del grado di difficoltà degli elementi e saranno sempre influenzate dal comportamento naturale del team (in termini di sovrastima/sottostima) e dal sovraccarico organizzativo. La velocity è tutto ciò che conta dal punto di vista della pianificazione.
Most teams estimate using story points. Story points measure the complexity of one work items relative to others. This makes sense because the main questions to be answered are 'How much work can we realistically commit to completing this sprint?' and 'How long will this part of the backlog take to deliver?'. A story point approach can deliver the answers to these questions without the anxiety around 'accuracy' that teams feel when asked to estimate in hours.
Per ulteriori informazioni su come monitorare le stime e la velocity, dai un'occhiata al nostro tutorial sul burn-down.
To set an estimate for a work item:
- Immetti una stima.
Posso modificare una stima dopo averla inserita? In sintesi, la risposta è sì. Ma se modifichi il valore di stima dopo l'inizio di uno sprint, questo verrà visualizzato come modifica dell'ambito nel grafico burn-down.
If you're finding it hard to estimate work items, that's totally normal! Check out our estimation guide for tips and tricks on finding the right estimates for your work items.
Rank your work items in order of priority
Ranking your work items in order of priority allows the team to see which work items they'll be working on next. To rank your work items, navigate to your backlog or board and click-and-drag your work items to order than based on priority. Here are some examples of where you might do this:
-
In a Scrum project, when planning your next sprint you might rank the work items in your backlog, and then decide to put the first 10 (or however many work items the team is capable of completing) into the sprint.
-
In a Kanban template, you might rank the work items in the To do column, and have team members take a work item off the top of the list when they need more work to do. With this approach, the column with all To do work items will need constant attention as priorities shift.
Note: You must have the Schedule Work Item and Edit Work Item permissions for the work item you want to move higher or lower on your board.
Flag a work item
You have the option to flag a work item, which look like this:
Flagging a work item is useful because it encourages collaboration and communication throughout the team. Here are some examples:
-
You're working on a task, but realize you don't have capacity to finish it off. You can flag the work item, and a team member with spare capacity who looks at the board can jump on and help.
-
A work item you're working on becomes blocked. You can flag the work item, add a comment explaining the blocker, and move on to the next task. Anyone who looks at the board will see that it has been flagged, and understand what's going on when they open it.
To flag a work item:
-
Vai alla board.
-
Right click a work item.
-
Premi Aggiungi flag.
Transition work items
Transitioning work items shows progress across your workflow. To transition a work item from one column to another, drag a work item and place it in its new column.
Note that if you find that you're not able to transition a work item into another column, it may be because the workflow for your project is restricting you from doing so. What makes Jira so powerful is that administrators can enforce certain rules on the project's workflow, like forcing bugs to go through a QA column, or not allowing Stories to go straight from To do to Done. For more information, check out our workflow documentation.
Filter work items
A work item filter allows you to hide the work items you don't want to see, and zone in on the ones you want to focus on. Jira has Quick filters, which allow you to filter the work items on your board. Here's what they look like on Scrum/Kanban boards:
-
Search bar: Display work items that contain a search term, and hide the rest.
-
Quick filters menu: By default, you can filter by work items assigned to you, and work items recently updated. Any Quick filters you create will also display here.
-
Assignee menu: Only display work items assigned to people you select.
Per creare filtri rapidi (board Scrum e Kanban):
- Pulsante con puntini di sospensioneVai alla board e seleziona altro (
) > Impostazioni della board. - Clicca sulla scheda Filtri rapidi .
-
Immetti un nome, una query JQL e una descrizione per il filtro. Per ulteriori informazioni su JQL, dai un'occhiata alla nostra documentazione di ricerca avanzata.
-
Clicca su Aggiungi.
Utilizzo dell'automazione come arma segreta
Jira is the place where work lives. Sometimes a lot of work can live there! Automation is the key to keeping all work items up to date and in order. See the most commonly used automations in the Jira automation template library.
Vuoi saperne di più?
For more detailed information on working with work items in Jira, check out our documentation on work items. Excited to get started? Check out our free Jira templates.
Vuoi chiederci qualcosa? Rivolgiti all'Atlassian Community.
