Hi Richard, your videos are very informative and the concepts are very well explained. Could you please make a series on the scrum reports (burndown , burnup etc) capacity planning report , resource utilisation etc created and used by Scrum masters in a project. In short all the charts or reports a scrum master would use in a project
@rakeshggiri5 күн бұрын
Arambh (Start), Jyestha (Calendar Month)
@sergiohoracioninodiaz4419 күн бұрын
Thanks Richard for sharing your knowledge and helping me improve my skills. I'm trying to upload the csv into the jira free account, but it seems the CSV import mthod is not working :(. Any workaround that could help me, please? Thanks in advance
@AxisAgileAppsКүн бұрын
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.
@kutra10016 күн бұрын
Hekduum koshthi
@learning.place78621 күн бұрын
very informative
@AxisAgileAppsКүн бұрын
Thank you!
@markusklyver627722 күн бұрын
Scrum is astrology for management and CEOs
@Salmanmushtaq-cs3jm23 күн бұрын
Thanks for the video. 1 question: What about if we received a bug (new) so we need to add in some EPIC or add a task (type bug)? How to handle the bugs in current sprint and in product backlog?
@AxisAgileAppsКүн бұрын
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!
@stabassam27 күн бұрын
Thanks, is version here referring to the release version?
@AxisAgileAppsКүн бұрын
Hi @stabassam, yes that’s what it is referring to
@stabassamКүн бұрын
@@AxisAgileAppsthanks loved this. Is there an extended version?
@AxisAgileApps19 сағат бұрын
@@stabassam Many thanks! Yes, the extended version is here: kzfaq.info/get/bejne/nruYhtOKlr2anp8.html
@mario17-t3427 күн бұрын
Thanks, How I can tell if issue belong to Backlog ? I work with Jira data import/API and trying to find clear criteria how to set switch for Jira issues Backlog_YN
@addicttomusicshagun5779Ай бұрын
Amazing, you're the only one who explained it well so far.
@AxisAgileAppsКүн бұрын
Thanks!!
@ehsensehven9579Ай бұрын
Great explanation man. Thank you
@AxisAgileAppsКүн бұрын
My pleasure, thanks!
@sheilasarkodie4725Ай бұрын
Hi how did you created the site you choose the project from.. with Jira software, your work, project, dashboard, teams create etc. thank you
@CuriousScrummerАй бұрын
This is a great video! However, help me understand Richard, I have 6 team members, and from above example if I have a velocity of 21 with around 5 user stories being taken, how do I know which team member is working on what User story?, Do we further add subtasks? Ex for US "Login to account" , when there is UI, API and backend changes involved, how do we further divide this 8 story pointing between 3 members? Thanks in advance
@AxisAgileAppsКүн бұрын
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.
@r.s.7085Ай бұрын
Very clear and detailed! And exactly my opinion - that is very often a missing link in teams which try to work with scrum. Thank you for your helpful video
@AxisAgileAppsАй бұрын
Thanks! And our pleasure :)
@MarcinScholkeАй бұрын
check LOV111VOL maybe it is something for You :)
@JODAKAN0815Ай бұрын
This makes sense i just would hate to have this implemented at my workplace
@AxisAgileAppsАй бұрын
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.
@acuxartАй бұрын
This was super useful, specially with the examples & showing it on Jira. Thank you so much!!
@AxisAgileAppsАй бұрын
Thanks Anna! Our pleasure :)
@Salmanmushtaq-cs3jmАй бұрын
Please make video on estimation plan
@AxisAgileAppsАй бұрын
Hey Salman, take a look at our playlist here: kzfaq.info/sun/PLL-72IrJnz2w_8JyHQVlWSw2w3eP9tL76 Hope it helps!
@TacBladesАй бұрын
Why gamify and formalise such a simple activity of discussing and agreeing on something ?
@AxisAgileAppsАй бұрын
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!
@Itstoufiqsfitness2 ай бұрын
I have a question here. Is the total story points in product backlog decided by the product owner? From what I understand the story points are decided by the SM & development team during spring planning while moving them to sprint backlog. Or am i wrong?
@AxisAgileAppsАй бұрын
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.
@Itstoufiqsfitness2 ай бұрын
Sorry Im a newbie to scrum. Firstly could you please explain what is a release and why is it used and for what purposes
@AxisAgileAppsАй бұрын
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.
@adGurtiza2 ай бұрын
Very informative. Thanks a lot!
@AxisAgileAppsАй бұрын
You are welcome! Thanks :)
@shewayegurmessa87802 ай бұрын
I cannot thank you enough❤❤❤❤
@AxisAgileAppsАй бұрын
Our pleasure Shewaye, thanks!
@kperegbeyimabelegude92532 ай бұрын
You are the best. Thank you for this video.
@AxisAgileAppsАй бұрын
You're welcome! Thanks!
@Velocity04282 ай бұрын
Why don't I have a "Start Sprint" button like you do?
@AxisAgileAppsАй бұрын
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.
@IvanMusaelyan3 ай бұрын
Thanks for amazing description!
@AxisAgileApps3 ай бұрын
Our pleasure! Thanks Ivan :)
@inquestyle3 ай бұрын
Thank you for the clear and simplified explanations.
@AxisAgileApps3 ай бұрын
You are welcome! :)
@chrischelsisters55583 ай бұрын
Hi Richard, i can't see forecast and management reports , how can i enable ? pls reply Richard
@AxisAgileApps3 ай бұрын
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.
@smcla3 ай бұрын
For those wondering, Parent ID is now Parent
@AxisAgileApps3 ай бұрын
Thanks @smcla!
@ahmedtrabelsi85523 ай бұрын
Hi, What if a story is not completed on a release? How can we handle this case in jira? Should we juste update the release or we keep the old and add the new release (like sprint field)? Thanks
@AxisAgileAppsАй бұрын
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.
@ankitade22343 ай бұрын
Great content!!
@AxisAgileApps3 ай бұрын
Thank you!
@sridevisri38984 ай бұрын
Fantastic. I am using the time sheet now. Thanks for this wonderful series.
@AxisAgileApps3 ай бұрын
My pleasure!! hope it helps :)
@madhankumar18114 ай бұрын
fantastic videos
@AxisAgileApps3 ай бұрын
Many thanks!
@qasim35194 ай бұрын
thankyou really helpful lesson
@AxisAgileApps3 ай бұрын
Our pleasure!
@amudhaekambaram41264 ай бұрын
Awesome video! That was my next question... how to incorporate planning poker points in Jira. So there you ended the video with information on Velocity. Thank you 🙂
@AxisAgileAppsАй бұрын
Our pleasure Amudha, glad it was helpful! :)
@sanketdeo28694 ай бұрын
Thank you so much !!
@AxisAgileApps3 ай бұрын
You're welcome!
@sanketdeo28694 ай бұрын
Appreciate your Valuable Guidance , Thanks !! 🙂
@AxisAgileApps3 ай бұрын
My pleasure!
@RasamRostami4 ай бұрын
Great video. I have 2 questions: - How can everyone in delivery team provide an estimate when they are not expert in every area? For example how can a front-end developer provide story points for a work that includes back-end points as well? Is their estimation valid? - What would be the role of designers in sprint planning session? I assume they are mostly a part of backlog refinement (designing for items) process, but should they be included in sprint plannings too?
@amydesai42925 ай бұрын
You are Awesome. Simple Explanation.
@AxisAgileAppsАй бұрын
Thank you Amy!
@klidraik5 ай бұрын
Good video. Thanks.
@AxisAgileApps5 ай бұрын
Many thanks!
@ishamammastudio86275 ай бұрын
sir big fan of yours,need to talk to you and i m from india and need your certification
@AxisAgileApps5 ай бұрын
Certainly! I think I received your message via our support contact form - did you receive my reply?
@sugarfaryprinces5 ай бұрын
Hi. Really like your videos. They are helping me very much. I have a question regarding the release process. How would you proceed if the team is organized in sprints that are 2 weeks long BUT they release every week? I am finding it hard to organize the release and at the moment there is only a release note available with all the tasks that ended up in the release.
@AxisAgileApps5 ай бұрын
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
@sugarfaryprinces5 ай бұрын
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?
@thygel.1225 ай бұрын
One of the few good explanations I've heard - thanks!
@AxisAgileApps5 ай бұрын
Thanks Thyge! Our pleasure :)
@adityasahu80526 ай бұрын
Very insightful content... Thank you. I am trying to download the sample data from the given link. Its not working. Please share some sample data for doing practice in jira.
@AxisAgileApps5 ай бұрын
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
@sumithvasav6 ай бұрын
Your are so well in explaining things in very short time, but with lots of information !!!! This is amazing... Thank you !!
@AxisAgileApps5 ай бұрын
Thanks Sumith!! Our pleasure :)
@sumithvasav6 ай бұрын
Great explanations !!! Thank you for your effort.. Please see if you can add the kanban board for DoR
@AxisAgileApps5 ай бұрын
Thanks Sumith. We'll have more videos coming soon :)
@sanushkabaskali89786 ай бұрын
How do you normally use Epics in Jira. this series of videos you used stories and sub tasks ...... how do you use epics?
@AxisAgileApps5 ай бұрын
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
@Heredia19736 ай бұрын
Hi Richard, thank you so much for your tips!!
@AxisAgileApps5 ай бұрын
Thanks Randall! it's our pleasure :)
@milos-lukic6 ай бұрын
Yes, do videos on all suggested topics please. Like your short and straight to the point tutorials :)
@AxisAgileApps6 ай бұрын
Thanks Milos! :)
@milos-lukic6 ай бұрын
It would be interesting to learn more on differences between team and company managed kanbans, so yes, please do a video on that topic :)
@AxisAgileApps6 ай бұрын
Thanks for the suggestion Milos! We've added it to our video backlog