Lean Software Development

Correct Answer: Secure the slot, identify another interim learning solution to mitigate current issues, and evaluate for future training needs.

The best course of action as per the amplifying learning principle of Lean Software Development is to 'Secure the slot, identify another interim learning solution to mitigate current issues, and evaluate for future training needs'. This is because as per the Lean Software Development methodology, it's essential to keep learning and adapting to change to ensure products are delivered with great efficiency. By securing the slot, we ensure that the team will get the necessary training eventually. Meanwhile, by identifying an interim learning solution for current issues, we ensure that knowledge gaps are filled and our processes don't suffer due to a lack of knowledge. Let's explain why the other options are not optimal: 'Wait until the training slot becomes available and try to work with current knowledge': This approach delays necessary learning that could improve the team's performance sooner rather than later and doesn't align with the principle of 'Amplify Learning'. 'Skip the training and delegate the complex tasks to the most experienced team members': This approach does not help in team development or knowledge sharing and would increase the pressure on experienced team members. 'Decide that no training is needed as the team should learn by doing': While learning by doing is valuable, it's not the most effective way to close knowledge gaps rapidly. On-the-job learning should be combined with structured learning processes.

Correct Answer: Just enough features that early adopters could use and provide feedback.

The goal of an MVP, or Minimum Viable Product, in the context of Lean Software Development, is to create a product with a minimum number of features that fulfills the primary goal of the software. It's meant to be a usable, releasable product that early adopters can use, gain value from, and provide feedback on. This feedback helps the team to understand their users, and make any necessary adjustments and enhancements to the product. The answer suggesting 'All planned features, but in their most basic form' isn't fully correct as this could lead to an overloaded product with unnecessary features. The idea of an MVP is not to provide all planned features, but to focus on the core features that deliver the product's value proposition. As for 'Every feature, but only accessible to the team', this defies the purpose of an MVP as it has to be released to early adopters for feedback collection. The 'All planned features slightly downgraded' is incorrect as well because like the other incorrect options, it involves implementing all planned features instead of focusing on the most vital ones.

Correct Answer: Immediately clarify the requirements with all stakeholders to ensure accuracy and avoid wasted effort.

In Lean Software Development, eliminating waste is one of the core principles. Ambiguity in requirements is recognized as a waste because it often leads to building the wrong features or products. The ultimate course of action should be to immediately clarify the requirements with all stakeholders to ensure accuracy and avoid wasted effort. This makes sure that what is being built is truly what the customer and stakeholders want, which saves time and resources. Making assumptions, proceeding without clarification, or delegating the task of requirement clarification, could lead to working on the wrong things, leading to waste of time and effort, which is against the principles of Lean Software Development.