Program SenseProgram Management
Can you describe your method for ending a project?
Answers
Anonymous
7 months ago
Winding down a project requires several tasks from ensuring all the tasks associated with a program are in a final state. Those final states can be completed, abandoned for tasks that are not required anymore or moved to a future program.
Ensure the services and tooling outcomes of the program are transitioned to the final users who will maintain and operate them in the long term defining a clear ownership.
After all the tasks are in a finalized step the next step is communications. The communication channels can include email and presentation in all hands. The communication includes a summary of the program, some top level metrics showing the impact as compared to the baseline, and a list of people with their contributions to the program.
Managing a retrospective to collect information about what went well, what could be improved and the lessons learned that can be useful for future programs.
The final step is to archive all the documents and resources associated with the program.
There are a few challenges associated with winding down projects. For example during the Google Home Infrastructure program there were hundreds of thousands of legacy code that was kept for half a year after the project completion and was tracked separately. Because the program touched multiple areas and technical and not technical stakeholders there was a need to create multiple versions of the program completion announcement with different levels of detail. For the retrospective I collected information from risk management, tasks that were deprecated, things that could have been done differently and tasks that were moved to future programs.
Anonymous
5 months ago
Once the project is live in production. As a program manager, would ensure if the the delivered features are enabled for the eligible customers and ensure we monitor the usage metrics and error logs. From a execution perspective, I will collect the planned vs actual timelines information from the gantt chart and conduct a retrospective meeting with the team. Will document all the learning and share them with the stakeholders including BU leaders. With a thank you note, Will share appreciation for the whole team and highlight the exceptional work done by individuals by highlighting the impact.
Anonymous
6 months ago
After launching the last piece of our project, I would make sure that stakeholders would be informed of its completion, most likely in the form of a newsletter and an email. I would make sure that we would review any remaining tasks and either reprioritize or delete them if they're not necessary. I would make sure to check with product teams that we handle technical hygiene and that our environments are stable. I would make sure to meet with key stakeholders and a hold a retro to learn about what worked well, what could be improved. These learnings would become action items that we would use for our next project. And of course, we would celebrate!
Try Our AI Interviewer
Prepare for success with realistic, role-specific interview simulations.
Try AI Interview NowInterview question asked to candidates interviewing at top companies: Can you describe your method for ending a project?.