agile - Concepts

Explore concepts tagged with "agile"

Total concepts: 38

Concepts

Scrum Master - The Scrum role responsible for facilitating the process and removing team impediments.
Agile Manifesto - A foundational declaration of values and principles for iterative, collaborative software development.
Visual Management - Using visual displays to communicate status, progress, and standards at a glance.
Affinity Estimation - A collaborative estimation technique where team members silently group work items by relative size to quickly estimate large backlogs.
Job Story - A requirements format from JTBD that focuses on the situation and motivation rather than the user persona, using 'When... I want to... So I can...' structure.
Host Leadership - A leadership approach where leaders act as hosts who prepare the space, invite participation, and step back to let teams work autonomously while retaining authority to intervene.
Velocity - A measure of the amount of work a team completes during a sprint, used for planning.
Product Owner - The Scrum role responsible for maximizing product value through backlog management.
Sprint Retrospective - A team meeting at the end of each sprint to reflect on process and identify improvements.
Delegation Poker - A Management 3.0 card game where teams collaboratively decide the appropriate delegation level for decisions and tasks.
Daily Standup - A brief daily team meeting to synchronize work and identify blockers.
Acceptance Criteria - Specific conditions that must be met for a user story or feature to be considered complete and acceptable.
Pair Programming - An agile software development technique where two programmers work together at one workstation, sharing a single screen and keyboard.
Definition of Done - A shared checklist of criteria that must be met for work to be considered complete.
Delegation Board - A visual management tool that maps delegation levels for different decision areas, making authority boundaries transparent.
Burndown Chart - A visual graph showing remaining work over time to track sprint or project progress.
Extreme Programming - An agile software development methodology that emphasizes technical excellence, continuous feedback, and close customer collaboration through practices taken to their logical extremes.
Scrum - An agile framework for managing complex work through iterative sprints and defined roles.
Sprint - A fixed-length iteration in Scrum where a team completes a set of committed work.
Backlog - A prioritized list of all desired work items for a product or project.
Release Early, Release Often - A software development philosophy advocating frequent releases to gather feedback and iterate quickly.
Information Radiators - Visible displays that broadcast important information to anyone who passes by.
Iterative and Incremental Note-Taking - A methodology that treats notes as living documents refined through continuous small improvements over time.
Rapid Experimentation - Running quick, low-cost experiments to test ideas and learn before major investments.
Retrospective - A structured team meeting held after a project or iteration to reflect on what went well, what didn't, and how to improve.
Behavior-Driven Development - A software development methodology that extends TDD by writing tests as human-readable specifications describing expected behavior from the user's perspective.
Definition of Ready - Shared criteria that must be met before a work item can be started by a team.
Cross-Functional Teams - Teams composed of members with different functional expertise working toward shared goals.
Scrumban - A hybrid agile approach combining Scrum's structure with Kanban's flow-based principles.
Planning Poker - A consensus-based estimation technique where team members simultaneously reveal cards to estimate effort.
T-Shirt Sizing - An estimation technique using clothing sizes (XS, S, M, L, XL) to categorize work items by relative effort.
Test-Driven Development - A software development approach where tests are written before the code they validate, following a red-green-refactor cycle.
Sprint Planning - A collaborative meeting where the team selects and plans work for the upcoming sprint.
Iterative Development - A software development approach that builds systems through repeated cycles of planning, building, testing, and refining.
Software Estimation - The process of predicting the effort, time, or cost required to develop software, using various techniques to manage inherent uncertainty.
Sustainable Pace - Working at a consistent rate that can be maintained indefinitely without burnout, enabling long-term productivity and well-being.
Story Points - A relative estimation unit measuring the effort and complexity of user stories.
User Stories - Short descriptions of features from the user's perspective used to capture requirements.

← Back to all concepts