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.
Just one comment trying to add something to this interesting post. For those who will prepare the PMI-ACP certification exam take care about the terms. There is a big problem, in my understanding, with the meaning of some terms. If you read the books and documents inside the Reference List you will find more than one definition. For example, about sprints and sprint duration.
Interesting. If you could share the different definitions of these terms for the benefit of other members, it would be great. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Those terms are distributed inside the list of books. People who will prepare the exam can do that Saving Changes...
Moving on to H.
High Performance Team:
A group of people who work together for a common goal and are able to achieve great results through productive communication, innovative solutions, and great performance. Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
MoSCoW -
The MoSCoW approach to prioritization originated from the DSDM methodology (Dynamic Software Development Method), which was possibly the first agile methodology (?) – even before we knew iterative development as ‘agile’. MoSCoW is a fairly simple way to sort features (or user stories) into priority order – a way to help teams quickly understand the customer’s view of what is essential for launch and what is not. MoSCoW stands for:
? Must have (or Minimum Usable Subset)
? Should have
? Could have
? Won’t have (but Would like in future) Saving Changes...
WIP Limits:
Limiting the Work-in-Progress (WIP) helps the team in maintaining the focus on completing stories\tasks, maintaining quality, and delivering value. Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
Story Maps -
User story mapping offers an alternative for traditional agile planning approaches like the Scrum product backlog. Instead of a simple list, stories are laid out as a two dimensional map. The map provides both a high level overview of the system under development and of the value it adds to the users (the horizontal axis), and a way to organize detailed stories into releases according to importance, priority, etc. (the vertical axis). The map shows how every user story fits in the full scope.
Releases are defined by creating horizontal slices of user stories, each slice is a release. For the first release, it is recommended to build a minimal set of user stories covering all user goals, so that you build a minimal but complete system to validate functionality and architecture early. Saving Changes...
Spike:
A story or task aimed at answering a question or gathering information. If a user story cannot be estimated until the dev team does some actual work to resolve a technical question or a design problem. The output of a spike story is an estimate for the original story. Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
Escaped Defects -
Escaped Defects are those defects reported by the Customer that have escaped all software quality processes are represented in this metric. Escaping defects should then be treated as ranked backlog work items, along with other project work items. They should be prioritized high enough to resolve them within the next sprint or two and not accumulate a growing backlog. Watch the defect backlog as part of the project metrics. A growing defect backlog is a key indicator that the team is taking on more new work than it can handle. It may also be a key indicator that the team is operating as a “mini-waterfall” project, rather than a agile project, requiring more collaboration between Dev and Quality Engineers and early testing. Drop the number of new items the team works on until the escaping defects are well managed or eliminated. Saving Changes...
Scrum:
A framework for the iterative development of complex products, particularly software. Scrum is the most widely recognized Agile framework, and is compatible with other Agile practices like XP(Extreme Programming) and TDD(Test Driven Development).Iterations in Scrum are called Sprints and they are between 2 to 4 weeks. . Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
Minimally Marketable Feature (MMF) -
Start by identifying your product's most desirable features. Prioritize their value, either through a formal technique or by subjectively ranking each one against the others. Once you've done so, plan your releases around the features. Release the highest-value features first to maximize their return. To accelerate delivery, have your entire team collaborate on one feature at a time and perform releases as often as possible. Saving Changes...
