From 5d5a34b87b1d316d59c4f3d2f66119a5de306f24 Mon Sep 17 00:00:00 2001 From: JanC <108794854+janc-pxl@users.noreply.github.com> Date: Fri, 25 Oct 2024 09:40:50 +0200 Subject: [PATCH] PUBLISHER #147 * PUSH NOTE : 004 Kwaliteitsmanagement.md * PUSH NOTE : @wikipediakwaliteitsmanagement_2020.md * PUSH NOTE : @hogeschoolpxl_2024.md * PUSH NOTE : @governmentofwesternaustralia_2017.md * PUSH NOTE : @cspo_2021.md * PUSH NOTE : @sickipedia_2021.md * PUSH NOTE : @stefanowicz_2024.md * PUSH NOTE : @beljaars_2020.md * PUSH NOTE : 007 Agile Projectmanagement.md * PUSH NOTE : @stanley.etal_2020.md * PUSH NOTE : @martin_2020.md * PUSH NOTE : @zentaoteam_2022a.md * PUSH NOTE : @verheyen_2022.md * PUSH NOTE : @userstorymap_2022.md * PUSH NOTE : @qframe_2021.md * PUSH NOTE : @scrumguide_2022.md * PUSH NOTE : @visualparadigm_2022.md * PUSH NOTE : @visual-paradigm_2022.md * PUSH NOTE : @raghuprasad_2019.md * PUSH NOTE : @productplan_2022.md * PUSH NOTE : @agile4all_2019.md * PUSH NOTE : @vanderwardt_2017.md * PUSH NOTE : @agilescrumgroup_2018.md * PUSH NOTE : @vanlier_2018.md * PUSH NOTE : @vanrooden_2015.md * PUSH NOTE : @vanrooden_2015a.md * PUSH NOTE : @vrielink_2020.md * PUSH NOTE : @adobeworkfront_2022.md * PUSH NOTE : @agilescrumgroup_2017.md * PUSH NOTE : @scrumguide_2022a.md * PUSH NOTE : @wikipedia_2023.md * PUSH NOTE : @leaninfo_2024.md --- content/004 Kwaliteitsmanagement.md | 2 +- content/007 Agile Projectmanagement.md | 5 +- content/References/@adobeworkfront_2022.md | 62 ++++----- content/References/@agilescrumgroup_2017.md | 58 ++++---- content/References/@agilescrumgroup_2018.md | 58 ++++---- content/References/@beljaars_2020.md | 84 ++++++------ content/References/@cspo_2021.md | 100 +++++++------- .../@governmentofwesternaustralia_2017.md | 64 ++++----- content/References/@hogeschoolpxl_2024.md | 80 +++++------ content/References/@leaninfo_2024.md | 84 ++++++------ content/References/@martin_2020.md | 66 +++++----- content/References/@productplan_2022.md | 66 +++++----- content/References/@qframe_2021.md | 70 +++++----- content/References/@raghuprasad_2019.md | 68 +++++----- content/References/@scrumguide_2022.md | 60 ++++----- content/References/@scrumguide_2022a.md | 60 ++++----- content/References/@sickipedia_2021.md | 78 +++++------ content/References/@stanley.etal_2020.md | 64 ++++----- content/References/@stefanowicz_2024.md | 84 ++++++------ content/References/@userstorymap_2022.md | 68 +++++----- content/References/@vanderwardt_2017.md | 68 +++++----- content/References/@vanlier_2018.md | 60 ++++----- content/References/@vanrooden_2015.md | 70 +++++----- content/References/@vanrooden_2015a.md | 72 +++++----- content/References/@verheyen_2022.md | 68 +++++----- content/References/@visual-paradigm_2022.md | 60 ++++----- content/References/@visualparadigm_2022.md | 52 ++++---- content/References/@vrielink_2020.md | 58 ++++---- content/References/@wikipedia_2023.md | 124 +++++++++--------- .../@wikipediakwaliteitsmanagement_2020.md | 70 +++++----- content/References/@zentaoteam_2022a.md | 58 ++++---- 31 files changed, 1021 insertions(+), 1020 deletions(-) diff --git a/content/004 Kwaliteitsmanagement.md b/content/004 Kwaliteitsmanagement.md index 796f7549..cc6961eb 100644 --- a/content/004 Kwaliteitsmanagement.md +++ b/content/004 Kwaliteitsmanagement.md @@ -427,7 +427,7 @@ Bijvoorbeeld: ![](https://i.imgur.com/LpiyWXB.png) -#### Oefeningen +### Oefeningen **Oefening 1:** diff --git a/content/007 Agile Projectmanagement.md b/content/007 Agile Projectmanagement.md index 5bc4c798..5de9de6f 100644 --- a/content/007 Agile Projectmanagement.md +++ b/content/007 Agile Projectmanagement.md @@ -138,7 +138,7 @@ Scrum is gebaseerd op een simpel idee: we leren het beste door dingen te doen en In Scrum gebruiken we drie belangrijke principes om dit in de praktijk te brengen: -- T**ransparantie:** Iedereen ziet wat er gebeurt +- **Transparantie:** Iedereen ziet wat er gebeurt - We zijn eerlijk over hoe het werk vordert. - We verbergen geen problemen of uitdagingen. - Iedereen in het team weet wat er gaande is. @@ -180,6 +180,7 @@ Scrum is gebaseerd op vijf kernwaarden die essentieel zijn voor effectieve samen - We committeren ons aan het team en de Sprint doelen, niet aan specifieke oplossingen. - We streven naar kwaliteit en blijven leren. - We zijn toegewijd aan continue verbetering. + ### Focus - We concentreren ons op wat nu het belangrijkst is voor de Sprint en productdoelen. @@ -607,7 +608,7 @@ De dagelijkse meetings voor de werknemers die aan een project samenwerken noemen Daily Standups helpen te verzekeren dat mogelijke belemmeringen (zie het stuk over [[007 Agile Projectmanagement#Obstakel|Obstakel]]) om je werk af te ronden snel geïdentificeerd en vlot weggewerkt raken. > [!example] VOORBEELD: Daily Standup -> Stel je voor dat je in een fastfoodrestaurant werkt. Elke shift begint met een korte standup van 15 minuten. Iedereen vertelt wat ze gisteren hebben gedaan, wat ze vandaag gaan doen, en of er obstakels zijn. Bijvoorbeeld: "Gisteren heb ik de friteuses schoongemaakt, vandaag ga ik de voorraad bijvullen, en ik merk dat we bijna door de hamburgerbroodjes heen zijn." +> Stel je voor dat je in een fastfoodrestaurant werkt. Elke shift begint met een korte standup van 15 minuten. Iedereen vertelt wat ze gisteren hebben gedaan, wat ze vandaag gaan doen, en of er obstakels zijn. Bijvoorbeeld: "Gisteren heb ik de frietketels schoongemaakt, vandaag ga ik de voorraad bijvullen, en ik merk dat we bijna door de hamburgerbroodjes heen zijn." ### Sprint Review diff --git a/content/References/@adobeworkfront_2022.md b/content/References/@adobeworkfront_2022.md index 52aee6c1..2467189e 100644 --- a/content/References/@adobeworkfront_2022.md +++ b/content/References/@adobeworkfront_2022.md @@ -6,34 +6,34 @@ authors: Adobe Workfront, year: 2022 url: https://www.workfront.com/project-management/methodologies/agile/velocity --- - -# What is Velocity in Agile? Charts & Examples | Adobe Workfront - - -> [!info] Metadata -> - **CiteKey**: adobeworkfront_2022 -> - **Type**: webpage -> - **Title**: What is Velocity in Agile? Charts & Examples | Adobe Workfront, -> - **Author**: Adobe Workfront, -> - **Year**: 2022 - -> [!abstract] Files and Links -> - **Url**: [https://www.workfront.com/project-management/methodologies/agile/velocity](https://www.workfront.com/project-management/methodologies/agile/velocity) -> - **Uri**: [http://zotero.org/groups/4724240/items/2JIMBRUM](http://zotero.org/groups/4724240/items/2JIMBRUM) -> - **Uri**: [http://zotero.org/users/9685140/items/7ATEI54D](http://zotero.org/users/9685140/items/7ATEI54D) -> - **File**: [What is Velocity in Agile? Charts & Examples | Adobe Workfront](file:///Users/jan/Zotero/storage/EACPRE9L/velocity.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/7ATEI54D)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# What is Velocity in Agile? Charts & Examples | Adobe Workfront + + +> [!info] Metadata +> - **CiteKey**: adobeworkfront_2022 +> - **Type**: webpage +> - **Title**: What is Velocity in Agile? Charts & Examples | Adobe Workfront, +> - **Author**: Adobe Workfront, +> - **Year**: 2022 + +> [!abstract] Files and Links +> - **Url**: [https://www.workfront.com/project-management/methodologies/agile/velocity](https://www.workfront.com/project-management/methodologies/agile/velocity) +> - **Uri**: [http://zotero.org/groups/4724240/items/2JIMBRUM](http://zotero.org/groups/4724240/items/2JIMBRUM) +> - **Uri**: [http://zotero.org/users/9685140/items/7ATEI54D](http://zotero.org/users/9685140/items/7ATEI54D) +> - **File**: [What is Velocity in Agile? Charts & Examples | Adobe Workfront](file:///Users/jan/Zotero/storage/EACPRE9L/velocity.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/7ATEI54D)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@agilescrumgroup_2017.md b/content/References/@agilescrumgroup_2017.md index e2841a6e..1d282e15 100644 --- a/content/References/@agilescrumgroup_2017.md +++ b/content/References/@agilescrumgroup_2017.md @@ -6,32 +6,32 @@ authors: Agile Scrum Group, year: 2017 url: https://agilescrumgroup.nl/wat-is-definition-of-done/ --- - -# Wat is Definition of Done? Check de uitleg en voorbeelden (IT & non-IT) - -> [!info] Metadata -> - **CiteKey**: agilescrumgroup_2017 -> - **Type**: blogPost -> - **Title**: Wat is Definition of Done? Check de uitleg en voorbeelden (IT & non-IT), -> - **Author**: Agile Scrum Group, -> - **Journal**: Agile Scrum Group -> - **Year**: 2017 - -> [!quote] Abstract -> In dit artikel lees je wat een Definition of Done is en worden voorbeelden gegeven. Zowel voor IT Scrumteams als non-IT Scrumteams. - -> [!abstract] Files and Links -> - **Url**: [https://agilescrumgroup.nl/wat-is-definition-of-done/](https://agilescrumgroup.nl/wat-is-definition-of-done/) -> - **Uri**: [http://zotero.org/groups/4724240/items/RNZLMPBC](http://zotero.org/groups/4724240/items/RNZLMPBC) -> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/RNZLMPBC)) - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Wat is Definition of Done? Check de uitleg en voorbeelden (IT & non-IT) + +> [!info] Metadata +> - **CiteKey**: agilescrumgroup_2017 +> - **Type**: blogPost +> - **Title**: Wat is Definition of Done? Check de uitleg en voorbeelden (IT & non-IT), +> - **Author**: Agile Scrum Group, +> - **Journal**: Agile Scrum Group +> - **Year**: 2017 + +> [!quote] Abstract +> In dit artikel lees je wat een Definition of Done is en worden voorbeelden gegeven. Zowel voor IT Scrumteams als non-IT Scrumteams. + +> [!abstract] Files and Links +> - **Url**: [https://agilescrumgroup.nl/wat-is-definition-of-done/](https://agilescrumgroup.nl/wat-is-definition-of-done/) +> - **Uri**: [http://zotero.org/groups/4724240/items/RNZLMPBC](http://zotero.org/groups/4724240/items/RNZLMPBC) +> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/RNZLMPBC)) + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@agilescrumgroup_2018.md b/content/References/@agilescrumgroup_2018.md index dce9efdb..a850048e 100644 --- a/content/References/@agilescrumgroup_2018.md +++ b/content/References/@agilescrumgroup_2018.md @@ -6,32 +6,32 @@ authors: Agile Scrum Group, year: 2018 url: https://agilescrumgroup.nl/sprint-review/ --- - -# De Sprint Review uitgelegd. Waarom deze meeting? (+ Checklist & Valkuilen) - -> [!info] Metadata -> - **CiteKey**: agilescrumgroup_2018 -> - **Type**: blogPost -> - **Title**: De Sprint Review uitgelegd. Waarom deze meeting? (+ Checklist & Valkuilen), -> - **Author**: Agile Scrum Group, -> - **Journal**: Agile Scrum Group -> - **Year**: 2018 - -> [!quote] Abstract -> Wat is de Sprint Review? Waarom is deze meeting belangrijk? Wat zijn valkuilen voor deze meeting? Lees alles hierover in deze blog. - -> [!abstract] Files and Links -> - **Url**: [https://agilescrumgroup.nl/sprint-review/](https://agilescrumgroup.nl/sprint-review/) -> - **Uri**: [http://zotero.org/groups/4724240/items/CRVEWZAV](http://zotero.org/groups/4724240/items/CRVEWZAV) -> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/CRVEWZAV)) - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# De Sprint Review uitgelegd. Waarom deze meeting? (+ Checklist & Valkuilen) + +> [!info] Metadata +> - **CiteKey**: agilescrumgroup_2018 +> - **Type**: blogPost +> - **Title**: De Sprint Review uitgelegd. Waarom deze meeting? (+ Checklist & Valkuilen), +> - **Author**: Agile Scrum Group, +> - **Journal**: Agile Scrum Group +> - **Year**: 2018 + +> [!quote] Abstract +> Wat is de Sprint Review? Waarom is deze meeting belangrijk? Wat zijn valkuilen voor deze meeting? Lees alles hierover in deze blog. + +> [!abstract] Files and Links +> - **Url**: [https://agilescrumgroup.nl/sprint-review/](https://agilescrumgroup.nl/sprint-review/) +> - **Uri**: [http://zotero.org/groups/4724240/items/CRVEWZAV](http://zotero.org/groups/4724240/items/CRVEWZAV) +> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/CRVEWZAV)) + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@beljaars_2020.md b/content/References/@beljaars_2020.md index 9067f036..a58b5bd4 100644 --- a/content/References/@beljaars_2020.md +++ b/content/References/@beljaars_2020.md @@ -10,45 +10,45 @@ year: "2020" url: https://www.agile4all.nl/wat-is-een-affiniteitsdiagram/ authors: " Beljaars, Peter" --- - -> [!Cite] -> Beljaars, P. (2020, November 9). _Wat is een affiniteitsdiagram?_ agile4all. [https://www.agile4all.nl/wat-is-een-affiniteitsdiagram/](https://www.agile4all.nl/wat-is-een-affiniteitsdiagram/) - - ---- - -# Metadata - ->[!Properties] -> **FirstAuthor** Beljaars, Peter -~ -> **Title** Wat is een affiniteitsdiagram? -> **Year** 2020 -> **Citekey** beljaars_2020 -> **itemType** webpage - -> [!LINK] -> - -> [!Abstract] -> -> Een affiniteitsdiagram is een hulpmiddel om gegevens te verkrijgen, ordenen en te beoordelen door het creëren van categorieën. ->. -> -# Notes - ->> - - -# Annotations -_annotations in the paper_. -### Highlights - - - -### Notes - - - -### Images - + +> [!Cite] +> Beljaars, P. (2020, November 9). _Wat is een affiniteitsdiagram?_ agile4all. [https://www.agile4all.nl/wat-is-een-affiniteitsdiagram/](https://www.agile4all.nl/wat-is-een-affiniteitsdiagram/) + + +--- + +# Metadata + +>[!Properties] +> **FirstAuthor** Beljaars, Peter +~ +> **Title** Wat is een affiniteitsdiagram? +> **Year** 2020 +> **Citekey** beljaars_2020 +> **itemType** webpage + +> [!LINK] +> + +> [!Abstract] +> +> Een affiniteitsdiagram is een hulpmiddel om gegevens te verkrijgen, ordenen en te beoordelen door het creëren van categorieën. +>. +> +# Notes + +>> + + +# Annotations +_annotations in the paper_. +### Highlights + + + +### Notes + + + +### Images + diff --git a/content/References/@cspo_2021.md b/content/References/@cspo_2021.md index b389e147..7b001269 100644 --- a/content/References/@cspo_2021.md +++ b/content/References/@cspo_2021.md @@ -6,53 +6,53 @@ authors: CSPO, Erin Aldridge, PMP, PMI-ACP, & year: 2021 url: https://projectmanagementacademy.net/resources/blog/quality-vs-grade-pmp-guide/ --- - -# Quality vs. Grade for PMP - -> [!info] Metadata -> - **CiteKey**: cspo_2021 -> - **Type**: blogPost -> - **Title**: Quality vs. Grade for PMP, -> - **Author**: CSPO, Erin Aldridge, PMP, PMI-ACP, & -> - **Journal**: Project Management Academy Resources -> - **Year**: 2021 - -> [!quote] Abstract -> The terms “quality” and “grade” are often used interchangeably. PMPs must understand the differences in quality vs grade for PMP. - -> [!abstract] Files and Links -> - **Url**: [https://projectmanagementacademy.net/resources/blog/quality-vs-grade-pmp-guide/](https://projectmanagementacademy.net/resources/blog/quality-vs-grade-pmp-guide/) -> - **Uri**: [http://zotero.org/groups/4724240/items/TF8VEDUG](http://zotero.org/groups/4724240/items/TF8VEDUG) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/Q2KC9BN2/quality-vs-grade-pmp-guide.html) -> - **Uri**: [http://zotero.org/users/9685140/items/457476SE](http://zotero.org/users/9685140/items/457476SE) -> - **File**: [Snapshot](file://C:%5CUsers%5C20003936%5CZotero%5Cstorage%5C6PNDHRRP%5Cquality-vs-grade-pmp-guide.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/457476SE)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments -It is crucial to understand the difference between quality vs. grade for the PMP exam. You should understand their definitions, the high and low variants, and how they interact with each other. Let’s start by taking a look at them separately: - -* **Quality**: measures how closely a deliverable meets expectations and functions as intended. It’s necessary to consider if there are any defects or performance errors. - - * High quality: the deliverable matches its expected specifications. There are no defects, and it functions correctly. - * Low quality: the deliverable does not fulfill requirements. It has defects or does not work well or at all. -* **Grade**: categorizes desired features or characteristics of a deliverable. It can be understood as a measure of what a customer values in a product. - - * High grade: many valuable or desired features. - * Low grade: limited or undesirable features. -There are four possible combinations when looking at a product or deliverable-based on quality and grade. At Project Management Academy, we like to use the example of a burger to explain the differences between these combinations for the PMP exam. - -* **High quality, high grade:** this is the type of burger you might find at a five-star restaurant. It’s cooked correctly and safe to eat (high quality), and it uses a high grade of meat and other ingredients that make it desirable – and often pretty expensive (high grade). -* **High quality, low grade:** you can get this type of burger at a fast-food restaurant. It’s still cooked correctly and safe to eat (high quality), but it might use low-grade meat or have unhealthy ingredients that make it less desirable (low grade). -* **Low quality, high grade**: imagine you ordered a burger at a nice restaurant that you know uses good ingredients (high grade). However, the burger arrives burnt and inedible! Although the grade is high, the quality is low. -* **Low quality, low grade**: have you ever gotten a fast-food burger and bitten into a cold patty or burnt rock? That’s a low-quality AND low-grade burger. - - ----- - -## Extracted Annotations - + +# Quality vs. Grade for PMP + +> [!info] Metadata +> - **CiteKey**: cspo_2021 +> - **Type**: blogPost +> - **Title**: Quality vs. Grade for PMP, +> - **Author**: CSPO, Erin Aldridge, PMP, PMI-ACP, & +> - **Journal**: Project Management Academy Resources +> - **Year**: 2021 + +> [!quote] Abstract +> The terms “quality” and “grade” are often used interchangeably. PMPs must understand the differences in quality vs grade for PMP. + +> [!abstract] Files and Links +> - **Url**: [https://projectmanagementacademy.net/resources/blog/quality-vs-grade-pmp-guide/](https://projectmanagementacademy.net/resources/blog/quality-vs-grade-pmp-guide/) +> - **Uri**: [http://zotero.org/groups/4724240/items/TF8VEDUG](http://zotero.org/groups/4724240/items/TF8VEDUG) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/Q2KC9BN2/quality-vs-grade-pmp-guide.html) +> - **Uri**: [http://zotero.org/users/9685140/items/457476SE](http://zotero.org/users/9685140/items/457476SE) +> - **File**: [Snapshot](file://C:%5CUsers%5C20003936%5CZotero%5Cstorage%5C6PNDHRRP%5Cquality-vs-grade-pmp-guide.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/457476SE)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments +It is crucial to understand the difference between quality vs. grade for the PMP exam. You should understand their definitions, the high and low variants, and how they interact with each other. Let’s start by taking a look at them separately: + +* **Quality**: measures how closely a deliverable meets expectations and functions as intended. It’s necessary to consider if there are any defects or performance errors. + + * High quality: the deliverable matches its expected specifications. There are no defects, and it functions correctly. + * Low quality: the deliverable does not fulfill requirements. It has defects or does not work well or at all. +* **Grade**: categorizes desired features or characteristics of a deliverable. It can be understood as a measure of what a customer values in a product. + + * High grade: many valuable or desired features. + * Low grade: limited or undesirable features. +There are four possible combinations when looking at a product or deliverable-based on quality and grade. At Project Management Academy, we like to use the example of a burger to explain the differences between these combinations for the PMP exam. + +* **High quality, high grade:** this is the type of burger you might find at a five-star restaurant. It’s cooked correctly and safe to eat (high quality), and it uses a high grade of meat and other ingredients that make it desirable – and often pretty expensive (high grade). +* **High quality, low grade:** you can get this type of burger at a fast-food restaurant. It’s still cooked correctly and safe to eat (high quality), but it might use low-grade meat or have unhealthy ingredients that make it less desirable (low grade). +* **Low quality, high grade**: imagine you ordered a burger at a nice restaurant that you know uses good ingredients (high grade). However, the burger arrives burnt and inedible! Although the grade is high, the quality is low. +* **Low quality, low grade**: have you ever gotten a fast-food burger and bitten into a cold patty or burnt rock? That’s a low-quality AND low-grade burger. + + +---- + +## Extracted Annotations + diff --git a/content/References/@governmentofwesternaustralia_2017.md b/content/References/@governmentofwesternaustralia_2017.md index 5c430795..a79609bf 100644 --- a/content/References/@governmentofwesternaustralia_2017.md +++ b/content/References/@governmentofwesternaustralia_2017.md @@ -6,35 +6,35 @@ authors: Government of Western Australia, year: 2017 url: https://www.agric.wa.gov.au/improvement-tools-critical-success-factors-and-key-performance-indicators --- - -# Improvement tools: Critical success factors and key performance indicators - -> [!info] Metadata -> - **CiteKey**: governmentofwesternaustralia_2017 -> - **Type**: webpage -> - **Title**: Improvement tools: Critical success factors and key performance indicators, -> - **Author**: Government of Western Australia, -> - **Year**: 2017 - -> [!quote] Abstract -> In any business there are a number of things that have to be in place and working well if the business is to achieve its goals. These are the critical success factors (CSFs). There might be many day to day tasks that need to be done. But if the CSFs are missing or underperforming, the goals will not be achieved. Key performance indicators (KPIs) are the way to measure whether the CSFs are working. Using CSFs and KPIs helps a business stay focused on the key actions that will keep it on track to achieving its goals. - -> [!abstract] Files and Links -> - **Url**: [https://www.agric.wa.gov.au/improvement-tools-critical-success-factors-and-key-performance-indicators](https://www.agric.wa.gov.au/improvement-tools-critical-success-factors-and-key-performance-indicators) -> - **Uri**: [http://zotero.org/users/9685140/items/GKZ8D8K6](http://zotero.org/users/9685140/items/GKZ8D8K6) -> - **File**: [Snapshot](file://C:%5CUsers%5C20003936%5CZotero%5Cstorage%5CLBAR7W6K%5Cimprovement-tools-critical-success-factors-and-key-performance-indicators.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/GKZ8D8K6)) - -> [!note] Tags and Collections - - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Improvement tools: Critical success factors and key performance indicators + +> [!info] Metadata +> - **CiteKey**: governmentofwesternaustralia_2017 +> - **Type**: webpage +> - **Title**: Improvement tools: Critical success factors and key performance indicators, +> - **Author**: Government of Western Australia, +> - **Year**: 2017 + +> [!quote] Abstract +> In any business there are a number of things that have to be in place and working well if the business is to achieve its goals. These are the critical success factors (CSFs). There might be many day to day tasks that need to be done. But if the CSFs are missing or underperforming, the goals will not be achieved. Key performance indicators (KPIs) are the way to measure whether the CSFs are working. Using CSFs and KPIs helps a business stay focused on the key actions that will keep it on track to achieving its goals. + +> [!abstract] Files and Links +> - **Url**: [https://www.agric.wa.gov.au/improvement-tools-critical-success-factors-and-key-performance-indicators](https://www.agric.wa.gov.au/improvement-tools-critical-success-factors-and-key-performance-indicators) +> - **Uri**: [http://zotero.org/users/9685140/items/GKZ8D8K6](http://zotero.org/users/9685140/items/GKZ8D8K6) +> - **File**: [Snapshot](file://C:%5CUsers%5C20003936%5CZotero%5Cstorage%5CLBAR7W6K%5Cimprovement-tools-critical-success-factors-and-key-performance-indicators.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/GKZ8D8K6)) + +> [!note] Tags and Collections + + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@hogeschoolpxl_2024.md b/content/References/@hogeschoolpxl_2024.md index 9af1c8d9..025d8bb5 100644 --- a/content/References/@hogeschoolpxl_2024.md +++ b/content/References/@hogeschoolpxl_2024.md @@ -10,43 +10,43 @@ year: "2024" url: https://www.pxl.be/Pub/Over-PXL/Kwaliteitszorg.html authors: " Hogeschool PXL, " --- - -> [!Cite] -> Hogeschool PXL. (2024). _Kwaliteitszorg_. [https://www.pxl.be/Pub/Over-PXL/Kwaliteitszorg.html](https://www.pxl.be/Pub/Over-PXL/Kwaliteitszorg.html) - - ---- - -# Metadata - ->[!Properties] -> **FirstAuthor** Hogeschool PXL, -~ -> **Title** Kwaliteitszorg -> **Year** 2024 -> **Citekey** hogeschoolpxl_2024 -> **itemType** webpage - -> [!LINK] -> - -> [!Abstract] ->. -> -# Notes - ->> - - -# Annotations -_annotations in the paper_. -### Highlights - - - -### Notes - - - -### Images - + +> [!Cite] +> Hogeschool PXL. (2024). _Kwaliteitszorg_. [https://www.pxl.be/Pub/Over-PXL/Kwaliteitszorg.html](https://www.pxl.be/Pub/Over-PXL/Kwaliteitszorg.html) + + +--- + +# Metadata + +>[!Properties] +> **FirstAuthor** Hogeschool PXL, +~ +> **Title** Kwaliteitszorg +> **Year** 2024 +> **Citekey** hogeschoolpxl_2024 +> **itemType** webpage + +> [!LINK] +> + +> [!Abstract] +>. +> +# Notes + +>> + + +# Annotations +_annotations in the paper_. +### Highlights + + + +### Notes + + + +### Images + diff --git a/content/References/@leaninfo_2024.md b/content/References/@leaninfo_2024.md index d831eb3b..6ec6e3a4 100644 --- a/content/References/@leaninfo_2024.md +++ b/content/References/@leaninfo_2024.md @@ -10,45 +10,45 @@ year: "2024" url: https://www.leaninfo.nl/stroomdiagram/ authors: " Leaninfo" --- - -> [!Cite] -> Leaninfo. (2024). Stroomdiagram—Een flowchart maakt uw proces inzichtelijk | LeanInfo.nl. _Leaninfo_. [https://www.leaninfo.nl/stroomdiagram/](https://www.leaninfo.nl/stroomdiagram/) - - ---- - -# Metadata - ->[!Properties] -> **FirstAuthor** Leaninfo -~ -> **Title** Stroomdiagram - Een flowchart maakt uw proces inzichtelijk | LeanInfo.nl -> **Year** 2024 -> **Citekey** leaninfo_2024 -> **itemType** blogPost - -> [!LINK] -> - -> [!Abstract] -> -> Een stroomdiagram (flowchart) kan worden gebruikt om de invulling van verschillende deelprocessen en processtappen inzichtelijk te maken. Lees snel meer! ->. -> -# Notes - ->> - - -# Annotations -_annotations in the paper_. -### Highlights - - - -### Notes - - - -### Images - + +> [!Cite] +> Leaninfo. (2024). Stroomdiagram—Een flowchart maakt uw proces inzichtelijk | LeanInfo.nl. _Leaninfo_. [https://www.leaninfo.nl/stroomdiagram/](https://www.leaninfo.nl/stroomdiagram/) + + +--- + +# Metadata + +>[!Properties] +> **FirstAuthor** Leaninfo +~ +> **Title** Stroomdiagram - Een flowchart maakt uw proces inzichtelijk | LeanInfo.nl +> **Year** 2024 +> **Citekey** leaninfo_2024 +> **itemType** blogPost + +> [!LINK] +> + +> [!Abstract] +> +> Een stroomdiagram (flowchart) kan worden gebruikt om de invulling van verschillende deelprocessen en processtappen inzichtelijk te maken. Lees snel meer! +>. +> +# Notes + +>> + + +# Annotations +_annotations in the paper_. +### Highlights + + + +### Notes + + + +### Images + diff --git a/content/References/@martin_2020.md b/content/References/@martin_2020.md index f55b2002..45d17ade 100644 --- a/content/References/@martin_2020.md +++ b/content/References/@martin_2020.md @@ -6,36 +6,36 @@ authors: Martin, Matthew year: 2020 url: https://www.guru99.com/what-is-incremental-model-in-sdlc-advantages-disadvantages.html --- - -# Incremental Model in SDLC: Use, Advantage & Disadvantage - -> [!info] Metadata -> - **CiteKey**: martin_2020 -> - **Type**: webpage -> - **Title**: Incremental Model in SDLC: Use, Advantage & Disadvantage, -> - **Author**: Martin, Matthew -> - **Year**: 2020 - -> [!quote] Abstract -> Incremental Methodology is a process of software engineering development where requrements are broken down into multiple standalone modules of software development cycle. Incremental development is done in steps from analysis design, implementation, testing/verification, maintenance. - -> [!abstract] Files and Links -> - **Url**: [https://www.guru99.com/what-is-incremental-model-in-sdlc-advantages-disadvantages.html](https://www.guru99.com/what-is-incremental-model-in-sdlc-advantages-disadvantages.html) -> - **Uri**: [http://zotero.org/groups/4724240/items/X24LCQFB](http://zotero.org/groups/4724240/items/X24LCQFB) -> - **Uri**: [http://zotero.org/users/9685140/items/DL9DZNFE](http://zotero.org/users/9685140/items/DL9DZNFE) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/JPNWMVUN/what-is-incremental-model-in-sdlc-advantages-disadvantages.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/DL9DZNFE)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Incremental Model in SDLC: Use, Advantage & Disadvantage + +> [!info] Metadata +> - **CiteKey**: martin_2020 +> - **Type**: webpage +> - **Title**: Incremental Model in SDLC: Use, Advantage & Disadvantage, +> - **Author**: Martin, Matthew +> - **Year**: 2020 + +> [!quote] Abstract +> Incremental Methodology is a process of software engineering development where requrements are broken down into multiple standalone modules of software development cycle. Incremental development is done in steps from analysis design, implementation, testing/verification, maintenance. + +> [!abstract] Files and Links +> - **Url**: [https://www.guru99.com/what-is-incremental-model-in-sdlc-advantages-disadvantages.html](https://www.guru99.com/what-is-incremental-model-in-sdlc-advantages-disadvantages.html) +> - **Uri**: [http://zotero.org/groups/4724240/items/X24LCQFB](http://zotero.org/groups/4724240/items/X24LCQFB) +> - **Uri**: [http://zotero.org/users/9685140/items/DL9DZNFE](http://zotero.org/users/9685140/items/DL9DZNFE) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/JPNWMVUN/what-is-incremental-model-in-sdlc-advantages-disadvantages.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/DL9DZNFE)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@productplan_2022.md b/content/References/@productplan_2022.md index 7a2d1fd3..c26f1aa1 100644 --- a/content/References/@productplan_2022.md +++ b/content/References/@productplan_2022.md @@ -6,36 +6,36 @@ authors: productplan, year: 2022 url: https://www.productplan.com/glossary/user-story/ --- - -# User Story - -> [!info] Metadata -> - **CiteKey**: productplan_2022 -> - **Type**: webpage -> - **Title**: User Story, -> - **Author**: productplan, -> - **Year**: 2022 - -> [!quote] Abstract -> What is a user story and who is responsible for them? Learn how to write user stories—plus get a free user story template. - -> [!abstract] Files and Links -> - **Url**: [https://www.productplan.com/glossary/user-story/](https://www.productplan.com/glossary/user-story/) -> - **Uri**: [http://zotero.org/groups/4724240/items/63BX82J2](http://zotero.org/groups/4724240/items/63BX82J2) -> - **Uri**: [http://zotero.org/users/9685140/items/DG75SWYS](http://zotero.org/users/9685140/items/DG75SWYS) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/RXGJPTQF/user-story.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/DG75SWYS)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# User Story + +> [!info] Metadata +> - **CiteKey**: productplan_2022 +> - **Type**: webpage +> - **Title**: User Story, +> - **Author**: productplan, +> - **Year**: 2022 + +> [!quote] Abstract +> What is a user story and who is responsible for them? Learn how to write user stories—plus get a free user story template. + +> [!abstract] Files and Links +> - **Url**: [https://www.productplan.com/glossary/user-story/](https://www.productplan.com/glossary/user-story/) +> - **Uri**: [http://zotero.org/groups/4724240/items/63BX82J2](http://zotero.org/groups/4724240/items/63BX82J2) +> - **Uri**: [http://zotero.org/users/9685140/items/DG75SWYS](http://zotero.org/users/9685140/items/DG75SWYS) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/RXGJPTQF/user-story.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/DG75SWYS)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@qframe_2021.md b/content/References/@qframe_2021.md index ffdad7b0..f9305ce5 100644 --- a/content/References/@qframe_2021.md +++ b/content/References/@qframe_2021.md @@ -6,38 +6,38 @@ authors: qframe, year: 2021 url: https://qframe.be/2021/06/25/scrum-master-teambuilder-of-agile-coach/ --- - -# Scrum Master, Teambuilder of Agile Coach? - -> [!info] Metadata -> - **CiteKey**: qframe_2021 -> - **Type**: webpage -> - **Title**: Scrum Master, Teambuilder of Agile Coach?, -> - **Author**: qframe, -> - **Journal**: Qframe -> - **Year**: 2021 - -> [!quote] Abstract -> Onze kijk op de rol van Scrum Master binnen onze software teams. Een 7-tal jaar geleden evolueerden wij van een IT-bodyshopping bedrijf naar een bedrijf met een TaaS aanpak ofte ‘team as a service’. Die switch kwam natuurlijk niet zomaar uit de lucht vallen. Een aantal negatieve ervaringen uit het verleden gecombineerd met onze nooit… - -> [!abstract] Files and Links -> - **Url**: [https://qframe.be/2021/06/25/scrum-master-teambuilder-of-agile-coach/](https://qframe.be/2021/06/25/scrum-master-teambuilder-of-agile-coach/) -> - **Uri**: [http://zotero.org/groups/4724240/items/HDIVHHPZ](http://zotero.org/groups/4724240/items/HDIVHHPZ) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/H6GDPNX2/scrum-master-teambuilder-of-agile-coach.html) -> - **Uri**: [http://zotero.org/users/9685140/items/62GKHLZF](http://zotero.org/users/9685140/items/62GKHLZF) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/NQPJ85QZ/scrum-master-teambuilder-of-agile-coach.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/62GKHLZF)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Scrum Master, Teambuilder of Agile Coach? + +> [!info] Metadata +> - **CiteKey**: qframe_2021 +> - **Type**: webpage +> - **Title**: Scrum Master, Teambuilder of Agile Coach?, +> - **Author**: qframe, +> - **Journal**: Qframe +> - **Year**: 2021 + +> [!quote] Abstract +> Onze kijk op de rol van Scrum Master binnen onze software teams. Een 7-tal jaar geleden evolueerden wij van een IT-bodyshopping bedrijf naar een bedrijf met een TaaS aanpak ofte ‘team as a service’. Die switch kwam natuurlijk niet zomaar uit de lucht vallen. Een aantal negatieve ervaringen uit het verleden gecombineerd met onze nooit… + +> [!abstract] Files and Links +> - **Url**: [https://qframe.be/2021/06/25/scrum-master-teambuilder-of-agile-coach/](https://qframe.be/2021/06/25/scrum-master-teambuilder-of-agile-coach/) +> - **Uri**: [http://zotero.org/groups/4724240/items/HDIVHHPZ](http://zotero.org/groups/4724240/items/HDIVHHPZ) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/H6GDPNX2/scrum-master-teambuilder-of-agile-coach.html) +> - **Uri**: [http://zotero.org/users/9685140/items/62GKHLZF](http://zotero.org/users/9685140/items/62GKHLZF) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/NQPJ85QZ/scrum-master-teambuilder-of-agile-coach.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/62GKHLZF)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@raghuprasad_2019.md b/content/References/@raghuprasad_2019.md index aa0a85cc..9987eca9 100644 --- a/content/References/@raghuprasad_2019.md +++ b/content/References/@raghuprasad_2019.md @@ -6,37 +6,37 @@ authors: Raghuprasad, year: 2019 url: https://agilebatech.com/what-is-sprint-planning/ --- - -# Basics of Sprint Planning - WHAT - -> [!info] Metadata -> - **CiteKey**: raghuprasad_2019 -> - **Type**: blogPost -> - **Title**: Basics of Sprint Planning - WHAT, -> - **Author**: Raghuprasad, -> - **Journal**: AgileBAtech -> - **Year**: 2019 - -> [!quote] Abstract -> Sprint Planning is held on the first day of the Sprint. This key Scrum event is designed to provide the Team and the Product Owner an opportunity to - -> [!abstract] Files and Links -> - **Url**: [https://agilebatech.com/what-is-sprint-planning/](https://agilebatech.com/what-is-sprint-planning/) -> - **Uri**: [http://zotero.org/groups/4724240/items/UWDYWUEF](http://zotero.org/groups/4724240/items/UWDYWUEF) -> - **Uri**: [http://zotero.org/users/9685140/items/D47QT5F5](http://zotero.org/users/9685140/items/D47QT5F5) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/HMHENKD8/what-is-sprint-planning.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/D47QT5F5)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Basics of Sprint Planning - WHAT + +> [!info] Metadata +> - **CiteKey**: raghuprasad_2019 +> - **Type**: blogPost +> - **Title**: Basics of Sprint Planning - WHAT, +> - **Author**: Raghuprasad, +> - **Journal**: AgileBAtech +> - **Year**: 2019 + +> [!quote] Abstract +> Sprint Planning is held on the first day of the Sprint. This key Scrum event is designed to provide the Team and the Product Owner an opportunity to + +> [!abstract] Files and Links +> - **Url**: [https://agilebatech.com/what-is-sprint-planning/](https://agilebatech.com/what-is-sprint-planning/) +> - **Uri**: [http://zotero.org/groups/4724240/items/UWDYWUEF](http://zotero.org/groups/4724240/items/UWDYWUEF) +> - **Uri**: [http://zotero.org/users/9685140/items/D47QT5F5](http://zotero.org/users/9685140/items/D47QT5F5) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/HMHENKD8/what-is-sprint-planning.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/D47QT5F5)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@scrumguide_2022.md b/content/References/@scrumguide_2022.md index 8db0d267..e36cc0c5 100644 --- a/content/References/@scrumguide_2022.md +++ b/content/References/@scrumguide_2022.md @@ -6,33 +6,33 @@ authors: scrumguide, year: 2022 url: https://scrumguide.nl/scrumteam/ --- - -# Het Scrumteam: uitleg en tips bij de verantwoordelijkheid | Scrumguide.nl - -> [!info] Metadata -> - **CiteKey**: scrumguide_2022 -> - **Type**: blogPost -> - **Title**: Het Scrumteam: uitleg en tips bij de verantwoordelijkheid | Scrumguide.nl, -> - **Author**: scrumguide, -> - **Journal**: Scrumguide -> - **Year**: 2022 - -> [!quote] Abstract -> Het Scrumteam bestaat uit de professionals die werken aan uitvoerende projecttaken in een scrumproject. Het Scrum team gemakkelijk uitgelegd. - -> [!abstract] Files and Links -> - **Url**: [https://scrumguide.nl/scrumteam/](https://scrumguide.nl/scrumteam/) -> - **Uri**: [http://zotero.org/groups/4724240/items/P8EMVPDV](http://zotero.org/groups/4724240/items/P8EMVPDV) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/LMM58I4J/scrumteam.html) -> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/P8EMVPDV)) - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Het Scrumteam: uitleg en tips bij de verantwoordelijkheid | Scrumguide.nl + +> [!info] Metadata +> - **CiteKey**: scrumguide_2022 +> - **Type**: blogPost +> - **Title**: Het Scrumteam: uitleg en tips bij de verantwoordelijkheid | Scrumguide.nl, +> - **Author**: scrumguide, +> - **Journal**: Scrumguide +> - **Year**: 2022 + +> [!quote] Abstract +> Het Scrumteam bestaat uit de professionals die werken aan uitvoerende projecttaken in een scrumproject. Het Scrum team gemakkelijk uitgelegd. + +> [!abstract] Files and Links +> - **Url**: [https://scrumguide.nl/scrumteam/](https://scrumguide.nl/scrumteam/) +> - **Uri**: [http://zotero.org/groups/4724240/items/P8EMVPDV](http://zotero.org/groups/4724240/items/P8EMVPDV) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/LMM58I4J/scrumteam.html) +> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/P8EMVPDV)) + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@scrumguide_2022a.md b/content/References/@scrumguide_2022a.md index 47d688c8..2b51fcf3 100644 --- a/content/References/@scrumguide_2022a.md +++ b/content/References/@scrumguide_2022a.md @@ -6,33 +6,33 @@ authors: Scrumguide, year: 2022 url: https://scrumguide.nl/scrumbord/ --- - -# Scrum takenbord | Scrumguide.nl - -> [!info] Metadata -> - **CiteKey**: scrumguide_2022a -> - **Type**: blogPost -> - **Title**: Scrum takenbord | Scrumguide.nl, -> - **Author**: Scrumguide, -> - **Journal**: Scrumguide -> - **Year**: 2022 - -> [!quote] Abstract -> Het Scrum takenbord Binnen Scrum wordt gewerkt met een takenbord. Het Scrum takenbord is bedoeld als hulpmiddel bij het overzichtelijk maken van de stand van zaken binnen een sprint. Alle taken die voor een sprint geselecteerd zijn, worden opgenomen in de Sprint Backlog en hangen op post-its in één van de drie kolommen op het […] - -> [!abstract] Files and Links -> - **Url**: [https://scrumguide.nl/scrumbord/](https://scrumguide.nl/scrumbord/) -> - **Uri**: [http://zotero.org/groups/4724240/items/I4D8Q6VK](http://zotero.org/groups/4724240/items/I4D8Q6VK) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/XHK4QUE2/scrumbord.html) -> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/I4D8Q6VK)) - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Scrum takenbord | Scrumguide.nl + +> [!info] Metadata +> - **CiteKey**: scrumguide_2022a +> - **Type**: blogPost +> - **Title**: Scrum takenbord | Scrumguide.nl, +> - **Author**: Scrumguide, +> - **Journal**: Scrumguide +> - **Year**: 2022 + +> [!quote] Abstract +> Het Scrum takenbord Binnen Scrum wordt gewerkt met een takenbord. Het Scrum takenbord is bedoeld als hulpmiddel bij het overzichtelijk maken van de stand van zaken binnen een sprint. Alle taken die voor een sprint geselecteerd zijn, worden opgenomen in de Sprint Backlog en hangen op post-its in één van de drie kolommen op het […] + +> [!abstract] Files and Links +> - **Url**: [https://scrumguide.nl/scrumbord/](https://scrumguide.nl/scrumbord/) +> - **Uri**: [http://zotero.org/groups/4724240/items/I4D8Q6VK](http://zotero.org/groups/4724240/items/I4D8Q6VK) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/XHK4QUE2/scrumbord.html) +> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/I4D8Q6VK)) + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@sickipedia_2021.md b/content/References/@sickipedia_2021.md index 38a3b0c6..31f48145 100644 --- a/content/References/@sickipedia_2021.md +++ b/content/References/@sickipedia_2021.md @@ -6,42 +6,42 @@ authors: SICKipedia, year: 2021 url: https://cdn.sick.com/media/content/hcc/hdf/9692943974430.pdf --- - -# Het verschil tussen nauwkeurigheid en reproduceerbaarheid - -> [!info] Metadata -> - **CiteKey**: sickipedia_2021 -> - **Type**: document -> - **Title**: Het verschil tussen nauwkeurigheid en reproduceerbaarheid, -> - **Author**: SICKipedia,; -> - **Publisher**: SICK, -> - **Year**: 2021 - -> [!quote] Abstract -> veelal worden de begrippen nauwkeurigheid en precisie door elkaar gebruikt en worden ze als synoniemen beschouwd. deze twee termen hebben echter een verschillende betekenis. de nauwkeurigheid geeft aan hoe accuraat de meting is, ofwel hoe groot de afwijking is tussen de gemeten en werkelijke waarde. de precisie heeft betrekking op de spreiding van de gemeten waarden uit een serie metingen. - -> [!abstract] Files and Links -> - **Url**: [https://cdn.sick.com/media/content/hcc/hdf/9692943974430.pdf](https://cdn.sick.com/media/content/hcc/hdf/9692943974430.pdf) -> - **Uri**: [http://zotero.org/groups/4724240/items/48S8MBKN](http://zotero.org/groups/4724240/items/48S8MBKN) -> - **Uri**: [http://zotero.org/users/9685140/items/26CS97QK](http://zotero.org/users/9685140/items/26CS97QK) -> - **Url**: https://cdn.sick.com/media/content/hcc/hdf/9692943974430.pdf -> - **Uri**: http://zotero.org/users/9685140/items/26CS97QK -> - **File**: [SICKipedia - 2021 - Het verschil tussen nauwkeurigheid en reproduceerb.pdf](file://C:%5CUsers%5C20003936%5CZotero%5Cstorage%5CG3WI6V7R%5CSICKipedia%2520-%25202021%2520-%2520Het%2520verschil%2520tussen%2520nauwkeurigheid%2520en%2520reproduceerb.pdf) -> - **Local Library**: [Zotero]((zotero://select/library/items/26CS97QK)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations -Annotations(24/06/2022, 17:10:23) -- *“nauwkeurigheid of accuratesse is de graad van overeenstemming van een gemeten of berekende hoeveelheid met haar daadwerkelijke (ware) waarde. hoe groter de nauwkeurigheid, hoe kleiner de totale fout.”* [(SICKipedia, 2021, p. 1)](zotero://open-pdf/library/items/G3WI6V7R?page=1&annotation=ECLFRYYH) -- *“reproduceerbaarheid, herhaalnauwkeurigheid of precisie van een meting geeft, bij gelijke omstandigheden, aan hoe goed eenzelfde uitkomst wordt gehaald. bij afstandmeetsystemen wordt de maximale afwijking in mm aangegeven, waarmee een meting onder gelijke omstandigheden kan afwijken. reproduceerbaarheid is dus niet te verwarren met absolute nauwkeurigheid.”* [(SICKipedia, 2021, p. 1)](zotero://open-pdf/library/items/G3WI6V7R?page=1&annotation=INDJUSX9) - + +# Het verschil tussen nauwkeurigheid en reproduceerbaarheid + +> [!info] Metadata +> - **CiteKey**: sickipedia_2021 +> - **Type**: document +> - **Title**: Het verschil tussen nauwkeurigheid en reproduceerbaarheid, +> - **Author**: SICKipedia,; +> - **Publisher**: SICK, +> - **Year**: 2021 + +> [!quote] Abstract +> veelal worden de begrippen nauwkeurigheid en precisie door elkaar gebruikt en worden ze als synoniemen beschouwd. deze twee termen hebben echter een verschillende betekenis. de nauwkeurigheid geeft aan hoe accuraat de meting is, ofwel hoe groot de afwijking is tussen de gemeten en werkelijke waarde. de precisie heeft betrekking op de spreiding van de gemeten waarden uit een serie metingen. + +> [!abstract] Files and Links +> - **Url**: [https://cdn.sick.com/media/content/hcc/hdf/9692943974430.pdf](https://cdn.sick.com/media/content/hcc/hdf/9692943974430.pdf) +> - **Uri**: [http://zotero.org/groups/4724240/items/48S8MBKN](http://zotero.org/groups/4724240/items/48S8MBKN) +> - **Uri**: [http://zotero.org/users/9685140/items/26CS97QK](http://zotero.org/users/9685140/items/26CS97QK) +> - **Url**: https://cdn.sick.com/media/content/hcc/hdf/9692943974430.pdf +> - **Uri**: http://zotero.org/users/9685140/items/26CS97QK +> - **File**: [SICKipedia - 2021 - Het verschil tussen nauwkeurigheid en reproduceerb.pdf](file://C:%5CUsers%5C20003936%5CZotero%5Cstorage%5CG3WI6V7R%5CSICKipedia%2520-%25202021%2520-%2520Het%2520verschil%2520tussen%2520nauwkeurigheid%2520en%2520reproduceerb.pdf) +> - **Local Library**: [Zotero]((zotero://select/library/items/26CS97QK)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations +Annotations(24/06/2022, 17:10:23) +- *“nauwkeurigheid of accuratesse is de graad van overeenstemming van een gemeten of berekende hoeveelheid met haar daadwerkelijke (ware) waarde. hoe groter de nauwkeurigheid, hoe kleiner de totale fout.”* [(SICKipedia, 2021, p. 1)](zotero://open-pdf/library/items/G3WI6V7R?page=1&annotation=ECLFRYYH) +- *“reproduceerbaarheid, herhaalnauwkeurigheid of precisie van een meting geeft, bij gelijke omstandigheden, aan hoe goed eenzelfde uitkomst wordt gehaald. bij afstandmeetsystemen wordt de maximale afwijking in mm aangegeven, waarmee een meting onder gelijke omstandigheden kan afwijken. reproduceerbaarheid is dus niet te verwarren met absolute nauwkeurigheid.”* [(SICKipedia, 2021, p. 1)](zotero://open-pdf/library/items/G3WI6V7R?page=1&annotation=INDJUSX9) + diff --git a/content/References/@stanley.etal_2020.md b/content/References/@stanley.etal_2020.md index 113b6783..11eb704c 100644 --- a/content/References/@stanley.etal_2020.md +++ b/content/References/@stanley.etal_2020.md @@ -5,35 +5,35 @@ title: "Project management handbook: simplified Agile, Scrum, and DevOps for beg authors: Stanley, Jack C; Gross, Erik D; Tech Academy year: 2020 --- - -# Project management handbook: simplified Agile, Scrum, and DevOps for beginners - -> [!info] Metadata -> - **CiteKey**: stanley.etal_2020 -> - **Type**: book -> - **Title**: Project management handbook: simplified Agile, Scrum, and DevOps for beginners, -> - **Author**: Stanley, Jack C; Gross, Erik D; Tech Academy -> - **Year**: 2020 -> - **ISBN**: 978-0-9973264-8-2 - -> [!quote] Abstract -> What is project management? Scrum? Agile? DevOps? Project management simply refers to managing groups in the interest of accomplishing established goals. Scrum, Agile adn DevOps are names for various approaches to project management. In this book, you'll learn about each of these and how to implement them in your company. - -> [!abstract] Files and Links -> - **Uri**: [http://zotero.org/groups/4724240/items/YHK78MNS](http://zotero.org/groups/4724240/items/YHK78MNS) -> - **Uri**: [http://zotero.org/users/9685140/items/FP5TF2EU](http://zotero.org/users/9685140/items/FP5TF2EU) -> - **Local Library**: [Zotero]((zotero://select/library/items/FP5TF2EU)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Project management handbook: simplified Agile, Scrum, and DevOps for beginners + +> [!info] Metadata +> - **CiteKey**: stanley.etal_2020 +> - **Type**: book +> - **Title**: Project management handbook: simplified Agile, Scrum, and DevOps for beginners, +> - **Author**: Stanley, Jack C; Gross, Erik D; Tech Academy +> - **Year**: 2020 +> - **ISBN**: 978-0-9973264-8-2 + +> [!quote] Abstract +> What is project management? Scrum? Agile? DevOps? Project management simply refers to managing groups in the interest of accomplishing established goals. Scrum, Agile adn DevOps are names for various approaches to project management. In this book, you'll learn about each of these and how to implement them in your company. + +> [!abstract] Files and Links +> - **Uri**: [http://zotero.org/groups/4724240/items/YHK78MNS](http://zotero.org/groups/4724240/items/YHK78MNS) +> - **Uri**: [http://zotero.org/users/9685140/items/FP5TF2EU](http://zotero.org/users/9685140/items/FP5TF2EU) +> - **Local Library**: [Zotero]((zotero://select/library/items/FP5TF2EU)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@stefanowicz_2024.md b/content/References/@stefanowicz_2024.md index 9b6993b5..b8b31459 100644 --- a/content/References/@stefanowicz_2024.md +++ b/content/References/@stefanowicz_2024.md @@ -10,45 +10,45 @@ year: "2024" url: https://www.tidio.com/blog/helpdesk-metrics/ authors: " Stefanowicz, Beata" --- - -> [!Cite] -> Stefanowicz, B. (2024, May 22). _15 Essential Help Desk Metrics & KPIs [+ Best Practices]_. Tidio. [https://www.tidio.com/blog/helpdesk-metrics/](https://www.tidio.com/blog/helpdesk-metrics/) - - ---- - -# Metadata - ->[!Properties] -> **FirstAuthor** Stefanowicz, Beata -~ -> **Title** 15 Essential Help Desk Metrics & KPIs [+ Best Practices] -> **Year** 2024 -> **Citekey** stefanowicz_2024 -> **itemType** webpage - -> [!LINK] -> - -> [!Abstract] -> -> A beautiful Live Chat solution. Talk with your customers in real-time and increase your sales. Available in the free and paid versions. ->. -> -# Notes - ->> - - -# Annotations -_annotations in the paper_. -### Highlights - - - -### Notes - - - -### Images - + +> [!Cite] +> Stefanowicz, B. (2024, May 22). _15 Essential Help Desk Metrics & KPIs [+ Best Practices]_. Tidio. [https://www.tidio.com/blog/helpdesk-metrics/](https://www.tidio.com/blog/helpdesk-metrics/) + + +--- + +# Metadata + +>[!Properties] +> **FirstAuthor** Stefanowicz, Beata +~ +> **Title** 15 Essential Help Desk Metrics & KPIs [+ Best Practices] +> **Year** 2024 +> **Citekey** stefanowicz_2024 +> **itemType** webpage + +> [!LINK] +> + +> [!Abstract] +> +> A beautiful Live Chat solution. Talk with your customers in real-time and increase your sales. Available in the free and paid versions. +>. +> +# Notes + +>> + + +# Annotations +_annotations in the paper_. +### Highlights + + + +### Notes + + + +### Images + diff --git a/content/References/@userstorymap_2022.md b/content/References/@userstorymap_2022.md index 6cb5aa81..ea756f35 100644 --- a/content/References/@userstorymap_2022.md +++ b/content/References/@userstorymap_2022.md @@ -6,37 +6,37 @@ authors: userstorymap, year: 2022 url: https://www.userstorymap.io/being-an-effective-product-owner/ --- - -# How to Be An Effective Product Owner - -> [!info] Metadata -> - **CiteKey**: userstorymap_2022 -> - **Type**: blogPost -> - **Title**: How to Be An Effective Product Owner, -> - **Author**: userstorymap, -> - **Journal**: User Story Map for Jira -> - **Year**: 2022 - -> [!quote] Abstract -> See what is Product Owner role and how to become an effective one and deliver great products. - -> [!abstract] Files and Links -> - **Url**: [https://www.userstorymap.io/being-an-effective-product-owner/](https://www.userstorymap.io/being-an-effective-product-owner/) -> - **Uri**: [http://zotero.org/groups/4724240/items/9JVQR7QI](http://zotero.org/groups/4724240/items/9JVQR7QI) -> - **Uri**: [http://zotero.org/users/9685140/items/ZDXYY3L7](http://zotero.org/users/9685140/items/ZDXYY3L7) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/BPQZKMNM/being-an-effective-product-owner.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/ZDXYY3L7)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# How to Be An Effective Product Owner + +> [!info] Metadata +> - **CiteKey**: userstorymap_2022 +> - **Type**: blogPost +> - **Title**: How to Be An Effective Product Owner, +> - **Author**: userstorymap, +> - **Journal**: User Story Map for Jira +> - **Year**: 2022 + +> [!quote] Abstract +> See what is Product Owner role and how to become an effective one and deliver great products. + +> [!abstract] Files and Links +> - **Url**: [https://www.userstorymap.io/being-an-effective-product-owner/](https://www.userstorymap.io/being-an-effective-product-owner/) +> - **Uri**: [http://zotero.org/groups/4724240/items/9JVQR7QI](http://zotero.org/groups/4724240/items/9JVQR7QI) +> - **Uri**: [http://zotero.org/users/9685140/items/ZDXYY3L7](http://zotero.org/users/9685140/items/ZDXYY3L7) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/BPQZKMNM/being-an-effective-product-owner.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/ZDXYY3L7)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@vanderwardt_2017.md b/content/References/@vanderwardt_2017.md index 4c51521a..06a96742 100644 --- a/content/References/@vanderwardt_2017.md +++ b/content/References/@vanderwardt_2017.md @@ -6,37 +6,37 @@ authors: van der Wardt, Rik year: 2017 url: https://agilescrumgroup.nl/5-tips-goede-daily-stand-up-meeting/ --- - -# Daily Stand-up: 5 tips voor een goede meeting (+checklist download) - -> [!info] Metadata -> - **CiteKey**: vanderwardt_2017 -> - **Type**: blogPost -> - **Title**: Daily Stand-up: 5 tips voor een goede meeting (+checklist download), -> - **Author**: van der Wardt, Rik -> - **Journal**: Agile Scrum Group -> - **Year**: 2017 - -> [!quote] Abstract -> Lees hier onze 5 tips voor een goede Daily Stand-up meeting. Wat wel doen? En wat niet? Ook de 4 valkuilen hebben we voor je opgesomd! - -> [!abstract] Files and Links -> - **Url**: [https://agilescrumgroup.nl/5-tips-goede-daily-stand-up-meeting/](https://agilescrumgroup.nl/5-tips-goede-daily-stand-up-meeting/) -> - **Uri**: [http://zotero.org/groups/4724240/items/VZANGEIQ](http://zotero.org/groups/4724240/items/VZANGEIQ) -> - **Uri**: [http://zotero.org/users/9685140/items/QVYPYNPI](http://zotero.org/users/9685140/items/QVYPYNPI) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/45UJMHDE/5-tips-goede-daily-stand-up-meeting.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/QVYPYNPI)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Daily Stand-up: 5 tips voor een goede meeting (+checklist download) + +> [!info] Metadata +> - **CiteKey**: vanderwardt_2017 +> - **Type**: blogPost +> - **Title**: Daily Stand-up: 5 tips voor een goede meeting (+checklist download), +> - **Author**: van der Wardt, Rik +> - **Journal**: Agile Scrum Group +> - **Year**: 2017 + +> [!quote] Abstract +> Lees hier onze 5 tips voor een goede Daily Stand-up meeting. Wat wel doen? En wat niet? Ook de 4 valkuilen hebben we voor je opgesomd! + +> [!abstract] Files and Links +> - **Url**: [https://agilescrumgroup.nl/5-tips-goede-daily-stand-up-meeting/](https://agilescrumgroup.nl/5-tips-goede-daily-stand-up-meeting/) +> - **Uri**: [http://zotero.org/groups/4724240/items/VZANGEIQ](http://zotero.org/groups/4724240/items/VZANGEIQ) +> - **Uri**: [http://zotero.org/users/9685140/items/QVYPYNPI](http://zotero.org/users/9685140/items/QVYPYNPI) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/45UJMHDE/5-tips-goede-daily-stand-up-meeting.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/QVYPYNPI)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@vanlier_2018.md b/content/References/@vanlier_2018.md index 32c94197..cd29bcd2 100644 --- a/content/References/@vanlier_2018.md +++ b/content/References/@vanlier_2018.md @@ -6,33 +6,33 @@ authors: van Lier, Willemijn year: 2018 url: https://agilescrumgroup.nl/stakeholder-management-matrix-model/ --- - -# Stakeholdermanagement in projecten met Scrum - -> [!info] Metadata -> - **CiteKey**: vanlier_2018 -> - **Type**: blogPost -> - **Title**: Stakeholdermanagement in projecten met Scrum, -> - **Author**: van Lier, Willemijn -> - **Journal**: Agile Scrum Group -> - **Year**: 2018 - -> [!quote] Abstract -> Om als Product Owner de waarde van een project of product te maximaliseren, is goed stakeholdermanagement vereist. Dit is hoe dat moet. - -> [!abstract] Files and Links -> - **Url**: [https://agilescrumgroup.nl/stakeholder-management-matrix-model/](https://agilescrumgroup.nl/stakeholder-management-matrix-model/) -> - **Uri**: [http://zotero.org/groups/4724240/items/3UVWTTWC](http://zotero.org/groups/4724240/items/3UVWTTWC) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/EFHY7B3L/stakeholder-management-matrix-model.html) -> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/3UVWTTWC)) - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Stakeholdermanagement in projecten met Scrum + +> [!info] Metadata +> - **CiteKey**: vanlier_2018 +> - **Type**: blogPost +> - **Title**: Stakeholdermanagement in projecten met Scrum, +> - **Author**: van Lier, Willemijn +> - **Journal**: Agile Scrum Group +> - **Year**: 2018 + +> [!quote] Abstract +> Om als Product Owner de waarde van een project of product te maximaliseren, is goed stakeholdermanagement vereist. Dit is hoe dat moet. + +> [!abstract] Files and Links +> - **Url**: [https://agilescrumgroup.nl/stakeholder-management-matrix-model/](https://agilescrumgroup.nl/stakeholder-management-matrix-model/) +> - **Uri**: [http://zotero.org/groups/4724240/items/3UVWTTWC](http://zotero.org/groups/4724240/items/3UVWTTWC) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/EFHY7B3L/stakeholder-management-matrix-model.html) +> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/3UVWTTWC)) + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@vanrooden_2015.md b/content/References/@vanrooden_2015.md index f92b4451..2c0fe83f 100644 --- a/content/References/@vanrooden_2015.md +++ b/content/References/@vanrooden_2015.md @@ -6,38 +6,38 @@ authors: van Rooden, Stephan year: 2015 url: https://www.scrum.org/resources/blog/product-backlog-refinement-explained-13 --- - -# Product Backlog Refinement explained (1/3) - -> [!info] Metadata -> - **CiteKey**: vanrooden_2015 -> - **Type**: webpage -> - **Title**: Product Backlog Refinement explained (1/3), -> - **Author**: van Rooden, Stephan -> - **Journal**: Scrum.org -> - **Year**: 2015 - -> [!quote] Abstract -> One of the most challenging activities in Scrum is Product Backlog Refinement. During training courses I get many questions on this activity. What do you do during Product Backlog refinement? How do you prevent discussions going off track or in too much detail? Who should be there? When do you estimate? In this blog series, you will get some good practices and guidelines for having better, more effective and more vivid Product Backlog refinement. This series will consist of three posts: - -> [!abstract] Files and Links -> - **Url**: [https://www.scrum.org/resources/blog/product-backlog-refinement-explained-13](https://www.scrum.org/resources/blog/product-backlog-refinement-explained-13) -> - **Uri**: [http://zotero.org/groups/4724240/items/NNWPT5VV](http://zotero.org/groups/4724240/items/NNWPT5VV) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/SP3969UQ/product-backlog-refinement-explained-13.html) -> - **Uri**: [http://zotero.org/users/9685140/items/9RAVF38W](http://zotero.org/users/9685140/items/9RAVF38W) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/YJNDK2J5/product-backlog-refinement-explained-13.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/9RAVF38W)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Product Backlog Refinement explained (1/3) + +> [!info] Metadata +> - **CiteKey**: vanrooden_2015 +> - **Type**: webpage +> - **Title**: Product Backlog Refinement explained (1/3), +> - **Author**: van Rooden, Stephan +> - **Journal**: Scrum.org +> - **Year**: 2015 + +> [!quote] Abstract +> One of the most challenging activities in Scrum is Product Backlog Refinement. During training courses I get many questions on this activity. What do you do during Product Backlog refinement? How do you prevent discussions going off track or in too much detail? Who should be there? When do you estimate? In this blog series, you will get some good practices and guidelines for having better, more effective and more vivid Product Backlog refinement. This series will consist of three posts: + +> [!abstract] Files and Links +> - **Url**: [https://www.scrum.org/resources/blog/product-backlog-refinement-explained-13](https://www.scrum.org/resources/blog/product-backlog-refinement-explained-13) +> - **Uri**: [http://zotero.org/groups/4724240/items/NNWPT5VV](http://zotero.org/groups/4724240/items/NNWPT5VV) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/SP3969UQ/product-backlog-refinement-explained-13.html) +> - **Uri**: [http://zotero.org/users/9685140/items/9RAVF38W](http://zotero.org/users/9685140/items/9RAVF38W) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/YJNDK2J5/product-backlog-refinement-explained-13.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/9RAVF38W)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@vanrooden_2015a.md b/content/References/@vanrooden_2015a.md index ea4c1215..b40988e1 100644 --- a/content/References/@vanrooden_2015a.md +++ b/content/References/@vanrooden_2015a.md @@ -6,39 +6,39 @@ authors: van Rooden, Stephan year: 2015 url: https://www.scrum.org/resources/blog/product-backlog-refinement-explained-33 --- - -# Product Backlog Refinement explained (3/3) - -> [!info] Metadata -> - **CiteKey**: vanrooden_2015a -> - **Type**: webpage -> - **Title**: Product Backlog Refinement explained (3/3), -> - **Author**: van Rooden, Stephan -> - **Journal**: Scrum.org -> - **Year**: 2015 - -> [!quote] Abstract -> How to facilitate a Product Backlog Refinement meeting? What do you do as a Scrum Master to keep the item under refinement on track? When do you estimate and what do you do when you need more time for discussion? In this third post of this series on Product Backlog refinement you will find some good practices on how to facilitate an effective and efficient refinement meeting. -> This series consists of three posts: - -> [!abstract] Files and Links -> - **Url**: [https://www.scrum.org/resources/blog/product-backlog-refinement-explained-33](https://www.scrum.org/resources/blog/product-backlog-refinement-explained-33) -> - **Uri**: [http://zotero.org/groups/4724240/items/AUGWSIH9](http://zotero.org/groups/4724240/items/AUGWSIH9) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/XNRPEPVU/product-backlog-refinement-explained-33.html) -> - **Uri**: [http://zotero.org/users/9685140/items/API9CYGG](http://zotero.org/users/9685140/items/API9CYGG) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/BHG3X3DT/product-backlog-refinement-explained-33.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/API9CYGG)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Product Backlog Refinement explained (3/3) + +> [!info] Metadata +> - **CiteKey**: vanrooden_2015a +> - **Type**: webpage +> - **Title**: Product Backlog Refinement explained (3/3), +> - **Author**: van Rooden, Stephan +> - **Journal**: Scrum.org +> - **Year**: 2015 + +> [!quote] Abstract +> How to facilitate a Product Backlog Refinement meeting? What do you do as a Scrum Master to keep the item under refinement on track? When do you estimate and what do you do when you need more time for discussion? In this third post of this series on Product Backlog refinement you will find some good practices on how to facilitate an effective and efficient refinement meeting. +> This series consists of three posts: + +> [!abstract] Files and Links +> - **Url**: [https://www.scrum.org/resources/blog/product-backlog-refinement-explained-33](https://www.scrum.org/resources/blog/product-backlog-refinement-explained-33) +> - **Uri**: [http://zotero.org/groups/4724240/items/AUGWSIH9](http://zotero.org/groups/4724240/items/AUGWSIH9) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/XNRPEPVU/product-backlog-refinement-explained-33.html) +> - **Uri**: [http://zotero.org/users/9685140/items/API9CYGG](http://zotero.org/users/9685140/items/API9CYGG) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/BHG3X3DT/product-backlog-refinement-explained-33.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/API9CYGG)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@verheyen_2022.md b/content/References/@verheyen_2022.md index d7acada3..c4f67a45 100644 --- a/content/References/@verheyen_2022.md +++ b/content/References/@verheyen_2022.md @@ -6,37 +6,37 @@ authors: Verheyen, Gunther year: 2022 url: https://scrumglossary.org/ --- - -# Scrum Glossary - -> [!info] Metadata -> - **CiteKey**: verheyen_2022 -> - **Type**: webpage -> - **Title**: Scrum Glossary, -> - **Author**: Verheyen, Gunther -> - **Journal**: Scrum Glossary -> - **Year**: 2022 - -> [!quote] Abstract -> English Burn-down chart: a chart showing the decrease of remaining work against time. Burn-up chart: a chart showing the increase of a parameter, like value, against time. Daily Scrum: a daily event, time-boxed to 15 minutes or less, to re-plan the development work during a Sprint. The event serves to plan the work for the… - -> [!abstract] Files and Links -> - **Url**: [https://scrumglossary.org/](https://scrumglossary.org/) -> - **Uri**: [http://zotero.org/groups/4724240/items/6UJGXFI4](http://zotero.org/groups/4724240/items/6UJGXFI4) -> - **Uri**: [http://zotero.org/users/9685140/items/JQLIXRQ8](http://zotero.org/users/9685140/items/JQLIXRQ8) -> - **File**: [scrum-glossary-dutch-version-2021.pdf](file:///Users/jan/Zotero/storage/4KVKCL4J/scrum-glossary-dutch-version-2021.pdf); [Snapshot](file:///Users/jan/Zotero/storage/TTT93ZH9/scrumglossary.org.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/JQLIXRQ8)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Scrum Glossary + +> [!info] Metadata +> - **CiteKey**: verheyen_2022 +> - **Type**: webpage +> - **Title**: Scrum Glossary, +> - **Author**: Verheyen, Gunther +> - **Journal**: Scrum Glossary +> - **Year**: 2022 + +> [!quote] Abstract +> English Burn-down chart: a chart showing the decrease of remaining work against time. Burn-up chart: a chart showing the increase of a parameter, like value, against time. Daily Scrum: a daily event, time-boxed to 15 minutes or less, to re-plan the development work during a Sprint. The event serves to plan the work for the… + +> [!abstract] Files and Links +> - **Url**: [https://scrumglossary.org/](https://scrumglossary.org/) +> - **Uri**: [http://zotero.org/groups/4724240/items/6UJGXFI4](http://zotero.org/groups/4724240/items/6UJGXFI4) +> - **Uri**: [http://zotero.org/users/9685140/items/JQLIXRQ8](http://zotero.org/users/9685140/items/JQLIXRQ8) +> - **File**: [scrum-glossary-dutch-version-2021.pdf](file:///Users/jan/Zotero/storage/4KVKCL4J/scrum-glossary-dutch-version-2021.pdf); [Snapshot](file:///Users/jan/Zotero/storage/TTT93ZH9/scrumglossary.org.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/JQLIXRQ8)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@visual-paradigm_2022.md b/content/References/@visual-paradigm_2022.md index c1dde8c0..e18f5f87 100644 --- a/content/References/@visual-paradigm_2022.md +++ b/content/References/@visual-paradigm_2022.md @@ -6,33 +6,33 @@ authors: visual-paradigm, year: 2022 url: https://www.visual-paradigm.com/scrum/why-fixed-length-of-sprints-in-scrum/ --- - -# Why Fixed Length Sprints in Scrum? - -> [!info] Metadata -> - **CiteKey**: visual-paradigm_2022 -> - **Type**: webpage -> - **Title**: Why Fixed Length Sprints in Scrum?, -> - **Author**: visual-paradigm, -> - **Year**: 2022 - -> [!abstract] Files and Links -> - **Url**: [https://www.visual-paradigm.com/scrum/why-fixed-length-of-sprints-in-scrum/](https://www.visual-paradigm.com/scrum/why-fixed-length-of-sprints-in-scrum/) -> - **Uri**: [http://zotero.org/groups/4724240/items/YC4LLIK7](http://zotero.org/groups/4724240/items/YC4LLIK7) -> - **Uri**: [http://zotero.org/users/9685140/items/YR55R9AG](http://zotero.org/users/9685140/items/YR55R9AG) -> - **File**: [Why Fixed Length Sprints in Scrum?](file:///Users/jan/Zotero/storage/MKDQWMK2/why-fixed-length-of-sprints-in-scrum.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/YR55R9AG)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Why Fixed Length Sprints in Scrum? + +> [!info] Metadata +> - **CiteKey**: visual-paradigm_2022 +> - **Type**: webpage +> - **Title**: Why Fixed Length Sprints in Scrum?, +> - **Author**: visual-paradigm, +> - **Year**: 2022 + +> [!abstract] Files and Links +> - **Url**: [https://www.visual-paradigm.com/scrum/why-fixed-length-of-sprints-in-scrum/](https://www.visual-paradigm.com/scrum/why-fixed-length-of-sprints-in-scrum/) +> - **Uri**: [http://zotero.org/groups/4724240/items/YC4LLIK7](http://zotero.org/groups/4724240/items/YC4LLIK7) +> - **Uri**: [http://zotero.org/users/9685140/items/YR55R9AG](http://zotero.org/users/9685140/items/YR55R9AG) +> - **File**: [Why Fixed Length Sprints in Scrum?](file:///Users/jan/Zotero/storage/MKDQWMK2/why-fixed-length-of-sprints-in-scrum.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/YR55R9AG)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@visualparadigm_2022.md b/content/References/@visualparadigm_2022.md index dc5fd0ad..b321d3b9 100644 --- a/content/References/@visualparadigm_2022.md +++ b/content/References/@visualparadigm_2022.md @@ -6,29 +6,29 @@ authors: Visual Paradigm, year: 2022 url: https://www.visual-paradigm.com/scrum/what-are-scrum-time-boxed-events/ --- - -# What are Time-boxed Events in Scrum? - -> [!info] Metadata -> - **CiteKey**: visualparadigm_2022 -> - **Type**: webpage -> - **Title**: What are Time-boxed Events in Scrum?, -> - **Author**: Visual Paradigm, -> - **Year**: 2022 - -> [!abstract] Files and Links -> - **Url**: [https://www.visual-paradigm.com/scrum/what-are-scrum-time-boxed-events/](https://www.visual-paradigm.com/scrum/what-are-scrum-time-boxed-events/) -> - **Uri**: [http://zotero.org/groups/4724240/items/U69W97VV](http://zotero.org/groups/4724240/items/U69W97VV) -> - **File**: [What are Time-boxed Events in Scrum?](file:///Users/jan/Zotero/storage/6BXHRL27/what-are-scrum-time-boxed-events.html) -> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/U69W97VV)) - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# What are Time-boxed Events in Scrum? + +> [!info] Metadata +> - **CiteKey**: visualparadigm_2022 +> - **Type**: webpage +> - **Title**: What are Time-boxed Events in Scrum?, +> - **Author**: Visual Paradigm, +> - **Year**: 2022 + +> [!abstract] Files and Links +> - **Url**: [https://www.visual-paradigm.com/scrum/what-are-scrum-time-boxed-events/](https://www.visual-paradigm.com/scrum/what-are-scrum-time-boxed-events/) +> - **Uri**: [http://zotero.org/groups/4724240/items/U69W97VV](http://zotero.org/groups/4724240/items/U69W97VV) +> - **File**: [What are Time-boxed Events in Scrum?](file:///Users/jan/Zotero/storage/6BXHRL27/what-are-scrum-time-boxed-events.html) +> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/U69W97VV)) + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@vrielink_2020.md b/content/References/@vrielink_2020.md index 996e2960..4032c23a 100644 --- a/content/References/@vrielink_2020.md +++ b/content/References/@vrielink_2020.md @@ -6,32 +6,32 @@ authors: Vrielink, Martijn year: 2020 url: https://www.incentro.com/nl-NL/blog/story-points-hoe-werken-ze-eigenlijk --- - -# Hoe werken story points? - -> [!info] Metadata -> - **CiteKey**: vrielink_2020 -> - **Type**: webpage -> - **Title**: Hoe werken story points?, -> - **Author**: Vrielink, Martijn -> - **Year**: 2020 - -> [!quote] Abstract -> Een beproefde methode binnen scrum om product backlog items in te schatten is die van de story points. Wat zijn story points eigenlijk? En hoe gebruik je ze? - -> [!abstract] Files and Links -> - **Url**: [https://www.incentro.com/nl-NL/blog/story-points-hoe-werken-ze-eigenlijk](https://www.incentro.com/nl-NL/blog/story-points-hoe-werken-ze-eigenlijk) -> - **Uri**: [http://zotero.org/groups/4724240/items/LYJVS5XK](http://zotero.org/groups/4724240/items/LYJVS5XK) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/XVVZRLLF/story-points-hoe-werken-ze-eigenlijk.html) -> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/LYJVS5XK)) - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Hoe werken story points? + +> [!info] Metadata +> - **CiteKey**: vrielink_2020 +> - **Type**: webpage +> - **Title**: Hoe werken story points?, +> - **Author**: Vrielink, Martijn +> - **Year**: 2020 + +> [!quote] Abstract +> Een beproefde methode binnen scrum om product backlog items in te schatten is die van de story points. Wat zijn story points eigenlijk? En hoe gebruik je ze? + +> [!abstract] Files and Links +> - **Url**: [https://www.incentro.com/nl-NL/blog/story-points-hoe-werken-ze-eigenlijk](https://www.incentro.com/nl-NL/blog/story-points-hoe-werken-ze-eigenlijk) +> - **Uri**: [http://zotero.org/groups/4724240/items/LYJVS5XK](http://zotero.org/groups/4724240/items/LYJVS5XK) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/XVVZRLLF/story-points-hoe-werken-ze-eigenlijk.html) +> - **Local Library**: [Zotero]((zotero://select/groups/4724240/items/LYJVS5XK)) + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@wikipedia_2023.md b/content/References/@wikipedia_2023.md index 054812d5..cd3f78d8 100644 --- a/content/References/@wikipedia_2023.md +++ b/content/References/@wikipedia_2023.md @@ -10,65 +10,65 @@ year: "2023" url: https://nl.wikipedia.org/w/index.php?title=Ishikawa-diagram&oldid=63986119 authors: " Wikipedia" --- - -> [!Cite] -> Wikipedia. (2023). Ishikawa-diagram. In _Wikipedia_. [https://nl.wikipedia.org/w/index.php?title=Ishikawa-diagram&oldid=63986119](https://nl.wikipedia.org/w/index.php?title=Ishikawa-diagram&oldid=63986119) - - ---- - -# Metadata - ->[!Properties] -> **FirstAuthor** Wikipedia -~ -> **Title** Ishikawa-diagram -> **Year** 2023 -> **Citekey** wikipedia_2023 -> **itemType** encyclopediaArticle - -> [!LINK] -> - -> [!Abstract] -> -> Het Ishikawa-diagram (ook wel bekend als visgraatdiagram) is een hulpmiddel dat bedoeld is om mogelijke oorzaken van problemen in kaart te brengen. Deze methode werd ontwikkeld door Kaoru Ishikawa die destijds werkzaam was bij Kawasaki Heavy Industries in Japan. Hij zag dat de mensen in de fabriek vaak werden overweldigd door het grote aantal factoren dat (mogelijk) van invloed was op een proces. Om dit makkelijker en overzichtelijker te maken, bedacht hij een eenvoudig en grafisch hulpmiddel om potentiële oorzaken van een probleem of een effect ordelijk weer te geven. Het doel is om de output van de brainstorm te kunnen structureren en niet zoals vaak gedacht het oplossen van een bestaand probleem. De methode is oorspronkelijk vooral van toepassing op productieprocessen en de bijbehorende kwaliteitscontrole. Tegenwoordig is de methode ook bekend voor de dienstensector. In dat laatste geval worden echter wel andere categorieën gebruikt. -Het diagram maakt onderscheid in mogelijke oorzaken en gevolgen. Aan de rechterkant wordt het veroorzaakte effect of probleem beschreven. Aan de linkerkant worden de mogelijke oorzaken in kaart gebracht. De mogelijke oorzaken worden ingedeeld in zes categorieën waarbij weer vertakkingen naar sub-oorzaken worden gelegd. Hiervoor worden de zes M's gebruikt: - - Mens: Wordt het probleem wel goed begrepen? Is er wel goede communicatie? Zijn de betrokkenen wel ervaren genoeg en goed genoeg opgeleid? -Machine (Machines, gereedschap & computers): Worden de juiste machines, gereedschap en software gebruikt? Kunnen deze hulpmiddelen zelf oorzaak zijn van een probleem? Zijn de machines wel veilig in het gebruik? -Metingen: Hoe meten we kwaliteit? Wat zijn de criteria? Hoe betrouwbaar zijn deze metingen? Hoe vaak vinden deze plaats? -Materialen: Welke materialen worden gebruikt? Wat is de kwaliteit hiervan? -Milieu (Omgevingsfactoren): Welke invloed heeft de omgeving? Denk bijvoorbeeld aan het weer, trillingen, geluidsoverlast, hoogteverschil. -Methode: Hoe verloopt de logistiek, communicatie, labelling en het bijhouden van de administratie? Hoe zijn de processen opgesteld en worden ze ook nageleefd? -Voor de dienstensector worden de vier P's gebruikt: - -Policies -Procedures -People -Plant / technology -Voor het integraal logistiek concept wordt "PBOI" gebruikt: - -Proces -Besturing -Organisatie -Informatie ->. -> -# Notes - ->> - - -# Annotations -_annotations in the paper_. -### Highlights - - - -### Notes - - - -### Images - + +> [!Cite] +> Wikipedia. (2023). Ishikawa-diagram. In _Wikipedia_. [https://nl.wikipedia.org/w/index.php?title=Ishikawa-diagram&oldid=63986119](https://nl.wikipedia.org/w/index.php?title=Ishikawa-diagram&oldid=63986119) + + +--- + +# Metadata + +>[!Properties] +> **FirstAuthor** Wikipedia +~ +> **Title** Ishikawa-diagram +> **Year** 2023 +> **Citekey** wikipedia_2023 +> **itemType** encyclopediaArticle + +> [!LINK] +> + +> [!Abstract] +> +> Het Ishikawa-diagram (ook wel bekend als visgraatdiagram) is een hulpmiddel dat bedoeld is om mogelijke oorzaken van problemen in kaart te brengen. Deze methode werd ontwikkeld door Kaoru Ishikawa die destijds werkzaam was bij Kawasaki Heavy Industries in Japan. Hij zag dat de mensen in de fabriek vaak werden overweldigd door het grote aantal factoren dat (mogelijk) van invloed was op een proces. Om dit makkelijker en overzichtelijker te maken, bedacht hij een eenvoudig en grafisch hulpmiddel om potentiële oorzaken van een probleem of een effect ordelijk weer te geven. Het doel is om de output van de brainstorm te kunnen structureren en niet zoals vaak gedacht het oplossen van een bestaand probleem. De methode is oorspronkelijk vooral van toepassing op productieprocessen en de bijbehorende kwaliteitscontrole. Tegenwoordig is de methode ook bekend voor de dienstensector. In dat laatste geval worden echter wel andere categorieën gebruikt. +Het diagram maakt onderscheid in mogelijke oorzaken en gevolgen. Aan de rechterkant wordt het veroorzaakte effect of probleem beschreven. Aan de linkerkant worden de mogelijke oorzaken in kaart gebracht. De mogelijke oorzaken worden ingedeeld in zes categorieën waarbij weer vertakkingen naar sub-oorzaken worden gelegd. Hiervoor worden de zes M's gebruikt: + + Mens: Wordt het probleem wel goed begrepen? Is er wel goede communicatie? Zijn de betrokkenen wel ervaren genoeg en goed genoeg opgeleid? +Machine (Machines, gereedschap & computers): Worden de juiste machines, gereedschap en software gebruikt? Kunnen deze hulpmiddelen zelf oorzaak zijn van een probleem? Zijn de machines wel veilig in het gebruik? +Metingen: Hoe meten we kwaliteit? Wat zijn de criteria? Hoe betrouwbaar zijn deze metingen? Hoe vaak vinden deze plaats? +Materialen: Welke materialen worden gebruikt? Wat is de kwaliteit hiervan? +Milieu (Omgevingsfactoren): Welke invloed heeft de omgeving? Denk bijvoorbeeld aan het weer, trillingen, geluidsoverlast, hoogteverschil. +Methode: Hoe verloopt de logistiek, communicatie, labelling en het bijhouden van de administratie? Hoe zijn de processen opgesteld en worden ze ook nageleefd? +Voor de dienstensector worden de vier P's gebruikt: + +Policies +Procedures +People +Plant / technology +Voor het integraal logistiek concept wordt "PBOI" gebruikt: + +Proces +Besturing +Organisatie +Informatie +>. +> +# Notes + +>> + + +# Annotations +_annotations in the paper_. +### Highlights + + + +### Notes + + + +### Images + diff --git a/content/References/@wikipediakwaliteitsmanagement_2020.md b/content/References/@wikipediakwaliteitsmanagement_2020.md index 4a633263..d1dc3fda 100644 --- a/content/References/@wikipediakwaliteitsmanagement_2020.md +++ b/content/References/@wikipediakwaliteitsmanagement_2020.md @@ -6,38 +6,38 @@ authors: Wikipedia kwaliteitsmanagement, year: 2020 url: https://nl.wikipedia.org/w/index.php?title=Kwaliteitsmanagement&oldid=55870333 --- - -# Kwaliteitsmanagement - -> [!info] Metadata -> - **CiteKey**: wikipediakwaliteitsmanagement_2020 -> - **Type**: encyclopediaArticle -> - **Title**: Kwaliteitsmanagement -> - **Author**: Wikipedia kwaliteitsmanagement -> - **Journal**: Wikipedia -> - **Year**: 2020 - -> [!quote] Abstract -> Kwaliteitsmanagement is de tak van het management die streeft naar een zo hoog mogelijke kwaliteit van een product, productieproces, dienst of organisatie. Kwaliteitsmanagement is geen afgebakend vakgebied, maar komt terug in alle delen van het management van een onderneming. - -> [!abstract] Files and Links -> - **Uri**: [http://zotero.org/groups/4724240/items/JWSVKEC6](http://zotero.org/groups/4724240/items/JWSVKEC6) -> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/LDNNE82G/Kwaliteitsmanagement.html) -> - **Url**: https://nl.wikipedia.org/w/index.php?title=Kwaliteitsmanagement&oldid=55870333 -> - **Uri**: http://zotero.org/users/9685140/items/SV5FYFQU -> - **File**: [Snapshot](file://C:%5CUsers%5C20003936%5CZotero%5Cstorage%5C2N6UDILG%5CKwaliteitsmanagement.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/SV5FYFQU)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# Kwaliteitsmanagement + +> [!info] Metadata +> - **CiteKey**: wikipediakwaliteitsmanagement_2020 +> - **Type**: encyclopediaArticle +> - **Title**: Kwaliteitsmanagement +> - **Author**: Wikipedia kwaliteitsmanagement +> - **Journal**: Wikipedia +> - **Year**: 2020 + +> [!quote] Abstract +> Kwaliteitsmanagement is de tak van het management die streeft naar een zo hoog mogelijke kwaliteit van een product, productieproces, dienst of organisatie. Kwaliteitsmanagement is geen afgebakend vakgebied, maar komt terug in alle delen van het management van een onderneming. + +> [!abstract] Files and Links +> - **Uri**: [http://zotero.org/groups/4724240/items/JWSVKEC6](http://zotero.org/groups/4724240/items/JWSVKEC6) +> - **File**: [Snapshot](file:///Users/jan/Zotero/storage/LDNNE82G/Kwaliteitsmanagement.html) +> - **Url**: https://nl.wikipedia.org/w/index.php?title=Kwaliteitsmanagement&oldid=55870333 +> - **Uri**: http://zotero.org/users/9685140/items/SV5FYFQU +> - **File**: [Snapshot](file://C:%5CUsers%5C20003936%5CZotero%5Cstorage%5C2N6UDILG%5CKwaliteitsmanagement.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/SV5FYFQU)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations + diff --git a/content/References/@zentaoteam_2022a.md b/content/References/@zentaoteam_2022a.md index ae26f691..98cd0e7c 100644 --- a/content/References/@zentaoteam_2022a.md +++ b/content/References/@zentaoteam_2022a.md @@ -6,32 +6,32 @@ authors: ZenTao team, year: 2022 url: https://www.zentao.pm/blog/What-are-the-complete-Scrum-artifacts-1102.html --- - -# What Are The Complete Scrum Artifacts? - Agile - ZenTao - -> [!info] Metadata -> - **CiteKey**: zentaoteam_2022a -> - **Type**: webpage -> - **Title**: What Are The Complete Scrum Artifacts? - Agile - ZenTao, -> - **Author**: ZenTao team, -> - **Year**: 2022 - -> [!abstract] Files and Links -> - **Url**: [https://www.zentao.pm/blog/What-are-the-complete-Scrum-artifacts-1102.html](https://www.zentao.pm/blog/What-are-the-complete-Scrum-artifacts-1102.html) -> - **Uri**: [http://zotero.org/users/9685140/items/8ZCN4II5](http://zotero.org/users/9685140/items/8ZCN4II5) -> - **File**: [What Are The Complete Scrum Artifacts? - Agile - ZenTao](file:///Users/jan/Zotero/storage/2YVBWSJ6/What-are-the-complete-Scrum-artifacts-1102.html) -> - **Local Library**: [Zotero]((zotero://select/library/items/8ZCN4II5)) - -> [!note] Tags and Collections -> - **Collections**: Project Management - ----- - -## Comments - - - ----- - -## Extracted Annotations - + +# What Are The Complete Scrum Artifacts? - Agile - ZenTao + +> [!info] Metadata +> - **CiteKey**: zentaoteam_2022a +> - **Type**: webpage +> - **Title**: What Are The Complete Scrum Artifacts? - Agile - ZenTao, +> - **Author**: ZenTao team, +> - **Year**: 2022 + +> [!abstract] Files and Links +> - **Url**: [https://www.zentao.pm/blog/What-are-the-complete-Scrum-artifacts-1102.html](https://www.zentao.pm/blog/What-are-the-complete-Scrum-artifacts-1102.html) +> - **Uri**: [http://zotero.org/users/9685140/items/8ZCN4II5](http://zotero.org/users/9685140/items/8ZCN4II5) +> - **File**: [What Are The Complete Scrum Artifacts? - Agile - ZenTao](file:///Users/jan/Zotero/storage/2YVBWSJ6/What-are-the-complete-Scrum-artifacts-1102.html) +> - **Local Library**: [Zotero]((zotero://select/library/items/8ZCN4II5)) + +> [!note] Tags and Collections +> - **Collections**: Project Management + +---- + +## Comments + + + +---- + +## Extracted Annotations +