Scrum/Agile Glossary
Glossary from scrum.org and agilemanifesto.org
Glossary from scrum.org and agilemanifesto.org
Kartei Details
| Karten | 104 |
|---|---|
| Lernende | 11 |
| Sprache | English |
| Kategorie | Allgemeinbildung |
| Stufe | Andere |
| Erstellt / Aktualisiert | 11.06.2020 / 15.01.2025 |
| Weblink |
https://card2brain.ch/box/20200611_scrum_glossary
|
| Einbinden |
<iframe src="https://card2brain.ch/box/20200611_scrum_glossary/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
Test-Automation is not only a way to increase the quality of a product, it also helps to reduce cycle time. If you see test execution as one form of feedback, automated tests help to get this feedback much earlier. This lowers the effort of fixing issues and allows to deliver releasable increments much faster.
Test-Driven Development (TDD) is a test-first software development practice in which test cases are defined and created first, and subsequently executable code is created to make those tests pass. The failing tests are constructed to pass as development proceeds and tests succeed.
Technical Debt is the typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership. May exist unintentionally in the Increment or introduced purposefully to realize value earlier.
Testing in Production means to execute various tests right in the production environment. To reduce the risk of affecting production operations with untested and failing functionality, various technologies can be used to make the new functionality only available to the test process or a very small set of users while other users will use the previous functionality. The change will be rolled out to all users once the test was successful. This practice will help you to get rid of various test stages like QA, UAT, Staging etc. And as the tests run in the real production environment, you can eliminate the risk of using a test environment that behaves slightly different from your production environment.
A User Story is an agile software development practice from Extreme Programming to express requirements from an end user perspective, emphasizing verbal communication. In Scrum, it is often used to express functional items on the Product Backlog.
A Unit Test is a low-level technical test focusing on small parts of a software system that can be executed fast and in isolation. The definition and boundaries of a ‘unit’ generally depends on the context and is to be agreed upon by the Developers.
Velocity is an optional but often used indication of the amount of Product Backlog turned into an Increment of product during a Sprint. It is tracked by the Developers for use within the Scrum Team.
Vertical Teams combine all the necessary competencies to handle the whole process end-to-end. In such scenarios teams typically are only responsible for small parts of the whole product. So instead of splitting the organization into horizontal layers (departments) this approach suggests slicing the product.
Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.
through early and continuous deliveryof valuable software.
Agile processes harness change forthe customer's competitive advantage.
frequently, from acouple of weeks to a couple of months, with apreference to the shorter timescale.
together daily throughout the project.
Give them the environment and support they need,and trust them to get the job done.
face-to-face conversation.
primary measure of progress.
The sponsors, developers, and users should be ableto maintain a constant pace indefinitely.
agility.
the art of maximizing the amountof work not done
self-organizing teams.
the team reflects on howto become more effective, then tunes and adjustsits behavior accordingly.
