Incremental Delivery means building and delivering the product in small, usable increments, allowing the customer to realize some value immediately. This concept is fundamental in Agile methods where work is broken down into small chunks known as 'user stories'. The primary advantage of incremental delivery is that it provides fast feedback on the product’s progress and allows for changes or corrections to be made early in the development process, thereby reducing the cost and time of reworking.

Story Points and Ideal Time are two estimation methods used in Agile EVM. Story Points are a unit of measure for expressing an estimate of the overall effort that will be required to implement a product backlog item or any other piece of work. It is a relative measure. Ideal Time, on the other hand, is an estimation technique where the duration is estimated based only on effective work time, ignoring any impact from interruptions. Understanding these estimation techniques is critical when using Agile EVM to compare estimates with actual progress and to project future progress.

Financial Analysis Techniques like Net Present Value (NPV) and Return on Investment (ROI) are used to determine the value and return of a project. In the context of Agile EVM, these techniques can be used to estimate the value of the work done and the return achieved from a given increment of work. NPV calculates the present value of future cash flows, and ROI computes the ratio of investment gain to its cost. Both help to quantify the value delivered in financial terms.

Velocity is a key metric in Agile EVM. It measures the amount of work a team can tackle during a single Sprint and is the key for determining project timelines. Velocity is calculated at the end of the Sprint by summing up the points for all fully completed User Stories. This concept helps Agile teams to understand how much they can deliver in a time-frame and helps to forecast future work delivery.

Burn Down Charts are used to represent work left to do versus time in an Agile project. It is a graphical representation of work left to do versus the time allocated for it. This concept helps in visualizing the amount of work done, the work remaining, and the project pace. Agile EVM leverages Burn Down Charts to track progress over time, uncovering issues in advance so that corrective actions can be taken.

Planning and monitoring iterations is one of the key concepts in Agile EVM. The team breaks down the project into smaller and manageable chunks, known as iterations. Each iteration is well-planned, executed, and monitored by considering user stories, identifying tasks and estimating the time required to complete them. Agile EVM offers value in understanding the project’s current status and predicting its future performance. Monitoring the actual time taken to perform tasks allows teams to adjust their velocity for future sprints, helping to improve project tracking and control, facilitating project management decision-making.

In Agile EVM, relative sizing or story points is a method used to estimate the effort required to complete user stories. The team assigns values known as 'story points' to each user story, reflecting the anticipated effort needed. The accumulated total of these estimates gives insight into the total effort required to deliver the project. In Agile EVM, this information is used to create the budget baseline using the expected value of each story or feature, this allows for financial tracking of the project.

Another essential concept in Agile EVM is tracking the Actual cost. The Actual Cost is the true cost incurred for the work performed. All expenses related to a project, including labour cost, materials cost, and any additional costs, are tracked. Agile EVM uses this tracking to provide an accurate reflection of how the project is faring financially, allowing project managers to make informed decisions based on actual expenditures.

Budget at Completion (BAC) is the sum of all budgets established for the project; it signifies how much the project is expected to cost upon completion. In Agile EVM, BAC can be set using the cost per story point (using the estimates provided in story points) and the number of features/stories to complete. It allows the Agile team to determine whether the project is on budget or has cost overruns (Positive or negative Variance).

Agile Release Planning is one of the most impactful concepts in Agile EVM. During this planning exercise, the team establishes the goals for software releases and aligns the scope, timeline, and resources needed to achieve them. In terms of EVM, this activity allows for the fine-tuning of resource allocation, cost forecasting, and risk assessment. This is a high-level project plan, guiding the project towards its deliverables and strategic objectives.