Big Agile

A visual task prioritization framework that helps teams make decisions on the most important work through a pyramid structure with WIP limits, guiding groups to filter tasks and agree on priorities through limited space at each level.

Prioritization technique developed in 1994 for use in rapid application development and Agile methodologies. Categorizes requirements into Must have, Should have, Could have, and Won't have to reach common understanding with stakeholders on delivery priorities. Widely used with timeboxing in Scrum and DSDM.

Project time estimation technique using three values: optimistic (best case), most likely (realistic), and pessimistic (worst case) scenarios to calculate weighted average. Originally developed for the US Navy's Polaris program, now widely used in project management for more accurate time and cost predictions.

Agile estimation technique where team members use cards to provide time/effort estimates for tasks anonymously before discussion. Combines individual expertise with team consensus to improve estimation accuracy and reduce anchoring bias.

A relative estimation method in Agile that measures complexity, effort, and risk rather than time, using techniques like Planning Poker and tracking team velocity for predictable sprint planning.

A stakeholder-driven prioritization approach that categorizes requirements and features as Must have, Should have, Could have, and Won't have to prevent scope creep and ensure focus.