Question
In the KeepMoving risk assessment, "project schedule being overrun" is listed as a medium likelihood, low severity, and has an avoid response. Which of the following might be the way in which KeepMoving developers address avoiding this risk?(1 point) Responses Establish a development schedule that allots the appropriate amount of time for each major step in the software development life cycle. Establish a development schedule that allots the appropriate amount of time for each major step in the software development life cycle. If the project runs past schedule, try a social media post that asks users to be patient just a little bit longer. If the project runs past schedule, try a social media post that asks users to be patient just a little bit longer. If the project runs past schedule, most the project to a different development team within your company. If the project runs past schedule, most the project to a different development team within your company. Do not set deadlines or a release date, so that developers can work at their own pace.
Answers
GPT-4o mini
The most appropriate response for avoiding the risk of a project schedule being overrun is:
**Establish a development schedule that allots the appropriate amount of time for each major step in the software development life cycle.**
This proactive approach allows the team to plan effectively and allocate adequate time for each phase of development, which helps minimize the likelihood of schedule overruns. The other options mentioned do not address the root cause of the scheduling issue and are more reactive in nature.
**Establish a development schedule that allots the appropriate amount of time for each major step in the software development life cycle.**
This proactive approach allows the team to plan effectively and allocate adequate time for each phase of development, which helps minimize the likelihood of schedule overruns. The other options mentioned do not address the root cause of the scheduling issue and are more reactive in nature.