Pull-Request [pxl-projectmanagement-11-25-2024] from Obsidian

content/999 Bibliografie.md

@@ -49,7 +49,6 @@ order: "999"
 - [[./References/@agilescrumgroup_2018|@agilescrumgroup_2018]]: _'De Sprint Review uitgelegd. Waarom deze meeting? (+ Checklist & Valkuilen)'_ -  **Agile Scrum Group,(2018)** https://agilescrumgroup.nl/sprint-review/<br/><br/>  
 - [[./References/@agilescrumgroup_2017|@agilescrumgroup_2017]]: _'Wat is Definition of Done? Check de uitleg en voorbeelden (IT & non-IT)'_ -  **Agile Scrum Group,(2017)** https://agilescrumgroup.nl/wat-is-definition-of-done/<br/><br/>  
 - [[./References/@agile4all_2019|@agile4all_2019]]: _'Sprint Planning'_ -  **agile4all,(2019)** https://www.agile4all.nl/sprint-planning/<br/><br/>  
-- [[./References/@doshi_2016|@doshi_2016]]: _'The Three Pillars of Empiricism (Scrum)'_ -  **Doshi, Hiren(2016)** https://www.scrum.org/resources/blog/three-pillars-empiricism-scrum<br/><br/>  
 - [[./References/@martin_2020|@martin_2020]]: _'Incremental Model in SDLC: Use, Advantage & Disadvantage'_ -  **Martin, Matthew(2020)** https://www.guru99.com/what-is-incremental-model-in-sdlc-advantages-disadvantages.html<br/><br/>  
 - [[./References/@productplan_2022|@productplan_2022]]: _'User Story'_ -  **productplan,(2022)** https://www.productplan.com/glossary/user-story/<br/><br/>  
 - [[./References/@qframe_2021|@qframe_2021]]: _'Scrum Master, Teambuilder of Agile Coach?'_ -  **qframe,(2021)** https://qframe.be/2021/06/25/scrum-master-teambuilder-of-agile-coach/<br/><br/>  
@@ -63,7 +62,6 @@ order: "999"
 - [[./References/@vanrooden_2015|@vanrooden_2015]]: _'Product Backlog Refinement explained (1/3)'_ -  **van Rooden, Stephan(2015)** https://www.scrum.org/resources/blog/product-backlog-refinement-explained-13<br/><br/>  
 - [[./References/@vanrooden_2015a|@vanrooden_2015a]]: _'Product Backlog Refinement explained (3/3)'_ -  **van Rooden, Stephan(2015)** https://www.scrum.org/resources/blog/product-backlog-refinement-explained-33<br/><br/>  
 - [[./References/@verheyen_2022|@verheyen_2022]]: _'Scrum Glossary'_ -  **Verheyen, Gunther(2022)** https://scrumglossary.org/<br/><br/>  
-- [[./References/@verheyen_2017|@verheyen_2017]]: _'De kernwaarden van Scrum'_ -  **Verheyen, Gunther(2017)** https://guntherverheyen.com/2017/02/15/de-kernwaarden-van-scrum/<br/><br/>  
 - [[./References/@visualparadigm_2022|@visualparadigm_2022]]: _'What are Time-boxed Events in Scrum?'_ -  **Visual Paradigm,(2022)** https://www.visual-paradigm.com/scrum/what-are-scrum-time-boxed-events/<br/><br/>  
 - [[./References/@visual-paradigm_2022|@visual-paradigm_2022]]: _'Why Fixed Length Sprints in Scrum?'_ -  **visual-paradigm,(2022)** https://www.visual-paradigm.com/scrum/why-fixed-length-of-sprints-in-scrum/<br/><br/>  
 - [[./References/@vrielink_2020|@vrielink_2020]]: _'Hoe werken story points?'_ -  **Vrielink, Martijn(2020)** https://www.incentro.com/nl-NL/blog/story-points-hoe-werken-ze-eigenlijk<br/><br/>  

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  
+  

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  
+  

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  
+  

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  
+