Back to Lean Software Development

Deciding as Late as Possible

5 minutes 5 Questions

This concept deals with the decision-making process in software development. It is centered around maintaining flexibility by delaying decisions until they can be made based on facts, not assumptions. This means waiting until the last responsible moment to make decisions, in order to reduce the risk of waste due to wrong assumptions and reduce the need for changes in the future.

Guide: Deciding as Late as Possible in Lean Software Development

What is 'Deciding as Late as Possible'?
This principle is part of the Lean Software Development methodology and states that decisions should be delayed until they can be made based on facts, not assumptions. By deferring certain decisions, you can avoid making unnecessary or incorrect choices, minimize waste and react more flexibly to change.

Why is it important?
Delaying decisions until the last responsible moment allows for more informed decision-making, enabling improved flexibility and risk management. It can lead to a greater ability to respond to customer requirements and market shifts, thereby enhancing competitiveness and increasing the likelihood of project success.

How does it work?
In Lean software development, teams try to delay decisions until the latest possible moment that doesn’t negatively affect the project. This is based on the principles of 'just-in-time' production and 'set-based' design, where decisions are made when they are most informed. It isn’t about procrastination, but waiting only until you have a clearer understanding of the problem at hand.

Exam Tips: Answering Questions on Deciding as Late as Possible
When answering exam questions on this topic, remember not to confuse it with procrastination. Highlight its importance in risk management and in making informed decisions. Use real-life examples to illustrate the concept and benefits where possible. Be ready to discuss the potential challenges or drawbacks of this approach and how to overcome them. You may also need to compare this Lean principle with practices in other project management methodologies.

Remember: The ability to embrace change and adapt based on new information is a key tenet of Lean and Agile methodologies and is what this principle seeks to amplify.

Test mode:
Start practice test
PMI-ACP - Lean Software Development Example Questions

Test your knowledge of Amazon Simple Storage Service (S3)

Question 1

A key stakeholder wants to add a new feature to the project, but it would need significant changes that might delay the project timeline. What would be the best Agile Principle to apply in this instance?

Correct Answer: Decide as late as possible to give time to evaluate the impact of these changes and consult with the team and other stakeholders.

The best Agile Principle to be applied in this scenario is 'Responding to change over following a plan'. Agile is all about flexibility, continuous improvement and responding to change. Thus, it's important to consider the new request from the key stakeholder. This however, does not mean that the request should be accepted immediately without evaluation. The answer 'Decide as late as possible to give time to evaluate the impact of these changes and consult with the team and other stakeholders.' is the best approach because it aligns with Agile values. It gives time to evaluate the impact of the changes, engages the concerned team and stakeholders which fosters collaboration, an important value in Agile. On the other hand, 'Reject the stakeholder's request and stick to the original plan.' is not reflective of Agile, which values customer collaboration and responding to change 'Immediately accept the stakeholder's request without consulting with the team.' contradicts the Agile principle of giving importance to individuals and interactions. Communication and deliberation are key elements and bypassing them devalues the team. 'Halt the project until a decision is made about the feature.' is also a wrong approach as it delays the project unnecessarily instead of adapting to the situation.

Question 2

You are leading a team on a new software project. You have information about a newly released technology that could significantly speed up development, but you are not yet certain about its compatibility with your project. What is the best way to proceed?

Correct Answer: Continue using the current technology and monitor the new technology's compatibility closely before deciding.

Given the scenario, it is wise to continue using current technology while investigating the new one. Agile approaches emphasize learning and adjusting, and not taking unnecessary risks. Hence, it is a good idea to monitor whether the new technology is compatible before making a decision. The wrong approaches would be to completely ignore the new technology (failing to embrace change, a key agile principle), switch without further investigation (introducing unnecessary risk), or postpone the project until compatibility is confirmed (causing delays and possibly overlooking other workarounds or incremental progress that could be made with current technology).

Question 3

In an Agile project, a major risk is identified that could potentially affect the project's success. The solution to this risk is not readily apparent. What would be the best course of action?

Correct Answer: Iteratively develop small solutions and assess progress, deciding on the final solution as late as possible.

In the Agile methodology, when a major risk is identified that could potentially affect the project's success, and the immediate solution is not apparent, the best course of action is to 'Iteratively develop small solutions and assess progress, deciding on the final solution as late as possible.' The Agile approach is all about iteratively and incrementally tackling tasks, and this applies to risk management as well. Through iterative developments, teams can test smaller solutions and make necessary adjustments based on their effectiveness, thereby eventually mitigating the risk. The other options are not good practices. Ignoring the risk could lead to greater issues down the line. Deciding on a solution immediately without adequate investigation does not align with Agile principles as it doesn't take into account the value of iterations and feedback. Delaying the project until the full solution to the risk is figured out negates the benefit of Agile's iterative approach to problem-solving and may slow down the project's momentum.

Go Premium

PMI Agile Certified Practitioner Preparation Package (2024)

  • 3432 Superior-grade PMI Agile Certified Practitioner practice questions.
  • Accelerated Mastery: Deep dive into critical topics to fast-track your mastery.
  • Unlock Effortless PMI-ACP preparation: 5 full exams.
  • 100% Satisfaction Guaranteed: Full refund with no questions if unsatisfied.
  • Bonus: If you upgrade now you get upgraded access to all courses
  • Risk-Free Decision: Start with a 7-day free trial - get premium features at no cost!
More Deciding as Late as Possible questions
10 questions (total)
Start 10 question test