@@wowbykempe Good to know that, it is just something that I was going to suggest a video about change management, a serious suggestion that then the video is about request management, I'm just in my company looking for ways to adapt it to the agile world
I think the video is missing the point set out in the title. You state itil means working in a structurized manner while agile is working quickly. Both methodologies have these aspects within them. Showing how customer service works does not explain the difference between them.
Actually we're not stating that. But a lot of people do and our take with this one was to show that you don't have to choose between ITIL or agile, but benefit from the best of both worlds in something that could make sense to you (if you're Nea at least...)
Then what's the difference between QMS and ITIL? Because QMS also has work instructions and guidelines to help all people from the V model to improve their work and to delived in the end , the best products to our clients, in order to meet or exceed theirs expectations...How collaborates together ITIL and QMS? Is ITIL the same as concept in a factory and in a software company?
It depends. Some incidents (SEV1/Urgent/Major) will surely need to be managed outside of the traditional backlog scope (or rather by shortcircuiting the existing backlog). But you can still use the same process: the only difference is really that you sometimes need to kick something ahead of everything else. But yes, for some companies, the described balance between agility and control is surely not correct. A large part of the expertise we at Olingo bring to the table is to find the correct balance for each customer.
Very nice approach :)
Thank you. Glad you enjoyed it.
Hello, very good video, I would like to know if you have any additional video about AGILE VS ITIL? thanks and greetings from Peru
Not yet, but we have thought about doing one about Change mgt in an agile world. Do you have any suggestions?
@@wowbykempe Good to know that, it is just something that I was going to suggest a video about change management, a serious suggestion that then the video is about request management, I'm just in my company looking for ways to adapt it to the agile world
@@angevolo6475 Contact me via www.wowbykempe.com and I'll point you towards some ways on how to handle the change requests for the agile teams.
I think the video is missing the point set out in the title. You state itil means working in a structurized manner while agile is working quickly. Both methodologies have these aspects within them. Showing how customer service works does not explain the difference between them.
Actually we're not stating that. But a lot of people do and our take with this one was to show that you don't have to choose between ITIL or agile, but benefit from the best of both worlds in something that could make sense to you (if you're Nea at least...)
Then what's the difference between QMS and ITIL? Because QMS also has work instructions and guidelines to help all people from the V model to improve their work and to delived in the end , the best products to our clients, in order to meet or exceed theirs expectations...How collaborates together ITIL and QMS? Is ITIL the same as concept in a factory and in a software company?
Please give your opinion. But from my point of view backlog cannot be planned weekly, or even daily since they bear SLAs.
It depends. Some incidents (SEV1/Urgent/Major) will surely need to be managed outside of the traditional backlog scope (or rather by shortcircuiting the existing backlog). But you can still use the same process: the only difference is really that you sometimes need to kick something ahead of everything else.
But yes, for some companies, the described balance between agility and control is surely not correct. A large part of the expertise we at Olingo bring to the table is to find the correct balance for each customer.
umm...sound??
Hello Mike, I have sound as well as my friends and colleagues. Is yours silent?