AYDIN SATICIIT ARCHITECT / SENIOR PROGRAM MANAGER| DIGITTIONCary, Nc, United States
Enterprise application implementation projects implemented by implementer companies have mostly faced either failure or big delays because of doing change request on the scope. Both enterprise customer and implementer company lose money, prestige, customer, and time becasue of failure in this kind of projects. If there might be a way to park change request during implementation based on contract and then to do all CRs in first new release deployment, most of the projects avoids failure or delay. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The first answer is NO because it was demonstrated by Lehman´s Laws of software (beyond my personal experience). The second point to take into consideration is: I fully disagree about software implementation projects fail or are delayed. Those project always end in the estimated time. But it is not the time published including the time published has been agreed by both parts. Solution is simple (I have experienced it lot of times). project change management process must be showed into all walls into the company as a poster (exaggeration but is an illustration). All people that is part of the project must be aware, must understand, must agreed how much a change cost (not only in monetary terms) and must be understand that they have to decide about to do or not to do the change.
...
2 replies by AYDIN SATICI
Feb 05, 2018 5:42 PM
AYDIN SATICI
...
I tried to ask whether it is possible not to officially accept any change request proposed by implementer company. If you lose the base of contract (multi 10 million dolllars projects) between you and implementer company because of only one change request, you wouldn't have any chance to blame or to apply penalty to the implementer company for extra delays in the project deadline. Once, during a big transformation project, I faced an interesting change request that implementer company asked us, as their client, for accepting one development as a change request which had zero cost and zero time effect on the project. It's unbelievable. Why does implementer company offer us to accept a task with zero cost and zero time effect as an offical change request? I think, in emergency case, they would have to use it as an excuse of any delays in the project.
Is it possible - yes. Is it likely - no. The complexity involved with enterprise applications usually impacts the ability to use a wholly deterministic delivery approach which implies the need to embrace change.
Kiron
...
2 replies by AYDIN SATICI
Feb 05, 2018 8:33 PM
AYDIN SATICI
...
Thank you for your answer
Feb 05, 2018 8:36 PM
AYDIN SATICI
...
Thank you for your answer
Saving Changes...
Anish AbrahamPrivacy Program Manager| University of WashingtonAuburn, Wa, United States
I remember implementing an enterprise application without any change request over a decade ago but now it's a mandatory requirement.
As soon as you mention the word "enterprise" and "implementation" you increase the number of stakeholders exponentially. Given this, the chances of zero change requests are, well, zero!
...
1 reply by AYDIN SATICI
Feb 05, 2018 8:35 PM
AYDIN SATICI
...
Thank you or your answer
Saving Changes...
AYDIN SATICIIT ARCHITECT / SENIOR PROGRAM MANAGER| DIGITTIONCary, Nc, United States
Feb 05, 2018 1:20 PM
Replying to Sergio Luis Conte
...
The first answer is NO because it was demonstrated by Lehman´s Laws of software (beyond my personal experience). The second point to take into consideration is: I fully disagree about software implementation projects fail or are delayed. Those project always end in the estimated time. But it is not the time published including the time published has been agreed by both parts. Solution is simple (I have experienced it lot of times). project change management process must be showed into all walls into the company as a poster (exaggeration but is an illustration). All people that is part of the project must be aware, must understand, must agreed how much a change cost (not only in monetary terms) and must be understand that they have to decide about to do or not to do the change.
I tried to ask whether it is possible not to officially accept any change request proposed by implementer company. If you lose the base of contract (multi 10 million dolllars projects) between you and implementer company because of only one change request, you wouldn't have any chance to blame or to apply penalty to the implementer company for extra delays in the project deadline. Once, during a big transformation project, I faced an interesting change request that implementer company asked us, as their client, for accepting one development as a change request which had zero cost and zero time effect on the project. It's unbelievable. Why does implementer company offer us to accept a task with zero cost and zero time effect as an offical change request? I think, in emergency case, they would have to use it as an excuse of any delays in the project. Saving Changes...
Amany NuseibehSpeaker, Global Leader | Optimal ConsultingSydney, Nsw, Australia
Aydin, I guess you have your answers. Having said that, I think we need to treat change requests as a "natural part" of any project. Changes in strategies, legislations, compliance with standards, internal and external process ... etc changes could happen at any point in time within the lifetime of a project. The more complex the project is, the more stakeholders are involved, the more time it requires, the more likely this will happen, and the more likely it will have an impact on the overall project, be it cost or time, scope or quality and ultimately business outcomes, strategic alignment and benefits.
...
1 reply by AYDIN SATICI
Feb 05, 2018 8:34 PM
AYDIN SATICI
...
Thank you for your answer.
Saving Changes...
AYDIN SATICIIT ARCHITECT / SENIOR PROGRAM MANAGER| DIGITTIONCary, Nc, United States
Feb 05, 2018 1:37 PM
Replying to Kiron Bondale
...
Aydin -
Is it possible - yes. Is it likely - no. The complexity involved with enterprise applications usually impacts the ability to use a wholly deterministic delivery approach which implies the need to embrace change.
Kiron
Thank you for your answer Saving Changes...
AYDIN SATICIIT ARCHITECT / SENIOR PROGRAM MANAGER| DIGITTIONCary, Nc, United States
Feb 05, 2018 7:05 PM
Replying to Amany Nuseibeh
...
Aydin, I guess you have your answers. Having said that, I think we need to treat change requests as a "natural part" of any project. Changes in strategies, legislations, compliance with standards, internal and external process ... etc changes could happen at any point in time within the lifetime of a project. The more complex the project is, the more stakeholders are involved, the more time it requires, the more likely this will happen, and the more likely it will have an impact on the overall project, be it cost or time, scope or quality and ultimately business outcomes, strategic alignment and benefits.
Thank you for your answer. Saving Changes...
AYDIN SATICIIT ARCHITECT / SENIOR PROGRAM MANAGER| DIGITTIONCary, Nc, United States
Feb 05, 2018 1:20 PM
Replying to Sergio Luis Conte
...
The first answer is NO because it was demonstrated by Lehman´s Laws of software (beyond my personal experience). The second point to take into consideration is: I fully disagree about software implementation projects fail or are delayed. Those project always end in the estimated time. But it is not the time published including the time published has been agreed by both parts. Solution is simple (I have experienced it lot of times). project change management process must be showed into all walls into the company as a poster (exaggeration but is an illustration). All people that is part of the project must be aware, must understand, must agreed how much a change cost (not only in monetary terms) and must be understand that they have to decide about to do or not to do the change.
Thank you for your answer Saving Changes...
AYDIN SATICIIT ARCHITECT / SENIOR PROGRAM MANAGER| DIGITTIONCary, Nc, United States
Feb 05, 2018 4:33 PM
Replying to Sante Delle-Vergini, PhD
...
As soon as you mention the word "enterprise" and "implementation" you increase the number of stakeholders exponentially. Given this, the chances of zero change requests are, well, zero!
"Put your hand on a hot stove for a minute, and it seems like an hour. Sit with a pretty girl for an hour, and it seems like a minute. THAT's relativity."
