MoSCoW Prioritization
Must have, Should have, Could have, and Won't have (MoSCoW) is a method used to prioritize features or tasks.
Must have, Should have, Could have, and Won't have (MoSCoW) is a method used to prioritize features or tasks.
Detailed, Estimated, Emergent, and Prioritized (DEEP) is an agile project management framework for a well-maintained product backlog.
A set of criteria that a user story or task must meet before being accepted into the development cycle, ensuring it is actionable and clear.
The process of identifying, assessing, and controlling dependencies between tasks or projects to minimize risks and ensure smooth project execution.
A time management tool that helps prioritize tasks based on their urgency and importance, dividing them into four quadrants.
A project management technique that identifies the longest sequence of dependent tasks and calculates the shortest possible project duration.
A prioritized list of tasks, features, and technical debt items that need to be addressed by the engineering team.
A relative estimation technique used in Agile project management to quickly assess the size and complexity of tasks by assigning them T-shirt sizes (e.g., small, medium, large).
Getting Things Done (GTD) is a productivity methodology that emphasizes capturing tasks, organizing them, and taking action.