Hi Sergio, the error might be caused because you’re using a “Team Managed” project. The data only works with “Company Managed” projects that use the Scrum template. Let me know how you go.

Thank you!

Hi Salman, thanks for your patience with my response. If a bug is found during the Sprint we need to determine if it’s urgent or not. If it’s urgent then it can be added to the current Sprint but the team will need to potentially adjust the scope of their Sprint Plan if they have not factored in time for this. If the bug is not urgent, then it is added to the Product Backlog and the Product Owner decides on its priority. The bug is fixed in a future Sprint and does not affect the teams Sprint Plan. Hope it helps!

Hi @stabassam, yes that’s what it is referring to

@@AxisAgileAppsthanks loved this. Is there an extended version?

@@stabassam Many thanks! Yes, the extended version is here: kzfaq.info/get/bejne/nruYhtOKlr2anp8.html

Thanks!!

My pleasure, thanks!

Hi @CuriousScrummer, my apologies on the delayed reply. Yes that’s correct, use sub-tasks to distribute the tasks for a User Story among your team members. You can see how I do that in the next video (“part 3”) of this series.

Thanks! And our pleasure :)

Thanks Jodakan, it's certainly not a mandatory approach. If you are working with an Agile team it's important to voice that with your Scrum Master so they know it may not be something the team likes doing and can address it.

Thanks Anna! Our pleasure :)

Hey Salman, take a look at our playlist here: kzfaq.info/sun/PLL-72IrJnz2w_8JyHQVlWSw2w3eP9tL76 Hope it helps!

Good question! The process helps with removing bias and anchoring when it comes to estimation. By allowing each person to share how much effort they believe the work is without being influenced by others can lead to better discussions about what's realistically involved. Hope that makes sense and thanks for watching!

Hi Toufiq, my apologies on the delay. Typically the story points are decided by the SM and Development team, not at Sprint Planning, but at Product Backlog refinement sessions which occur during the Sprint.

Hi Toufiq, sorry again for the delay. In Jira a "release" signifies the release of a product increment to customers. For example, the "First release" would be the first version of the product given to customers, and the "Second release" the second, or next version that is given to customers. You'll notice that in Jira, the terms release and version refer to the same thing.

You are welcome! Thanks :)

Our pleasure Shewaye, thanks!

You're welcome! Thanks!

It's most likely you don't have the right user permissions to start a Sprint, or you might not be using the "Scrum" project template.

Our pleasure! Thanks Ivan :)

You are welcome! :)

Hi there! Do you see "Reports" in the left panel? If not you might be using a "Team Managed" project. If that's the case you'll need to click on project settings at the bottom of the left panel, and then click on "Features" and enable reports. That said, keep in mind that the Release Burndown and Version Report are unfortunately not available with Team Managed projects.

Thanks @smcla!

Hi Ahmed, sorry about the late reply. If a story is not completed in a release, then it should be shifted to a subsequent release. I.e just update the release it is associated to.

Thank you!

My pleasure!! hope it helps :)

Many thanks!

Our pleasure!

Our pleasure Amudha, glad it was helpful! :)

You're welcome!

My pleasure!

Thank you Amy!

Many thanks!

Certainly! I think I received your message via our support contact form - did you receive my reply?

Hi @sugarfaryprinces, sorry for the delayed reply! I typically create a Jira "Version" for each release, so in your case there would be a new version each week with all the Product Backlog items that were deployed. It's sounds like that's what you're already doing - is that correct? If so, tell me a little a bit more where you're experiencing issues. Look forward to hearing from you. Richard

Hi @@AxisAgileApps thanks for your response. So the situation that we have at the moment is that these versions that I have in Jira are automatically created from GitHub when code will be sent from Development environment to Integration environment. There is no exact planning ahead regarding what goes in to a release. There is only sprint planning. What can I do to improve that process from a release perspective and have a better overview?

Thanks Thyge! Our pleasure :)

Hi Aditya, to download the sample data you'll need to go to the url: axisagileapps.com/sampledata/ A form will load up on the left, sometime's there a slight delay. If it doesn't load up for you let me know :) Thanks, Richard

Thanks Sumith!! Our pleasure :)

Thanks Sumith. We'll have more videos coming soon :)

Hi Sanushka, in Jira Epics represent a collection of Product Backlog items. So they're great for signifying larger pieces of work that are going to take several Sprints to deliver. This helps both the team and stakeholders understand how the project is progressing, and what the team is working on, from a higher more broader perspective. For a more detailed explanation you can check out my video on the Product Backlog here: kzfaq.info/get/bejne/nruYhtOKlr2anp8.html Hope it helps! Richard

Thanks Randall! it's our pleasure :)

Thanks Milos! :)

Thanks for the suggestion Milos! We've added it to our video backlog