Iterative Development

Correct Answer: Implementing small batch sizes and limiting work in progress

In iterative development, implementing small batch sizes and limiting work in progress is the most effective practice for enhancing value delivery when facing recurring impediments. This approach works because: - It reduces complexity and makes problems more manageable - Enables faster feedback loops - Makes it easier to identify and resolve bottlenecks - Improves flow efficiency and reduces waste - Allows for quicker adaptation and problem resolution The other options are incorrect because: - Increasing tasks and expanding scope actually creates more complexity and compounds existing problems - Extending iteration duration goes against agile principles and delays value delivery - Adding more resources and expanding capacity often leads to increased coordination overhead and doesn't address the root causes of impediments The key is to simplify and optimize flow rather than add complexity or delay solutions. Small batch sizes and WIP limits help teams maintain a steady, manageable flow of work while effectively addressing impediments.

Correct Answer: Conduct a feature prioritization workshop with all stakeholder groups to create a unified priority list based on business value.

The best solution is to conduct a feature prioritization workshop with all stakeholder groups to create a unified priority list based on business value. This approach is optimal because: 1. It brings all stakeholders together in a collaborative environment 2. It focuses on business value as the key decision criterion 3. It promotes transparency and shared understanding 4. It allows for direct communication and negotiation between groups 5. It results in a single, unified priority list that all parties have contributed to Why other approaches are less effective: - Implementing features based on organizational authority undermines the collaborative nature of iterative development and may miss crucial business value opportunities - Dividing capacity equally among groups is artificial and fails to consider actual business value or urgency of features - Having separate meetings and letting the project manager decide creates potential bias, lacks transparency, and misses the opportunity for stakeholders to understand each other's perspectives The workshop approach aligns with business analysis best practices by facilitating stakeholder collaboration, ensuring transparency, and focusing on maximizing business value.

Correct Answer: Regular code refactoring during each iteration cycle

Regular code refactoring during each iteration cycle is the best practice to minimize technical debt in iterative development. Refactoring code regularly during iterations helps maintain code quality, improves system architecture, and prevents the accumulation of technical issues. This proactive approach allows teams to address potential problems early, making them easier and less costly to fix. The other options are less effective because: Extensive documentation of improvements for future iterations creates a backlog of issues that may grow larger and more complex over time. Addressing technical improvements after multiple iterations allows problems to compound, making them more difficult and expensive to resolve. Maintaining a separate backlog for technical improvements and addressing them in alternate sprints can lead to delayed fixes and increased complexity when issues are finally addressed.