Value vs. Complexity
A prioritization framework used to assess and compare the value a feature will deliver to users against the complexity and cost of implementing it.
A prioritization framework used to assess and compare the value a feature will deliver to users against the complexity and cost of implementing it.
A team responsible for delivering specific features or enhancements, typically working on predefined requirements and focusing on the implementation of assigned features.
Test-Driven Development (TDD) is a software development methodology where tests are written before the code that needs to pass them.
A meeting at the end of a sprint where the development team presents their completed work to stakeholders.
A list of tasks and deliverables that a team commits to completing during a sprint, providing a clear focus and scope for the sprint's duration.
Must have, Should have, Could have, and Won't have (MoSCoW) is a method used to prioritize features or tasks.
A preliminary testing method to check whether the most crucial functions of a software application work, without going into finer details.
Product Requirements is a document that outlines the essential features, functionalities, and constraints of a product.
A simple sorting algorithm that repeatedly steps through the list, compares adjacent elements, and swaps them if they are in the wrong order.