Agile Terminology Handbook

The Ultimate Guide to Agile Methodology Terms and Glossaries

Contents

• Acceptance Criteria
• Acceptance Test
• Agile Manifesto
• Agile Marketing
• Agile Mindset
• Agile Principle
• Agile Release Train
• Agile Software Development
• Agile Transformation
• Backlog
• Backlog Grooming
• Backlog Refinement
• Bottleneck
• Burndown Chart
• Burnup Chart
• Code Review
• Collaborative Development
• Continuous Integration (Cl)
• Continuous Improvement
• Daily Scrum
• Definition Of Done (DoD)
• DSDM
• Epics
• Event-Driven Development
• Feature-Driven Development
• Gantt Chart
• Increment
• Impediment
• Iteration
• Iteration Planning
• Kanban
• Kanban Board
• Lean
• Lean Startup
• Minimum Viable Product (MVP)
• Product Backlog
• Product Manager
• Product Owner
• Refactoring
• Release Plan
• Retrospective
• Retrospective Action Items
• Scaled Agile Framework
• Scrum
• Scrumban
• Scrum Board
• Scrum Master
• Scrum Meeting
• Scrum Of Scrums
• Scrum Team
• Sprint
• Sprint Goal
• Sprint Planning
• Sprint Review
• Stakeholder
• Story Points
• Task Board
• Timebox
• User Acceptance Testing (UAT)
• User Story
• Value Stream Mapping
• Velocity
• Work Item
• XP (Extreme Programming)

