I would expect that this would be part of the Executing process group and would fall under "Direct and Manage Project Work" process as a go live would happen once all deliverables required for the change implementation had been accepted (via Validate Scope) by stakeholders.
You won't find a concrete answer because it's a, "That Depends" question.
The PMI process groups are not sequential so that at some point in time, you are no longer planning and now only executing.
Going live (or similar terms) refer to a major project milestone in the development of a product. The Product is expected to have a longer lifetime, but the Project team may hand off the product or they may be responsible for improvements for a period of time.
At that milestone, you are closing some things like development, monitoring and controlling other activities like system performance, and initiating new change orders based on the monitor and control process. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
No question is dumb, at least for me, because I spend my time here learning from questions and the answers. While it could depends on the life cycle in my actual work place Go Live (we call it Go Live and Support where support is a period of hypercare after putting the solution in production) is inside Executing and Controlling Group. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
I see GoLive as a phase in a sequential project life cycle. Other than Sergio’s example, I see hypercare as a separate phase with different types of value, resources and metrics.
In an iterative life cycle GoLives ( providing end users with the product) are typically done with every release or even iteration.
A GoLive phase can include activities from all 5 process groups. You can /should initiate it, plan it, execute it, monitor and control it and close it.
"Go live" is something that could (should?) involve activities from all process groups. It's worth remembering that for software projects for example, going live may happen as early and as frequently as possible (e.g. weekly), and may be a continuous process rather than any kind of milestone. Saving Changes...
Luis NavarroUpstream and Downstream Project Manager| Petroleos de Venezuela (PDVSA)Venezuela (Bolivarian Republic of)
Good clarifications that "go live" should involve activities from all process, and I like the strong conclusion by Thomas, "no lifecycle phase is part of a process group", period.
A few years ago this used to cause a lot of confusion on people trying to map lifecycle phases with process groups, probably because the PMBoK guide didn't strongly clarified this. Now I like it very much when the guide says "the end of the project or phase", "the plan of the project or phase", and so on. It makes it obvious that it is applying all the processes to all the phases. Saving Changes...
Bill DowPMO Director| University of WARenton, Wa, United States
Good call on depends, but I agree it would be in the Executing process if you were going to find it in any. Not a dumb question, interesting one really. :) Saving Changes...
Phil AkinwaleProject Management & Leadership Speaker, Coach, Trainer & Author| PRAIZIONMesa, Az, United States
Thomas is right. Project Management Life Cycles (process groups)
are not equal to Project Life Cycles (phases). They should not be mapped. You could apply each of the 5 process groups to a go-live (a phase in a project). Saving Changes...
