Lean Software Development

Correct Answer: Seek clarification from the client to avoid wastage of resources and potential need for rework.

In the context of Agile methodologies and lean software development teams, communication and collaboration with the client are key principles. When faced with an ambiguous requirement, your first course of action should be to 'Seek clarification from the client to avoid wastage of resources and potential need for rework'. This answer is in keeping with the Agile principle of 'customer collaboration over contract negotiation'. The other options do not reflect Agile principles. Ignoring the ambiguity and proceeding with your own interpretation can lead to wasted work when the client's real needs are finally uncovered. Delaying addressing the requirement until the end of the project contradicts the Agile value of responding to change over following a plan. Lastly, assigning a new team to interpret the requirement is likely to disrupt team dynamic and introduce unnecessary complexities, contrary to lean principles of minimizing waste and maximizing learning.

Correct Answer: Encourage team empowerment by delegating decision-making authority to team members, fostering a sense of ownership and responsibility.

According to Lean Software Development principles, empowering the team and decentralizing decision-making help eliminate waste and improve efficiency. By delegating decision-making authority to team members, they become more engaged and responsible, reducing delays caused by waiting for approvals. Implementing stricter control, scheduling additional meetings, or assigning decision-making to a single individual centralizes control and can increase delays, which contradicts Lean principles of eliminating waste and promoting team empowerment.

Correct Answer: Eliminate the feature from the project by communicating with the stakeholders.

In the context of Lean Software Development, the foremost principle is to eliminate waste. If a feature is determined not to add as much value as initially thought, the immediate course of action should be to communicate with the stakeholders to eliminate this feature from the project. It's unwise to proceed with the implementation of a low-value feature (hence, this answer is incorrect), as it goes against the principles of Lean Software Development by adding potentially wasteful work. Waiting until the project ends to revise the feature (another incorrect answer) also results in wasted effort, which could have been avoided. Lastly, implementing the feature but prioritizing it lower than the others (also incorrect) would still justify working on a low-value feature, which contradicts the lean method's focus on value-additive tasks only.