1. Acceptance Criteria : A set of specific and measurable requirements that must be met in order for a product or service to be considered acceptable to the customers or end users.
2. Acceptance Test : A test that verifies that a product or service meets the acceptance criteria and is ready for release.
3. Agile Manifesto : A set of guiding principles for agile software development, focusing on delivering value to the customers, working collaboratively, and being open to change.
4. Agile Marketing : A methodology for marketing that emphasizes flexibility, rapid experimentation, and continuous improvement.
5. Agile Mindset : A way of thinking that values collaboration, adaptability and continuous improvement in the pursuit of delivering value to the customers.
6. Agile Principle : A fundamental concept or belief that guides agile software development and product delivery.
7. Agile Release Train : A collection of teams that works together to deliver a set of features or capabilities in a coordinated and collaborative manner.
8. Agile Software Development : A methodology for software development that emphasizes flexibility, collaboration and continuous improvement.
9. Agile Transformation : The process of adopting agile practices and principles in an organization.
10. Backlog : A list of items, such as features or user stories, that are prioritized and planned for development in a product.
11. Bottleneck : A point in a process or system where the flow of work is restricted or slowed down.
12. Backlog Grooming : The process of reviewing and refining the backlog to ensure that it is up-to date, relevant, and aligned with the goals of the product. In 2013, grooming was changed into refinement. The Product Backlog is refined rather than groomed.
13. Backlog Refinement : The process of reviewing and updating the backlog to ensure that it is up to date and aligned with the goals of the product.
14. Burndown Chart : A graphical representation of the amount of work remaining in a sprint or project over time.
15. Burnup Chart : A graphical representation of the amount of work completed in a sprint or project over time.
16. Code Review : The process of reviewing and evaluating code to ensure that it meets quality and design standards.
17. Collaborative Development : A method of software development that emphasizes teamwork and communication among developers, customers and stakeholders.
18. Continuous Integration (CI) : A software development practice that emphasizes frequent and automated integration of code changes into a shared repository.
19. Continuous Improvement : A process of continually assessing and improving processes and product to deliver value to the customer.
20. Daily Scrum : A daily meeting in Scrum where the team discusses progress, plans and any impediments that needs to be addressed.
21. Definition of Done (DoD) : A set of criteria that must be met in order for a product or service to be considered complete and ready for release.
22. DSDM (Dynamic Systems Development Method) : An agile methodology that focuses on delivering value to the customer through rapid, iterative development.
23. Epics : A type of user story that represent large, complex feature or capability.
24. Event Driven Development : A method of software development that emphasizes responsiveness to external events or triggers.
25. Feature Driven Development : A method of software development that emphasizes delivering small, incremental features and capabilities to customers.
26. Gantt Chart : A graphical representation of a project schedule that shows the start and end date of a tasks and milestones.
27. Increments : A working version of a product that is developed and delivered in small, incremental stages.
28. Impediments : Any obstacle or barrier that prevents a team from making progress on a task or feature.
29. Iterations : A set period of time, such as a sprint, during which a team works on a specific set of tasks or features.
30. Iteration Planning : The process of planning and organizing work for an iteration or sprint.
31. Kanban : A methodology for managing work and workflow, emphasizing on visualizing work, limiting work in progress, and making process policies explicit.
32. Kanban Board : A visual tool used in kanban, to represent flow of work through different stages of a process.
33. Lean : A methodology that emphasizes on elimination waste, and maximize value, continuously improving the processes to deliver value to the customer.
34. Lean Startup : A methodology that emphasizes rapid experimentation and learning to validate and improve product ideas.
35. Minimum Viable Product (MVP) : A product or service that has the minimum set of features and capabilities needed to be released to customers for testing and feedback.
36. Product?Backlog : A prioritized list of features, user stories and other items that are planned for development in a project.
37. Product Manager : A person responsible for the overall strategy and success of a product.
38. Product Owner : A person responsible for representing the needs and priorities of the customer and stakeholders in a product development process.
39. Refactoring : The process of reviewing and improving existing code to make it more efficient, maintainable and scalable.
40. Release Plan : A plan for delivering a product or service to customer including the features, capabilities and release date.
41. Retrospective : A meeting held at the end of a sprint or project (Waterfall) to review and reflect on the process, successes and areas of improvement.
42. Retrospective Action Items : Specific action or tasks that are identified during a retrospective and assigned to team members for improvements.
43. Scaled Agile Framework : A framework for scaling agile practices and principles to large, complex project and programs.
44. Scrum : A framework for agile software development that emphasizes on teamwork, collaboration and iterative development.
45. Scrumban : A hybrid methodology that combines elements of scrum and kanban to manage work and workflow.
46. Scrum Board : A visual tool used in scrum, to represent the flow of work through different stages of a sprint.
47. Scrum Master : A person responsible for facilitating and coaching the scrum team in following the scrum framework.
48. Scrum Meeting : A regular meeting in scrum, such as the daily scrum, sprint planning, sprint review, or sprint retrospective.
49. Scrum of Scrums : A meeting where representatives from multiple scrum teams come together to share information and coordinate efforts.
50. Scrum Team : A cross functional team of individuals who work together to deliver a product or service using the scrum framework.
51. Sprint : A set period of time usually 2-4 weeks, during which a scrum team works on a specific set of tasks or features.
52. Sprint Goal : A clear and specific goal that the scrum team set for themselves to achieve during a sprint.
53. Sprint Planning : A meeting held at the beginning of a sprint where the scrum team plan and organizes the work they will complete during the sprint.
54. Sprint Review : A meeting held at the end of a sprint where the scrum team demonstrates the work they completed during the sprint and receives feedback from the stakeholders.
55. Stakeholder : A person or group who has an interest or stake in the success of a project or product.
56. Story Points : A way of measuring the relative complexity and effort required for a user story or a task.
57. Task Board : A visual tool used to track the progress of tasks or user stories through different stages of a processes.
58. Timebox : A set period of time during which a specific task or activity must be completed.
59. User Acceptance Testing (UAT) : Testing done by the end users or customer to ensure that the product or service meets their needs and requirements.
60. User Story : A short, simple description of a feature or capability that a user needs or wants in a product.
61. Value Stream Mapping : A visual representation of the flow of work and value through a process or system.
62. Velocity : A measure of the amount of work that a team can complete in a given period of time.
63. Work Item : A specific task or item of work that needs to be completed such as a user story or bug fix.
64. XP (Extreme Programming) : A methodology for agile software development that emphasizes rapid feedback, pair programming and test driven development.

For More Interesting Content Follow Me On LinkedIn