Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,670
Community Members
 
Community Events
176
Community Groups

Jira Reports: Measuring Progress in Agile Teams

Hi Community!!

Recent years of work have brought us to the stage where we need to have a measurement of how our team is progressing with work.

Be it your team is following the scrum method of development or kanban, Jira provides us a way to measure the team's progress.

Before we move into reports, Jira needs data in order to show reports or correct configuration for the board.

It's important we plan our backlog and a sprint or continuous work with the kanban template with a correct set of data before we start working on a set of featues.

Its also important team plans the development of the features in set of releases which can be mapped to releases feature in Jira.

For example: Let's say we built a backlog for a product in Jira and we are following Sprints in order to release the features, now the data importance I was talking about was when we move the set of issues to Sprint backlog we have to make it has estimation effort, which version it is planned to be released in, only then your reports can show how can estimated effort has paved your way in developing a product.

Make sure whenever you create a new project and start building software your backlog makes sense with all the data in it either before you start the sprint or working on issues with the correct configuration on board.

For more information on how to build a backlog, sprint backlog, and configuration of board checkout the university course here

Let me know your thoughts on the article and how you plan to build a backlog and sprint's issues in order to have the correct reports in Jira

Thanks,
Pramodh

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events