Agile estimation techniques are used in Agile software development methodologies, such as Scrum and Kanban, to estimate the effort, time, and complexity of various tasks or user stories within a project. These techniques help teams make informed decisions, prioritize work, and plan their iterations effectively. Here are some common Agile estimation techniques:

1. Planning Poker (Relative Estimation): In Planning Poker, team members use a deck of cards with numbers representing estimates (e.g., Fibonacci sequence or modified Fibonacci sequence) to estimate the relative size or complexity of user stories. Team members discuss their estimates and reach a consensus. This technique encourages team collaboration and avoids anchoring bias.
2. T-shirt Sizing: Instead of using numbers, teams can use t-shirt sizes (XS, S, M, L, XL) to estimate user stories. This technique is less precise than Planning Poker but can be quicker and is useful for high-level estimations.
3. Dot Voting: Each team member is given a certain number of dots (votes), and they use these dots to vote on the estimated effort or complexity of user stories. It’s a simple and quick way to prioritize items on a backlog.
4. Bucket System: In the bucket system, user stories are divided into different buckets based on their complexity or size, such as “Small,” “Medium,” and “Large.” This approach is less granular than Planning Poker and can be faster for estimating large backlogs.
5. Story Points: Teams assign story points to user stories based on their complexity and effort required. Story points are a relative measurement and don’t represent specific units of time. Common scales include Fibonacci or powers of 2.
6. Ideal Days or Hours: Some teams prefer to estimate in ideal days or hours, representing the actual time they expect a task to take if no interruptions or delays occur. This technique is less common in Agile but may be used in some situations.
7. Reference Stories: Teams use previously completed user stories as reference points to estimate new ones. This approach leverages historical data and helps maintain consistency in estimation.
8. Three-Point Estimation: This technique involves assigning three values to each user story: the best-case estimate, the worst-case estimate, and the most likely estimate. These values are used to calculate a weighted average, providing a more probabilistic estimate.
9. Affinity Estimation: This technique involves grouping user stories into categories or clusters based on their similarities in complexity or effort. It can help identify patterns and simplify estimation.
10. Monte Carlo Simulation: Teams use statistical techniques and simulations to estimate project completion dates and identify potential risks. It involves running multiple simulations to account for uncertainty in estimates.

Remember that Agile estimation is not about achieving perfect accuracy but about facilitating communication, collaboration, and prioritization within the team. Teams should continually refine their estimation techniques and adapt them to their specific needs and context.