Best Agile Project Management Training Tips for Using Jira

[#1]

Hello Community readers, today I will be covering the best Jira agile project management tips

                                     

            Let’s first agree that your team can only succeed if Jira is configured following either Atlassian recommendations, or SMEs advice. Let’s assume that your admin has done a good job with Jira Configuration. How can a team achieve their best results while using Agile for project Management?

In this post, let’s assume that there is either a Scrum Coach/Master or a PM following the agile methodology framework (Sprint Ceremony, Standups, …). 

In an Agile Project, the very first step is to:

• Have stories in the backlog that describe the user’s requests in a concise way 
• Try to break the requirements into Stories that can be done within the Sprint. Lots of requirements may lead to unfinished work that can be dragged to other Sprints.
• Get into the habit of having subtasks within Stories. If anyone wants to get an update about your progress, they can get it just by looking at your Stories
• Don’t overcommit. Keep in mind unexpected things can happen in life
• Start working on Stories that can be done quickly
• Set up a demo with the Stakeholders to make sure that you are heading the right way.
• If requirements in one Story keep changing, make sure to flag it then report it to the Scrum master and the team, so none of your other stories are at risk. 
• If you incorrectly evaluated the work and story points make sure to report it to the Scrum master because it can happen to the best of us even when we worked on similar tasks before.
• Always leave 1 or 2 story points for last minute requests that will require your immediate attention
• Last but not least don’t create unnecessary work. Keep things easy and simple. Don’t complicate the steps to achieve the desired outcome.

While the tips above are a simple way to describe some familiar scenarios, it is understandable that these Stories you are working on are linked to Features and Epics, which are also linked to Initiatives. They all have a high visibility and were prioritized because there is a need for some problems to be resolved within the organization.

One important thing to note is that these are general tips for Atlassian Jira users; some minor tips may have been omitted. If you have any suggestions you would like to share please comment them below.

Best,

Fadoua Boualem

[YY Brother]

Really good practices 👍🏻 Thanks @Fadoua 

[Mohamed Benziane]

Really good article and very good tips !!! 

[Jack Brickey]

@Fadoua , great article! Thank you for sharing. 

[carolyn french]

@Fadoua - excellent tips!

[Samuel Gatica _ServiceRocket_]

@Fadoua great stuff! and I totally agree with this point - 

• Always leave 1 or 2 story points for last minute requests that will require your immediate attention

[Dave Liao]

@Fadoua - thanks for this article!

I recommend sub-tasks[1] to teams so they can get into the habit of actually breaking down their stories. Love the added benefit of making it easier for stakeholders to see a story's status!

[1] or checklists, if they're using a Jira checklists add-on...

[Fadoua]

Thank you guys for sharing your feedback, I really appreciate it!

[Liz Tanner]

@Fadoua Your last point:

Last but not least don’t create unnecessary work. Keep things easy and simple. Don’t complicate the steps to achieve the desired outcome.

Love that last Lean bullet. I worked with an Agile team and the mantra was: Don't make waste and KISS: Keep it Simple, Stupid.

Awesome article, @Fadoua, it's the ultimate Agile Cheat-Check-Sheet-List! 

[Fadoua]

Thank you @Liz Tanner for your kind words and kudos!