Skip to Content

Changes for page Peer reviews

Last modified by Danniar Firdausy on 2024/09/18 14:42
From version 22.8
edited by Danniar Firdausy
on 2024/09/18 14:42
Change comment: There is no comment for this version
To version 21.1
edited by Erik Bakker
on 2022/08/30 08:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -1,7 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 +In this microlearning, we will take a look at peer reviews for eMagiz.
2 2  
3 -Welcome to this microlearning session on peer reviews with eMagiz. In this microlearning, we will explore how peer reviews can enhance the quality of your integration solutions on the eMagiz platform. We will cover essential prerequisites, key concepts, and practical tips for running effective peer reviews. Whether you are new to peer reviews or looking to refine your process, this session will provide valuable insights to help you and your team achieve higher quality and consistency.
4 -
5 5  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
7 7  == 1. Prerequisites ==
... ... @@ -10,16 +10,11 @@
10 10  
11 11  == 2. Key concepts ==
12 12  
13 -This microlearning centers on peer-reviews.
14 -* By Peer reviews, we mean: A disciplined engineering practice for detecting and correcting defects in software artifacts and preventing their leakage into production.
12 +Peer reviews are defined as follows: A disciplined engineering practice for detecting and correcting defects in software artifacts and preventing their leakage into production. Its a well known and working concept with IT organization, and it can definetely applied in DevOps teams that have eMagiz as one of the technology pillars.
15 15  
16 -== 3. Running peer reviews in eMagiz ==
17 -
18 -Peer reviews is a well known and working concept with IT organization, and it can definetely applied in DevOps teams that have eMagiz as one of the technology pillars.
19 -
20 20  [[image:Main.Images.Microlearning.WebHome@intermediate-devops-perspectives-peerreview-1.png]]
21 21  
22 -Key benefits of peer reviews:
16 +Key benefits of peer reviews
23 23  
24 24  * Improved quality of integrations
25 25  * Higher consistency
... ... @@ -28,6 +28,8 @@
28 28  * Architecture challenge and verification
29 29  * Find alternative solutions
30 30  
25 +== 3. Running peer reviews in eMagiz ==
26 +
31 31  === 3.1 Who and when ===
32 32  
33 33  Doing peer reviews increases the quality of the delivered work by the team. This means it is the whole team's responsibility to ensure peer reviews are performed. Following that logic, asking different individuals within your team for other peer reviews makes sense.
... ... @@ -96,18 +96,18 @@
96 96   ** Cloud over on-premise
97 97   ** No hard-coded variable – use properties
98 98  
99 -== 4. Key takeaways ==
95 +== 4. Assignment ==
100 100  
101 -* Peer reviews are essential in any DevOps team for improving the quality of your integration solutions by identifying and correcting defects early in the development process.
102 -* Implement a structured approach to peer reviews by following the provided checklist for each Integration Lifecycle Management (ILM) phase. This will help maintain consistency and thoroughness in your reviews.
103 -* Use the peer review process not only to catch errors but also to foster knowledge sharing and challenge architectural decisions. Adjust the peer review process as needed based on team feedback and evolving project requirements.
97 +See how peer reviews are currently implemented within the projects on which you work to see if you can learn something from the information you have gathered via this microlearning.
104 104  
105 -== 5. Suggested Additional Readings ==
99 +== 5. Key takeaways ==
106 106  
107 -You will find plenty background items available on the Internet. If you are interested in this topic within the eMagiz platform, please see the following link:
101 +Peer reviews are instrumental in any DevOps team. Use the provided list as your team's peer review starting point and tune as you go along.
108 108  
109 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
110 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
111 -*** [[The five phases of eMagiz (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-intro-the-five-phases-of-emagiz||target="blank"]]
112 -* [[Peer Review (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22peer+review%22||target="blank"]]
113 -)))((({{toc/}}))){{/container}}{{/container}}
103 +== 6. Suggested Additional Readings ==
104 +
105 +You will find plenty background items available on the Internet.
106 +
107 +== 7. Silent demonstration video ==
108 +
109 +As this is a more theoretical microlearning we have no video for this.)))((({{toc/}}))){{/container}}{{/container}}