Відео

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!

It's my pleasure! :) thanks for watching

Thank you!

My pleasure!! hope it helps :)

Many thanks!

Our pleasure!

You're welcome!

My pleasure!

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: ua-cam.com/video/hUhSpY1W6nk/v-deo.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

HI Oshadhi, unfortunately Jira does not provide this functionality. But you can install an app from the Atlassian Marketplace (e.g. Tempo Timesheets) which will allow you to do so: marketplace.atlassian.com/search?query=time%20tracking

You're welcome! :)

Hi Mark, sorry about the delayed reply! Yes that's right, Jira doesn't provide an ability to manage capacity but there's several third party apps on the Marketplace which can help with doing so.

Thanks Akhil, I'll add that one to our video backlog.

Nice one Khalid! Spot on

My pleasure Adebanke, thanks for watching! :)

Thanks Dandi!!

Thanks Amir! Our pleasure :)

Thanks for sharing! :)

Thanks Telugu!

lol thanks for watching @positivemindset723!

Hey BovineOx, check out my video on Sprint Planning using sub-tasks and time to see how it's done :) Here's the link: ua-cam.com/video/94sqZadKOFI/v-deo.html

Hi BovineOx, firstly my apologies on the delayed reply. Those are excellent questions and I'll try my best to answer them below. There is an assumption that the team has some idea of what’s involved based on their experience and what they know. If they have absolutely no idea what’s involved an Agile team will typically start with some research or create a Proof of Concept before applying a broad Story Point estimate to the implementation. It’s also important to remember that an Agile team should be continually refining their Product Backlog Items and in turn their estimations. For example, a single Product Backlog Item that was given 100 points might be broken down into smaller Product Backlog Items, and further detail gathered based on priorities. I.e. the higher priority items would have more detail gathered (i.e. DoR criteria), where as the lower priority Product Backlog items may be left fairly vague (until they become a priority). In case you haven’t seen it, I do have a video on that topic :) here it is: ua-cam.com/video/hUhSpY1W6nk/v-deo.html I hope that makes sense, but if not or if you have any other questions let me know! Thanks, Richard

Hi Yannick, thanks for letting me know! We have added it to our backlog of videos.

@@AxisAgileApps you are awesome! Thank you! Kindly share the link to the video for creating custom control checkbox for the DOD. I can't seem to find it.

Hi @Qemynl, my apologies on the delayed reply! Hmm it sounds like you may not have any sub-tasks that are "in progress", or maybe there are no sub-tasks in the current Sprint. Perhaps try with just "sprint in OpenSprints() and issuetype in (Sub-task)" - if you see the sub-tasks listed then they must not be "In progress". If you see no sub-tasks listed it means that there are not sub-tasks in the current Sprint. Let me know how you go and if I can help further. Thanks! Richard

Thanks for letting me know Ashwini!

Great question Ashwini. The ideal situation is to allow the team to run a Sprint so that we have a realistic idea of what they could achieve, but if you have stakeholders who are asking for an estimate beforehand (and they can’t wait just 2 weeks) then the first thing to do is let them know that there is a large amount of uncertainty at this point in time. The team has not worked together before, it is a new project, and there are many unknowns that the team will only become aware of during the course of the project. With that said, we can provide them with an estimate, but we have to factor in the uncertainty. To factor in the uncertainty we will include it in the “buffer” value I mentioned within the video. e.g. we add an additional amount of time to the estimated date to cater for unknowns and fluctuations in scope/velocity that could occur. It’s important to be transparent about what makes up this “amount of time”, such as catering for team members getting sick, disruptions during the sprint, new requirements that need to be added etc So once expectations have been aligned, and stakeholders understand why a buffer needs to be added, I will typically gather the team together to “simulate” a Sprint. We’ll look over the top priority product backlog items (which should be well-understood, sufficiently detailed and appropriately sized) and the team decides what they could realistically get done within a Sprint cycle. With that, you will have an initial Velocity and can go through the calculation. The last tip I’ll give here, is to continually readjust the buffer as the uncertainty begins to drop. You can then continually re-appraise stakeholders with more precise estimates the close your team gets to the end of the project. I hope that makes sense! If not, please let me know and I can clarify :) Lastly thanks so much for checking out the videos and your positive feedback, we really appreciate it!!