Rules: >You start from the last letter of the term posted previously. >In case, more than one terms posted with same letters (concurrently posted), you start with the latest term. >Only PMI-ACP® Terms in this relay. >A term may include multiple words. >Acronyms are fine. please include the expansion before the description. >Your term needs to be followed by a short description of the term. >No successive posting of term by the same member. The below one is fine. member A: --------L member B: L----- --- ----D member A: D---- ------ ---- > If you don't get a term starting from a particular letter(last letter of previous term), feel free to start from the next letter. e.g. previous term - buzz, if you don't get a term starting with 'z', you may start with 'a'. (Hoping this rule will be rarely used.:) >End date of game: No end date. Till the game goes on.
Sprint:
The uninterrupted period of time in which an Agile team performs work, one week to four weeks in length, at the end of which the team delivers “potentially shippable” product. A new feature or feature set, or the improvement/expansion of an existing feature that was completed in an earlier iteration may be the deliverable. Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
Transition Indicator -
A transition indicator is a notification that a risk (i.e., something that will have a negative impact on the cost/schedule of the project if it occurs) has materialized and is in need of attention. Saving Changes...
Retrospective:
A time boxed meeting held at the end of an iteration, or at the end of a release, in which the team examines its processes to determine what went well, what could be stopped and what could be improved. Retrospective can be done at 3 levels, Project, Release and Iteration. It is not just a lessons learned exercise but more focus on action items for continuous improvement. Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
skipping E:
Feature Breakdown Structure (FBS)
During detailed planning, agile development favors a feature breakdown structure (FBS) approach instead of the work breakdown structure (WBS) used in waterfall development approaches. Feature breakdown structures are advantageous for a few reasons:
1. They allow communication between the customer and the development team in terms both can understand.
Last Updated 6/15/2015
2. They allow the customer to prioritize the team's work based on business value.
3. They allow tracking of work against the actual business value produced.
It is acceptable to start out with features that are large and then break them out into smaller features over time. This allows the customer to keep from diving in to too much detail until that detail is needed to help facilitate actual design and delivery. Saving Changes...
Fail Fast:
A strategy of trying something, getting fast feedback, and then rapidly inspecting and adapting. In case of high levels of uncertainty, it is often less expensive to start working on a product, learn whether we made a good decision, and if not,we should kill it fast before more money is spent. Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
Tail Length -
The tail is the time period from “code slush” (true code freezes are rare) or “feature freeze” to actual deployment. This is the time period when companies do some or all of the following: beta testing, regression testing, product integration, integration testing, documentation, defect fixing. Saving Changes...
Impediment:
Any obstacle preventing a team member from completing the assigned work. In Scrum, in the daily stand up meeting , one of the 3 questions each member answers is: What impediments stand in your way?
E.g.
A lack of technical expertise.
A technical issue (eg, a network is down). Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
Task Boards
Similar to Kanban Boards, a task board tracks the progress of work that is part of an overall story. Saving Changes...
Technical Debt:
Work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on.The technical debt comes in the form of the extra effort that we have to do in future development because of the quick and dirty design choice.
Examples:
Postponing decision on automation testing tool resulting in more manual testing.
Piling number of defects to be fixed. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Timeboxing - allocating a fixed time period, called a time box, to each planned activity. The goal is to fix the time in lieu of fixing the scope. Saving Changes...
