{"id":641,"date":"2024-07-02T10:23:52","date_gmt":"2024-07-02T10:23:52","guid":{"rendered":"https:\/\/te-culture.com\/ScrumMasteryHub\/?page_id=641"},"modified":"2024-07-02T10:23:52","modified_gmt":"2024-07-02T10:23:52","slug":"vocabularies","status":"publish","type":"page","link":"https:\/\/te-culture.com\/ScrumMasteryHub\/vocabularies\/","title":{"rendered":"vocabularies"},"content":{"rendered":"\n<h2 class=\"wp-block-heading alignwide has-text-align-center\">LIST OF VOCABULARY WORDS<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Acceptance Criteria:<\/strong> Conditions that a product must satisfy to be accepted by a user or customer.<\/li>\n\n\n\n<li><strong>Agile: <\/strong>A methodology that promotes continuous iteration of development and testing throughout the software development lifecycle.<\/li>\n\n\n\n<li><strong>Backlog: <\/strong>A list of tasks or features prioritized by importance and to be addressed by the development team.<\/li>\n\n\n\n<li><strong>Burn-Down Chart:<\/strong> A visual representation of work left to do versus time.<\/li>\n\n\n\n<li><strong>Burn-Up Chart:<\/strong> A chart that shows work completed against a total scope.<\/li>\n\n\n\n<li><strong>Cross-Functional Team:<\/strong> A team composed of members with various functional expertise working towards a common goal.<\/li>\n\n\n\n<li><strong>Daily Scrum:<\/strong> A short meeting held daily for the development team to synchronize activities and plan for the next 24 hours.<\/li>\n\n\n\n<li><strong>Definition of Done: <\/strong>A clear and concise list of requirements that software must adhere to for it to be considered complete.<\/li>\n\n\n\n<li><strong>Definition of Ready:<\/strong> A checklist that ensures user stories are ready to be worked on.<\/li>\n\n\n\n<li><strong>Development Team: <\/strong>A group of professionals responsible for delivering a potentially releasable increment of the product.<\/li>\n\n\n\n<li><strong>Epic: <\/strong>A large body of work that can be broken down into smaller tasks or user stories.<\/li>\n\n\n\n<li><strong>Feature:<\/strong> A distinct aspect of a product, such as a function or characteristic.<\/li>\n\n\n\n<li><strong>Increment: <\/strong>The sum of all the product backlog items completed during a sprint, along with the increments of all previous sprints.<\/li>\n\n\n\n<li><strong>Iteration: <\/strong>A time-boxed period during which development occurs.<\/li>\n\n\n\n<li><strong>Kanban:<\/strong> A visual process-management method that tells what to produce, when to produce it, and how much to produce.<\/li>\n\n\n\n<li><strong>Lean:<\/strong> A methodology focused on minimizing waste within manufacturing systems while simultaneously maximizing productivity.<\/li>\n\n\n\n<li><strong>Planning Poker: <\/strong>A consensus-based technique for estimating, mostly used to estimate effort or relative size of development goals.<\/li>\n\n\n\n<li><strong>Product Backlog<\/strong>: An ordered list of everything that might be needed in the product.<\/li>\n\n\n\n<li><strong>Product Backlog Refinement:<\/strong> The act of adding detail, estimates, and order to items in the product backlog.<\/li>\n\n\n\n<li><strong>Product Owner:<\/strong> The person responsible for maximizing the value of the product and the work of the development team.<\/li>\n\n\n\n<li><strong>Release Planning:<\/strong> The process of planning the features and timeline for the release of a product.<\/li>\n\n\n\n<li><strong>Retrospective:<\/strong> A meeting held at the end of an iteration in which the team discusses what went well and what could be improved.<\/li>\n\n\n\n<li><strong>Scrum:<\/strong> An Agile framework for managing knowledge work, with an emphasis on software development.<\/li>\n\n\n\n<li><strong>Scrum Master: <\/strong>A facilitator for the team and the product owner, ensuring that the Scrum process is followed.<\/li>\n\n\n\n<li><strong>Scrum Team: <\/strong>A self-organizing team consisting of a Scrum Master, Product Owner, and development team.<\/li>\n\n\n\n<li><strong>Scrumban: <\/strong>A hybrid methodology that combines Scrum and Kanban.<\/li>\n\n\n\n<li><strong>Sprint:<\/strong> A time-boxed period, usually 1-4 weeks, during which a specific set of work must be completed and made ready for review.<\/li>\n\n\n\n<li><strong>Sprint Backlog:<\/strong> A list of the work to be performed during the sprint, typically derived from the product backlog.<\/li>\n\n\n\n<li><strong>Sprint Goal:<\/strong> A short, concise statement of what the team plans to achieve during the sprint.<\/li>\n\n\n\n<li><strong>Sprint Planning: <\/strong>A meeting where the team selects a set of product backlog items to work on during a sprint.<\/li>\n\n\n\n<li><strong>Sprint Retrospective: <\/strong>A meeting where the team looks back on the sprint to discuss what went well and what needs improvement.<\/li>\n\n\n\n<li><strong>Sprint Review:<\/strong> A meeting where the team demonstrates what they accomplished during the sprint.<\/li>\n\n\n\n<li><strong>Stakeholder:<\/strong> Anyone with an interest in the outcome of a project, such as customers, users, or sponsors.<\/li>\n\n\n\n<li><strong>Story Point:<\/strong> A unit of measure used in Agile to estimate the effort required to implement a story.<\/li>\n\n\n\n<li><strong>Task: <\/strong>A piece of work assigned to a person or team to accomplish a goal.<\/li>\n\n\n\n<li><strong>Test-<\/strong>Driven Development (TDD): A software development process that relies on the repetition of a very short development cycle.<\/li>\n\n\n\n<li><strong>User Story:<\/strong> A simple description of a feature written from the perspective of the person who desires the new capability.<\/li>\n\n\n\n<li><strong>Velocity: <\/strong>A measure of the amount of work a team can tackle during a single sprint.<\/li>\n\n\n\n<li><strong>WIP (Work in Progress) Limit: <\/strong>A strategy for preventing bottlenecks in a process by limiting the amount of work in progress.<\/li>\n\n\n\n<li><strong>Agile Manifesto:<\/strong> A formal proclamation of four key values and 12 principles to guide an iterative and people-centric approach to software development.<\/li>\n\n\n\n<li><strong>Iteration Review:<\/strong> A meeting to inspect the increment and adapt the product backlog if needed.<\/li>\n\n\n\n<li><strong>Refactoring: <\/strong>The process of restructuring existing computer code without changing its external behavior.<\/li>\n\n\n\n<li><strong>Scrum of Scrums: <\/strong>A technique to scale Scrum up to large groups (over a dozen people), consisting of dividing the groups into smaller teams of 5-10.<\/li>\n\n\n\n<li><strong>Servant Leader: <\/strong>A leadership philosophy in which the main goal of the leader is to serve.<\/li>\n\n\n\n<li><strong>Sprint Zero:<\/strong> An initial sprint used for planning and setting up the infrastructure and environment needed for development.<\/li>\n\n\n\n<li><strong>Time-Boxing:<\/strong> Allocating a fixed, maximum unit of time for an activity.<\/li>\n\n\n\n<li><strong>Wireframe:<\/strong> A visual guide that represents the skeletal framework of a website or application.<\/li>\n\n\n\n<li><strong>XP (Extreme Programming): <\/strong>A software development methodology aimed at improving software quality and responsiveness to changing customer requirements.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>LIST OF VOCABULARY WORDS<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"nf_dc_page":"","footnotes":""},"class_list":["post-641","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/te-culture.com\/ScrumMasteryHub\/wp-json\/wp\/v2\/pages\/641","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/te-culture.com\/ScrumMasteryHub\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/te-culture.com\/ScrumMasteryHub\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/te-culture.com\/ScrumMasteryHub\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/te-culture.com\/ScrumMasteryHub\/wp-json\/wp\/v2\/comments?post=641"}],"version-history":[{"count":1,"href":"https:\/\/te-culture.com\/ScrumMasteryHub\/wp-json\/wp\/v2\/pages\/641\/revisions"}],"predecessor-version":[{"id":642,"href":"https:\/\/te-culture.com\/ScrumMasteryHub\/wp-json\/wp\/v2\/pages\/641\/revisions\/642"}],"wp:attachment":[{"href":"https:\/\/te-culture.com\/ScrumMasteryHub\/wp-json\/wp\/v2\/media?parent=641"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}