วีดีโอ

@anubis32377, thanks for dropping by! Regarding your question, bugs can be found during any moment in the project. They represent effort that was not foreseen and that will take time from your team. So, depending on how you want to plan that extra-work, it may make sense to have those bugs in your backlog to be estimated and planned for future implementation. This happens, for instance, when you find a regression bug. You may decide that you don't want to interrupt the team now (context switching also costs time and money). On the other hand, when you find errors in stuff that the team is currently developing, we do not consider them as bugs but instead, they are part of the development process. Because of that, they represent some additional work under a specific story and not a bug in the backlog. I mean, it wouldn't make much sense to create a bug in the backlog related to a story that haven't yet met the Definition of Done (not completed).

Thanks Loredana for taking the time to view! Regarding your question, that is an option that you can implement in JIRA indeed. However, for flexibility reasons, we decided not to do such. But I guess that will be more of a personal preference for the teams.

@@palhinhas thank you for your answer!

You're welcome!

First of all, thanks for watching and for taking the time to comment :) That's a great question. I think you need to have the patience to do what you need to do :). But I can tell you that this is actually quite straightforward, as soon as you have these tools built. The concepts behind them are in the first video, where I explain their purpose: th-cam.com/video/r_Gn76njEXY/w-d-xo.html Now, be aware that a lot of these links are actually managed by a Project Manager (this is based on PM²) or a facilitator an not by the team itself. Depending on the level of formality of the initiative you are part of, maybe some of these are not needed. In that case, I guess I don't need to tell "don't use them" :)

@@palhinhas Thank you for the reply. Very interesting approach.

Glad it was helpful!

Glad it was helpful! Thanks for dropping by!

Many thanks!

Obrigado!

Yes you can! However, be careful, as you are introducing several different workflows, which will likely make your board much harder to read.

Thanks a lot for taking the time to watch and comment! Really appreciated!

@@DOITAGILE we know how these algos work and i'd def be happy if they gave you a reason to make more videos. I've been going through your others too. super helpful. some context - i'm helping a new team set up some of their workflows, for development, design, and some other things. I've used jira a little in the past, but never as the guy setting it up and am not familiar with good defaults, tips, etc, or where to even look. and of course it's all very time sensitive. in any case, see ya around. subscribed and hit the little bell

@coachsondberg, thanks a lot for taking the time to see and comment. What you suggest can indeed be a possible option. However, having a cancelled item classified with DONE will mean that JIRA will consider it DONE and will credit the estimated points as velocity. This happens because the DONE status is in the last column of a scrum board and it's how JIRA finds which items are actually done. Crediting a team points for a Cancelled item is definitely something that we don't want :) The Cancelled status allows me to leave all those items outside the board, since they don't bring any additional value in that board.

@@palhinhas yeah ok, you could still go deep dive under the hood and set it up, but if we are talking out of the box functionality, youre ofc right!

@Etan Pfeiffer, thanks a lot for dropping by! When a Bug needs to be solved immediately within an iteration, it represents work that was never planned and it was never seen in the backlog. Additionally, it will take time from your iteration that was not foreseen (this is what I call an unplanned event). By not giving any point, you will implicitly reduce the team's velocity due to unplanned events. On the contrary, if you give points to a bug in this situation, you are considering that you are doing work as usual and you will maintain the team's velocity, stating that everything is business as usual. On top of that, teams tend to augment their estimates when they solve these type of issues to have the idea that they are progressing well, while in fact they are playing it against themselves :) I hope I was able to explain!

1. Work that moves from one sprint to the other never generates new work items. It either goes already to the next sprint (because I want to continue to work on it) or it goes to the backlog, to be planned for a future sprint (not the next one). The field Sprint will always show you the current sprint + previous sprints where the item has been assigned to. 2. Some statuses can only be assigned to by the person who reported the issue or the person who is working on it. 3. Usually, I prefer to have one step at a time as it will make less likely to make mistakes (practical experience) and makes the workflow much clearer (in my opinion). But, like I mentioned in the video, you can (and should) make sure you adapt them to your agile reality. This means that you only need to configure additional links between the statuses you would like to "travel" in between.

Wow, thank you! JIRA videos are a very specific topic, so it's a bit hard to make them viral. I'm more than happy to know that they are helpful! Still, feel free to share them to those who you believe may benefit from them! Cheers!

Because it has 41 like at this point

Thanks a lot for your comment and support. I will keep adding them!

I found JIRA, with the standard features, very limited in terms of providing this type of JQL. This is why I made use of ScriptRunner. But if you find a way, please let me know, as I would be definitely interested.

Thanks for your feedback Sophia! I'm glad it helped! Feel free to check the other videos and subscribe the channel.

Thanks a lot for your support! Feel free to share with anyone you believe may also find it helpful :)

Thank you! Cheers!

Thanks a lot Aaron. Really happy that it was useful! I'll keep delivering them :)

@Brayden Marshall yea, I've been watching on instaflixxer for years myself :)

Thanks a lot! Glad you liked it.

Thanks for watching!

You are welcome! Glad you enjoyed it!

Thanks for your feedback! I'm not sure what you mean is still far away from what was presented in the sketch, since the demo in JIRA is a reflex of the concept. I just hope you didn't mention that as a plot to promote your product and your company, since apparently, you are the co-founder of teamhood...:) Please note that I have no vested interest in Atlassian...:)

Since you called it a perfect agile board, and showed how swimlanes can be used with sketch, I feel a need to not agree. I assumed you did it that way because Jira has kanban structure limitations, this is why epics and subtasks got the same columns mapped, where in reality more often this is not OK. IMO traditional approach is to have epics or stories on the left as swimlane headers and then all relevant tasks are visually mapped only to the swimlane where their parent lives. Finally, I will advocate own tool, but there are two reasons - believing in the true Kanban aporoach and second one of course being subjective to own solution (actually should have disclosed in the first place, my mistake, sorry)

@@vvasiliauskas it's more than fine to disagree! This is, for me a perfect board. However, I would have to be very arrogant to say it's the only way...:). I have no problems with people promoting their tools. I just want to make sure that when they provide inputs, they are not biased by their natural preference. Now, there may be a slight confusion, because you mentioned that you see Epics and subtasks. Well, there are no Epics in the kanban board (active sprint section) that I present (neither in the concept nor in the implementation). Maybe I was not 100% clear? Can you please point where in the video you got that idea? Maybe I need to review! Thanks!

Many thanks for your kind words! That's exactly the kind of support that makes me produce these contents! Cheers!

Many thanks André!

Hi Matt! Many thanks for your comments! I actually encourage the use the Sprint goals as drivers for the PI goals during the PI Planing...:) It helps understanding the concept of PI. Now, the reason for having PI Objectives as such is because we not only want to keep track of the items that contribute to those PI Objectives (can belong to several different iterations and different types of items), but we also want to keep track of the Planned business value as also the business value achieved by the end of the PI. As such this was the viable solution I found. Regarding JIRA Portfolio, I have to admit that I analysed it 2,5 years ago and it wasn't enough. This is why we selected another solution. As such, my experience with JIRA Portfolio is not up to date and I can't say how easy/hard it easy. I built my solution based on Bigpicture.

@@DOITAGILE Makes sense. I find that as long as the teams plan the epics (including the planned value) and releases well that holding so much additional detail on what is essentially the sprint goal, is overhead. (I understand your implementation, just one of my problems with SAFE), but ya Portfolio has come a long way. definitely worth a second look. They essentially redid it last year after they rolled out the new Jira UI.

Thanks Matt! I'll definitely take a look!

Thanks a lot for your support! Really appreciated!