Metrics in New Project

[Fabrício Diego Ferreira]

Hello guys.

I'm starting on a new project, with a new team in a new company.

I would like to know which metrics would be interesting to use and why.

Could you help me with the most relevant ones?

Thank you in advance!

PS: Although I'm asking directly from my personal account, all answers about metrics apply to a company-managed account.

[Bill Sheboy · Accepted solution]

Hi @Fabrício Diego Ferreira 

What problems is your team trying to solve?
How does your team work, and how do they interact with other teams?
What goals does the organization have?
What things are you trying to optimize? (e.g., trade off matrix areas)

Measurement supports doing various things, and measuring without context is not helpful.  Instead it is "waste work" and possibly producing "vanity metrics" (i.e., measuring something with no real value).

I recommend discussing the above questions with your new team and company to learn what measures might help support them, and then experimenting to learn which measures help.

Kind regards,
Bill

[Fabrício Diego Ferreira]

Ótimo ponto.

O backlog está uma bagunça. É um projeto de migração de reescrita de uma aplicação móvel.

Não sei nem por onde começar a medir justamente pela desorganização do momento. Demandas entram a todo momento, tudo é prioridade e o mais rápido possível.

Tanta coisa que meu PM nem está utilizando o JIRA, por hora, e sim planilha Excel, para ganhar tempo.

Então confesso que estou perdido até mesmo para responder à essas suas perguntas, que fazem todo o sentido.

[Fabrício Diego Ferreira]

Utilizamos histórias e sub-tarefas para o projeto. As histórias são estimadas em pontos e as sub-tarefas em horas.

[Bill Sheboy]

From what you describe, you may want to discuss with your PM how to improve the backlog, starting with cleanup / prioritization of the top single item and how they measure "success".  Knowing those things may help to identify what is next and how to assess progress.

[Ste Wright · Accepted solution]

Hi @Fabrício Diego Ferreira 

Is the Project brand new? Or you're entering a Project which already exists with data?

And is this team level or portfolio level? Do the teams use Scrum or Kanban?

Ste

[Fabrício Diego Ferreira]

Olá.

O projeto é novo. Uma aplicação mobile está sendo reescrita do zero. Antes era um site (webview) e agora está sendo totalmente reescrito para ser um app mobile. Como os disponíveis em lojas Google ou Apple.

O projeto está a nível de portfolio. Utilizamos "Scrumban".

Utilizamos histórias e sub-tarefas para o projeto. As histórias são estimadas em pontos e as sub-tarefas em horas.

Essa informação pode ser útil.

Utilizamos Kanban como configuração dos quadros, mas trabalhamos com "Scrumban".

[Ste Wright]

Hi @Fabrício Diego Ferreira 

What reports are useful will largely depend on what's important to your team or stakeholders.

I'd check out...

• Report options - https://www.atlassian.com/software/jira/features/reports
• How to generate a report - https://support.atlassian.com/jira-software-cloud/docs/generate-a-report/
  • For Scrum...
    • Burnup/Burndown Charts are useful to show progress
    • Velocity Chart can show how much progress is made against the target each Sprint
  • I'd also check out...
    • Control Chart, which can help with cycle/lead time of issues
    • Cumulative Flow Diagram, to help identify bottlenecks
• Dashboards, which have some additional gadget report options. You can also visualise data from multiple Sprints, etc here - https://support.atlassian.com/jira-work-management/docs/what-is-a-jira-dashboard/
  • You can see a list of pre-installed gadgets here - https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/
    • Check out...
      • Bubble Chart - visually identifies popular/significant issues
      • Pie Chart
      • Resolution Time
      • Sprint Health / Sprint Burndown

---

Note: This assumes the data is clean and consistent though - if not, I'd focus on improving the hygiene alongside reporting

Ste

[Vitalii_Bobak_SaaSJet]

Hi @Fabrício Diego Ferreira  and everyone who is looking for the solution.

Here are some metrics that can provide valuable insights for your team, especially in a company-managed project:

1. Cycle Time

• Why it's important: Tracks how long it takes to complete a task from start to finish. This metric helps you identify bottlenecks and improve delivery speed.

2. Lead Time

• Why it's important: Measures the time from when a request is made to when it’s delivered. This metric is critical for understanding responsiveness to business needs.

3. Wait Time

• Why it's important: Tracks how long issues remain idle between statuses. Reducing Wait Time improves efficiency and team productivity.

4. Time in Progress

• Why it's important: Focuses on active work, helping you ensure resources are efficiently allocated.

5. Resolution Time

Why it's important: A critical metric for understanding how long it takes to resolve issues and meet SLAs.

You can get all of the with one tool - Time Metrics Tracker add-on 

Also you can measure these metrics effortlessly and gain actionable insights to optimize your project delivery by adding this data in your jira dashboard.


You can even set alerts to stay on top of deadlines or export reports in Excel/CSV formats for sharing with stakeholders.

Add-on developed by my team. 

Best of luck with your project! 😊