So when you create a spike, you are creating an story without an estimation (no story points) to a Sprint, and allocating a time to it. That time will possibly take away from the ability to complete the same number of story points won't it? If that is the case, do you maintain a consistently lower target number of points to accommodate unplanned spikes?
Hi!RU-vid recommended your video! love your content and your energy. By the way, are you currently interested in expanding your channel's reach and gaining more views? Let me know if you're interested?
Hello dear thanks for the video. I need small help in understanding about how we can categorise production support epic with ongoing development epics. Do we need to take all in one sprint or we have separate sprints. Thanks in advance.
As i understood it's a problem that we will have failed sprints often because of spikes. In the end of sprint we should deliver workable product. What's timebox for spike? Some scientists can do for a month, for example
thank you for your video, but do you know if it is possible to generate a full export file directly integrated workflows, users, permissions et data of course. If it not exists, how works the migration to the Clould Altalssian. I hope your anwser
Hi Anca, what methodology would you recommend for a data science team where team member works for different analysis which do not form a unitar product in the end and each analysis has a different stakeholder? I was thinking to try scrumban in 3 weeks sprints because based on team feedback 2 w were to tight comparing with the tooling and complexity of the tasks. Thanks a lot. Mike
Poorly edited video, why would the video be released rather than corrected? Clearly the issue was identified over a year ago. There are better, more effective,and well put together resources available on RU-vid. Poor Show Agile Scrum Chanel- Unsubscribed.
Hi,many thanks for valuable video series. Your explanation is very lean and understandable. I want to implement scrumban methods for supply chain and purchasing processes. But I don’t sure management with compatibility. If you have a best practice example,I would have success by your sharing. Best Regards
Thank you for the greatVideo ! One question ... what about the attachments inside of the Jira Issues ? Is there also a way to migrate data without a plugin ?
Unfortunately those you lose them. Ideally you can go in ticket and save them to a google drive for example and then add a link to then which will be carried over.
hi Orli, what about technical user stories whereby the persona is a system consumes APIs - have subsystem team design and deliver APIs for consumers(internal/external). It is not a usual ui and customer facing PO role but a technical one to translate the functionality coming from an architect
yes , in Scrumban we don't commit to certain scope , but we commit to some KPI's or Service Level Expectations , WIP's , Lead time etc. otherwise it is too free and loose process , like: customers order something and we say to them we ll see when we deliver it to you. that would nt be delivering value. Another thing that I miss is paying attention to complexity as a factor in choosing the right framework. Kanban is more suitable for developing simpel products , and Scrum or Scrumban is more suitable for complex products.
I think your approach goes against the guide described by the founders of agile. Quick fixes can be done but I'd it is not a priority, it is better to create the bug, link to the main story but estimate to understand the root cause . It works for capacity planning and yes, velocity is not a good team matric but it only comes after capacity has been planned. It is also better to have a placeholder estimate for bugs. Creating a whole new story makes you loose track of how many hugs are generated within a given time frame and so makes it hard to track how much time is actually spent fixing bugs than working on new requirements.
Sometimes this will enable things, i.e. QA to test - or whatever needs to happen, in either case what you did yesterday might be 'done' for you but not 'done' as a status, I did it, and now it's ready for the next thing to happen. Example "Yesterday I completed the code review for X task" this means something for someone else in the team.
That is not true. Scrumban is a way to work on its own. You may use Scrumban till eternity without going 100% over to Kanban (or Scrum). But it can be used as a transition, but that is just an option.
Thanks for the video :) we are implementing Scrumban un our team and I'm trying to figure out how to make KPIs work with story points. Do you recommend using story points in Scrumban? Or rather time estimations?
Hi, Thanks for video but your method to import Sub-task is wrong and does not work in the way you have. Normally importing sub task using excel never works when I look at different tutorials in Jira community. So please either remove that piece from your video or provide steps in details which you have skipped from the mappings till end.
You know what I think I found an easiest way to do it. Import all the issue types including Sub-Types as well, go to the new site where you have imported the data and using Bulk Change option from Advance Search - select sub task - select the action Move issues - select the Parent Issue - click Next That’s it and it is done but the down side it works for less number of task and if you have more then it may not be helpful 🙂
Hello, Thank you for your explanations. I have a trouble about "Map fields" 1. If I need to match all fields, some of them, I could not find it. For example : Watchers ID? I'm clicking on this field and no match as same as Watchers ID Also on my excel file is written watchers ID, How can I match them. 2. I tried to match them just like fun. (just wanted to move next step) but I can't go on next step! I stucked at 12:45 exporting Epics 3. Do I need to convert, what do I downloaded (Csv file)? 4. Also do I need to create new project and build issue types, workflows etc? Before migration?