Focus on the business need underpins the fact that every decision taken during a project should be grounded in what the business actually needs. A project is a means to an end, not the end itself. A sound business case is at the heart of every project, and it should be based on what the business priorities are. ongoing commitment from the stakeholders is essential to ensure that the project will satisfy the business priorities. Agile Project Management has a high level of direct involvement from the business representatives on projects and in project teams. A lack of commitment to providing resources from the business to an agile project team is often the source of failure for agile projects.

Managing stakeholders so that the business delivers on these commitments is critical if the business is not involved, if they do not deliver on their commitments. Even an agile project with the best team of developers in the world will fail. The minimum usable subset represents the most Have requirements defined using the Moscow technique. The business rules that are defined in Agile Project Management ensure there is a high level of business involvement in the project. The business products that are created in the foundations phase provide a clear statement of the business vision for the project. The prioritized requirements list by the end of foundations defines the overall scope of the project and is prioritized using the Moscow technique.

This defines the high level must have should have could have and won't have for now, requirements for the project timeboxing is used to control the creation of the low level products in an iterative way, and the application of the Moscow technique prioritizes these low level products to ensure the time boxes finish on time and are continuing to meet the business need. These two techniques contribute to the successful application of this principle.