Rolling Wave Planning is an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level. It is a form of progressive elaboration. Therefore, work can exist at various levels of detail depending upon its proximity to the execution timeframe. As that work gets closer, the details are refined and decomposed in more detail. This concept aligns with the adaptive planning principle of agile as it accommodates changes and refinement in the plan as more clarity emerges with time.

Progressive elaboration is a project management technique that allows for the refinement of detailed plans as more information becomes available. Rather than trying to plan everything in detail from the start (which is nearly impossible in a complex project), project teams using progressive elaboration create high-level plans and then define details as the project unfolds and more information is known. This way of approaching planning allows for better adaptation to changes and risk.

The concept of value-based prioritization underpins the execution of any agile project. Rather than focusing on how tasks can be completed most efficiently, value-based prioritization aligns all efforts towards delivering the maximum business value. It is a method used to select and order the highest return tasks for greatest value. In adaptive planning, this is crucial as it provides a means to handle change requests, new requirements, and modifications in a way that delivers the best value in the shortest time.

Emergent Design is a concept in Agile that promotes the creation of a system design in an incremental, iterative manner starting from simple, foundational system elements. As opposed to attempting to fully define a comprehensive design from the beginning of a project, an emergent design evolves over time as a system is developed and new requirements are discovered. This is an essential component of adaptive planning as it focuses on flexibility and allows for changes that surely emerge during development.

Feedback loops, integral to agile processes, refer to the process of using information about the output of a system to regulate the system. In the context of agile development, feedback loops involve activities like reviews, retrospectives, and constant customer interactions to gather feedback and make suitable changes in the work process or product accordingly. This approach of incorporating feedback regularly makes the planning truly adaptive, as it promotes learning from experiences and adapting plans based on real situations and responses.

Adaptive Planning accepts that change is a constant entity in any project. Rather than fearing change, this concept encourages us to embrace it as it brings new opportunities and challenges. Change as a constant means that the team must always be prepared to adapt their plans to meet evolving project needs. It acknowledges that as new information becomes available, project parameters can change and the team should be ready to pivot. In Agile projects, change is embraced rather than rejected. Customer feedback, market shifts, technology updates, all are likely to influence the project and the plans must be flexible to adapt to these changes promptly and efficiently.

Adaptive Planning understands and accepts the inherent variability in projects. This concept encourages teams to adapt their planning approaches according to the variability in customer needs, market conditions, technologies, resources, etc. Responding to variability is about adjusting plans based on real-time information and feedback, allowing for quick course corrections and realignment with project goals. This practice helps to mitigate risks, maximize resources, and deliver the best possible outcome in any given situation.

Adaptive planning emphasizes the importance of customer collaboration. It places customers at the forefront and encourages constant interaction with them to understand their evolving needs and expectations better. It implies that instead of being rigid in planning, teams should adapt their plans based on customers' feedback. The ultimate goal is to provide the maximum value to the customer, and direct input from the customer paves the way to achieve this.

Empirical Control, or empiricism, refers to making decisions based on what is experienced, learned, and known rather than on theory or speculation. To apply empirical control, a process must be transparent, inspected, and adapted. Inspection uncovers the current status and variances, and adaptation gradually adjusts the process for improved outcomes. Empirical control is an essential part of agile project management as it underpins the use of feedback to guide planning and action.

Scrum is an Agile development methodology used primarily for managing software development projects. It introduces the idea of iterative progress while promoting teamwork. Teams using Scrum break their work into small, manageable units called 'sprints'. The team adapts its process and methods based on the lessons learned from previous sprints. This approach reduces uncertainty and risk, as changes can be made early in the process rather than having to wait until a final product is completed.

Lean principles, originating from manufacturing, offer a useful approach to minimize waste and optimize resources in software development. These principles include defining value from the customer's perspective, identifying the value stream, making the value flow without interruptions, letting the customer pull value, and pursuing perfection. These principles provide a framework for creating more efficient processes, continually improving, and enhancing the ability to adapt to change.

Kanban is another approach used in agile project management. It helps manage workflow by visualizing work, limiting work in progress, and enhancing flow. Built on the principle that work should be released early and often, Kanban aids in adaptive planning by allowing teams to visualize their work, identify bottlenecks, and make necessary adjustments. This approach promotes transparency and allows for real-time communication of capacity and full-stack connectivity.