Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Change Management
Organizational Impact Assessments does anyone still use them?
Anonymous
With Agile being the dominant methodology these days. Curious to know if traditional Organizational Impact Assessments/Analysis are being created in an agile framework, if so what's your method?
Sort By:
Network:929



There is no such thing in any Agile framework. (sarcasm).
First of all there is no evidence that Agile is the 'dominat' project delivery approach these days. Second there is no such thing as Agile methodology. There are a collection of frameworks and practices, with over 70% of the Agile practitioners using or claiming that are using Scrum. There is no mention of impact assessment in Scrum, some activities related to the product backlog items it is (or it should be) done during the Release/Sprint Planning.
That's nit what the Organisational Change Management or ITIL Change Management is about. That kind of Impact assessment will be stil done by the Change Manager or the CAB.
There is nothing preventing Agile practices to be augmented by traditional practices, especially in areas that are far more mature in the planned approach, like Stakeholders Management, Risk Management, Financial Management, Procurement and the list can continue to all 10 knowledge areas.
Impact assessment (either of them) it's part of a science developed over many (~100) years, it can't be addressed in a 17 pages guide.
Agile doesn't mean discarding the existing knowledge but building on it.
Network:1350



Change management is needed regardless of the delivery approach for a change. The question is how detailed change strategy, planning & execution needs to be. If you are dealing with frequent, small changes as encouraged by adaptive lifecycles, then the magnitude of each change might not be great but there's still the need to prepare stakeholders to receive the change and to implement measures to ensure sustainability of the change.
...
1 reply by Stelian ROMAN
Apr 16, 2019 5:55 AM
Stelian ROMAN
...
In principle that's correct but if the environment is software development, where Agile is probably the norm, there is no OCM component. the Impact Assessment and everything else that comes with it will be very likely done at the client side as part of the implementation plan.
Network:325



I am currently running a big SAP implementation project using Nexus as scaled agile framework. In parallel we have to run OCM due to many processes changes with organizational impact. Organizational impact analysis is needed in any business analysis related work, regardless whether the project framework is agile, hybrid or traditional waterfall-driven.
...
1 reply by Stelian ROMAN
Apr 16, 2019 5:53 AM
Stelian ROMAN
...
Peter, interesting topic. I managed a Dynamics roll-out that on paper was using Scrum. I am really curious if you deliver increments of SAP to the end users after every sprint and if there are scope changes based on user feedback.
I am also extremely interested, based on my experiences with large and complex systems, if you don't have SIT, UAT, Regression, Staging phases before release to prod.
How long takes from the time a new feature that require customisation (code) is requested by users until it is released to production. I will be also very surprised if in a SAP implementation you don't have signed off BRD, SIT Plan, UAT Plan etc.
Can you please share the roles that are coming to the Nexus and how many Scrum teams are involved?
Network:929



Apr 13, 2019 4:54 PM
Replying to Peter Ambrosy
...
I am currently running a big SAP implementation project using Nexus as scaled agile framework. In parallel we have to run OCM due to many processes changes with organizational impact. Organizational impact analysis is needed in any business analysis related work, regardless whether the project framework is agile, hybrid or traditional waterfall-driven.
Peter, interesting topic. I managed a Dynamics roll-out that on paper was using Scrum. I am really curious if you deliver increments of SAP to the end users after every sprint and if there are scope changes based on user feedback.
I am also extremely interested, based on my experiences with large and complex systems, if you don't have SIT, UAT, Regression, Staging phases before release to prod.
How long takes from the time a new feature that require customisation (code) is requested by users until it is released to production. I will be also very surprised if in a SAP implementation you don't have signed off BRD, SIT Plan, UAT Plan etc.
Can you please share the roles that are coming to the Nexus and how many Scrum teams are involved?
Network:929



Apr 11, 2019 7:07 PM
Replying to Kiron Bondale
...
Change management is needed regardless of the delivery approach for a change. The question is how detailed change strategy, planning & execution needs to be. If you are dealing with frequent, small changes as encouraged by adaptive lifecycles, then the magnitude of each change might not be great but there's still the need to prepare stakeholders to receive the change and to implement measures to ensure sustainability of the change.
In principle that's correct but if the environment is software development, where Agile is probably the norm, there is no OCM component. the Impact Assessment and everything else that comes with it will be very likely done at the client side as part of the implementation plan.

Please login or join to reply

Content ID:
ADVERTISEMENTS
ADVERTISEMENT

Sponsors