Fallback Planning

Correct Answer: Define fallback plans for key features to enable rapid response when planned risk responses fail

In agile projects, the best approach for implementing fallback plans is to focus on key features with specific risk responses. This approach aligns with agile principles of adaptability and efficiency. The correct answer emphasizes defining fallback plans specifically for key features, which allows for: - Focused risk management - Efficient resource allocation - Quick adaptation when needed - Balanced risk coverage Why other options are less optimal: Creating detailed plans for all user stories is excessive and contradicts agile's lightweight approach, consuming too many resources and potentially slowing down the project. Limiting fallback plans to only critical path activities is too restrictive, as non-critical path features may still carry significant risks that need mitigation. Developing fallback plans exclusively during sprint planning is too rigid and doesn't allow for dynamic risk response as new risks emerge throughout the project lifecycle.

Correct Answer: To provide predefined actions when a risk response fails to work

A fallback plan serves as a backup strategy that is implemented when the primary risk response proves ineffective. Its main purpose is to provide a predetermined set of actions that can be executed if the initial risk response strategy fails to achieve the desired results. The correct answer states this accurately - the fallback plan provides predefined actions when a risk response fails to work. This is precisely what fallback plans are designed for in project risk management. The other options are incorrect because: - Creating alternative options before implementing risk responses is part of the initial risk response planning, not a fallback plan's purpose - Establishing secondary risk thresholds relates to risk monitoring and control, not fallback planning - Documenting all potential risk responses is part of the risk response planning process, which occurs earlier in the risk management process Fallback plans are specifically designed as contingency measures that activate when primary risk responses prove inadequate, making them an essential part of comprehensive risk management strategy.

Correct Answer: During initial risk response planning when primary strategies are developed

The best time to develop fallback plans is during the initial risk response planning phase when primary strategies are being developed. Here's why: 1. Proactive Planning: Creating fallback plans alongside primary strategies ensures comprehensive risk coverage from the start 2. Resource Efficiency: Planning both primary and backup strategies together allows for better resource allocation and coordination 3. Time Management: Having fallback plans ready before issues arise prevents rushed decision-making during crises 4. Cost Effectiveness: Early planning allows for proper budgeting and cost consideration of both primary and backup options The other options are incorrect because: - Waiting until a primary response fails is reactive and could lead to project delays - Developing fallback plans during periodic reassessments is too late and reactive - Creating fallback plans before choosing response strategies would be premature as the primary strategies aren't yet defined