Program SenseProgram Management

How would you handle new requirements in the middle of a project you're managing at Google?

Technical Program Manager

Google

Did you come across this question in an interview?

Answers

Anonymous

7 months ago
4Strong
1) Understand the requirements and assess the impact and risk to the program.
2) Get the team together to determine the risks vs rewards and timeline issues. 
3) If additional resources are required escalate to the executive and discuss the dependencies and impact to the program. Convince the exec through data from brainstorming sessions with the team if the feature is essential for program delivery

Anonymous

10 months ago
4.4Exceptional
As a TPM with experience in Agile methodologies, I value changing and adapting to new changes that contribute to the overall goal. To deal with this situation, I would first assess the impact that this change would cause on the goal of the project. I would achieve this by checking if the changes align with the project mission, if the stakeholders satisfaction is affected by the same, if the value derived from the new requirements are worth extending deadlines or adding resources. After the assessment, I would document the new requirements, new timelines, new resource requirements and communicate the same with stakeholders. If the additional requirements would have a negative impact on the project, I would politely decline and notify the stakeholders of the same, while communicating alternatives like accommodating the requirements in another project lifecycle.
  • How would you handle new requirements in the middle of a project you manage at Google?
  • In the middle of a project you are managing at Google, what would you do about new requirements?
  • How would you manage new requirements in the middle of a project at Google?
  • How would you respond to new requirements in the middle of a project you're working on at Google?
  • How would you handle new project requirements in the middle of the work you're doing at Google?
  • What would you do if you encountered new requirements in the middle of a project you are managing at Google?
  • At Google, how would you handle new requirements in the middle of a project you're handling?
  • How would you handle the situation if there were new requirements in the middle of a project you are managing at Google?
  • How would you handle new requirements in the middle of a project you're managing at Google?
  • As a project manager at Google, how would you handle new requirements that arise in the middle of a project?
  • How you would handle unexpected requirements that might emerge during a project during a project you're managing at Google?
  • In your capacity as a program manager at {compay}, what steps would you take to address newly introduced requirements in the midst of a project?
  • How might you, as the program manager, navigate the introduction of new requirements during an ongoing project at Google?
  • In the event of new requirements surfacing in the middle of a program you are managing at Google, how would you involve the project team and stakeholders to adapt to these changes?

Interview question asked to Technical Program Managers interviewing at Google: How would you handle new requirements in the middle of a project you're managing at Google?.