1 / 6

GLOSSARY OF TERMS

GLOSSARY OF TERMS. Terms and Definitions (1/5). No. Term. Short Definition. 1. Also known as ‘conditions of satisfaction’. Requirements that have to be met for the story to be considered complete. Acceptance criteria. 2.

porterpatricia
Download Presentation

GLOSSARY OF TERMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GLOSSARY OF TERMS

  2. Terms and Definitions (1/5) No Term Short Definition 1 Also known as ‘conditions of satisfaction’. Requirements that have to be met for the story to be considered complete. • Acceptance criteria 2 Acceptance testing is a validation activity conducted by the product owner to determine whether what has been built satisfies the acceptance criteria. Typically included in the definition of done for the team. • Acceptance testing 3 A framework for executing software projects; Agile is a combination of process and engineering practices. • Agile 4 A modern toolset to facilitate agile practices, drive discipline and create agile habits across the areas of continuous delivery, rapid prototyping and project & backlog management. • Agile Tools 5 Time for the team to look ahead and synchronize on the backlog – review stories, estimate, update/refine acceptance criteria, pre-plan for the next sprint and more. • Backlog refinement 6 A burn-down chart is a visual tool for measuring and displaying progress. Visually, a burn-down chart is simply a line chart representing remaining work over time. • Burn-down chart 7 A burn-up chart is an information radiator showing functionality completed over time. Progress trends up as stories are completed and value is accumulated. Valuable to track at a release level. Burn-up charts do not show work-in-progress (see WIP). • Burn-up chart 8 The measure of how much work can be completed with a given sprint by estimating the number of available, productive working hours for each team member. Takes into account meetings, vacations, training etc. Leveraged during sprint planning. • Capacity 9 An engineering practice used in software development to automate and improve the process of software delivery. • Continuous integration Source: Sasol Digital Catalyst

  3. Terms and Definitions (2/5) No Term Short Definition 10 Is to establish a reliable and dependable working rhythm for the team which demonstrates predictable practices. • Cadence 11 • Component team (non-agile delivery team) Team staffed to provide products / components to the agile solution delivery team with clear deliverables and timeframes defined as part of the release commitment 12 • Done The various tasks that need to happen before a story is considered potentially releasable. Explicitly defined and agreed upon by the entire team. The definition of ‘Done’ is important so that each team member means exactly the same think when they determine a story is completed 13 Meeting held each day for the team to understand its progress in order to do a daily “inspect and adapt cycle”. Team members share answers to 3 questions in 15 minutes: 1) What did I do yesterday? 2) What I plan to do today? 3) Are there any impediments in my way? • Daily stand-up 14 The process of agreeing on a size for stories. Only done by the team responsible for delivering the work, typically in story points or t-shirt sizes. • Estimation 15 A very large user story that cannot be completed in one Sprint and is eventually broken down into smaller stories. • Epic 16 Engineering practices enable delivery teams to achieve Agile goals and a few practices are “must do” to successfully implement Agile. • Engineering practices 17 Specific skills needed to deliver the project though may not be 100% dedicated. Clear and specialized roles defined (e.g. project manager, deployment team member etc.) • Extended team Source: Sasol Digital Catalyst

  4. Terms and Definitions (3/5) No Term Short Definition 18 Is a work and workflow visualization tool that enables the team to optimize the flow of work. Physical Kanban boards, typically use sticky notes on a whiteboard to communicate status, progress, and issues. • Kanban board 19 • Minimal viable product (MVP) Minimum viable product (MVP) is the product with the highest return on investment and filters out users who aren’t your target audience. • Not every user is appropriate for every type of functionality. • Capitalize on refining / enhancing existing functionality 20 A consensus-based technique for estimating, mostly used to estimate effort or relative size of stories in Agile. Typically leverages a Fibonacci sequence point scale. • Planning Poker 21 • Product Backlog A prioritized list of all known features or outstanding work necessary to bring the product to life. This may include customer/ user needs, technological, functional and non-functional requirements. The backlog is a living document maintained and managed by the product owner team. 22 • Potentially Shippable product Functionality that has been designed, fully implemented and tested with no major defects 23 Owns the overall product vision, roadmap, release goals and priorities. Is responsible for managing the product backlog and ensuring the value of the work the team performs. Works day-to-day with the team and is empowered to make product decisions. • Product owner (PO) 24 Deployable software package that is the culmination of several iterations and is the distribution of the final version of an application. A software release may be either public or private. • Release 25 Is a regular review of the team and its process. Focuses on "how" the team is building software and identifies how to get better for the next sprint • Retrospective Source: Sasol Digital Catalyst

  5. Terms and Definitions (4/5) No Term Short Definition 26 Often referred to as ‘research’ stories. Spikes are usually technical in nature and intended to provide just enough information so the team can estimate the size of the story or determine next steps. Spike stories should be time-boxed and have a clearly defined deliverable. • Spike 27 An iterative and incremental software development agile framework for managing product development. Scrum works well to deliver units of work in changing environments while productively and creatively delivering the highest business value. • Scrum 28 A set period of time during which specific work has to be completed. A foundational sprint for the team before development begins. • Sprint zero 29 A fixed, repeatable time box – usually ranges between 1-4 weeks. By the end of each sprint, the Scrum team produces a potentially shippable increment of working software. • Sprint 30 A subset of the product backlog that the team commits to during sprint planning for the upcoming sprint • Sprint backlog 31 A meeting where the team plans and commits to what can be accomplished during the next sprint • Sprint planning 32 Each Sprint is followed by a Sprint review. During this review the software developed in the previous sprint is reviewed and if necessary new backlog items are added. • Sprint review (demo) 33 • Story points A unit of relative estimation that measures complexity, difficulty, and size of a user story 34 Is the facilitator of the Scrum process and coaches the team in implementing agile practices. Works with the team to remove impediments and accelerate velocity. • Scrum Master (SM) 35 Drives the technical direction of the project and coaches the team. Works closely with the PO and SM to enable the team achieve their sprint and release goals • Solution Architect Source: Sasol Digital Catalyst

  6. Terms and Definitions (5/5) No Term Short Definition 36 Delivers potentially shippable software at every sprint. Staffed with cross functional team members that are self-organizing and empowered • Scrum team 37 • Stakeholders / Sponsors Individuals who have a vested interest in the outcome of the project. Typically engage with the team on Sprint reviews. 38 Business and IT leadership invested in supporting the success of the project and removing impediments • Steering Committee 39 A user story can be broken down in to one or more tasks. Tasks are typically estimated in hours • Task 40 Also known as the delivery team - set of cross-functional individuals who are responsible for delivering the potentially shippable increment of working software each sprint • Team 41 The core product feature/(s) that identify the product. A theme is a collection of epics and user stories. We could put a rubber band around a group of stories and we could call a “theme” • Theme 42 It is simply something that the user wants and has business value. A short & simple description, written from the user prospective. • User Story 43 Personas are a description of the typical users of a given software. A persona description should include: Skills and background – E.g. professional or beginner computer user and Goals: E.g. what does the user expect from the product? • User Personas 44 Community of direct benefactors of the solution being developed who can incrementally help validate the solution • User focus group 45 It is a relative number which describes how much work the team can get done per sprint • Velocity Source: Sasol Digital Catalyst

More Related