Changes for page Peer reviews
Last modified by Danniar Firdausy on 2024/09/18 14:42
From version 19.1
edited by Erik Bakker
on 2022/08/30 08:28
on 2022/08/30 08:28
Change comment:
There is no comment for this version
To version 22.8
edited by Danniar Firdausy
on 2024/09/18 14:42
on 2024/09/18 14:42
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Default language
-
... ... @@ -1,0 +1,1 @@ 1 +en - Content
-
... ... @@ -1,6 +1,7 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -In this microlearning, we will take a look at peer reviews for eMagiz. 3 3 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 + 4 4 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 5 5 6 6 == 1. Prerequisites == ... ... @@ -9,11 +9,16 @@ 9 9 10 10 == 2. Key concepts == 11 11 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. In tbe context of eMagiz, peer reviews are done usually after the Create phase. 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. 13 13 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 + 14 14 [[image:Main.Images.Microlearning.WebHome@intermediate-devops-perspectives-peerreview-1.png]] 15 15 16 -Key benefits of peer reviews 22 +Key benefits of peer reviews: 17 17 18 18 * Improved quality of integrations 19 19 * Higher consistency ... ... @@ -22,10 +22,14 @@ 22 22 * Architecture challenge and verification 23 23 * Find alternative solutions 24 24 25 -== 3. Runningpeer reviews ineMagiz==31 +=== 3.1 Who and when === 26 26 27 - ===3.1Considerationsfor reviewee===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. 28 28 35 +As described below, peer reviews should be conducted for every critical decision when building an integration solution via the eMagiz platform. See section 3.3 for a detailed list. 36 + 37 +=== 3.2 Considerations for reviewee === 38 + 29 29 Here are some things to keep in mind when presenting the work to peer review. 30 30 31 31 * Quickly explain the story / task / background ... ... @@ -35,7 +35,7 @@ 35 35 ** Don’t show every single detail but try to highlight the important parts and/or details you’re less sure about. This takes time and experience to get “right” and is different depending on the story, the reviewee, the reviewer, the project, etc. 36 36 * Always do a peer review, no exceptions. Making assumptions about the usefulness beforehand defeats the whole purpose. 37 37 38 -=== 3. 2Considerations for reviewer ===48 +=== 3.3 Considerations for reviewer === 39 39 40 40 Here are some things to keep in mind when peer reviewing the work . 41 41 ... ... @@ -86,18 +86,18 @@ 86 86 ** Cloud over on-premise 87 87 ** No hard-coded variable – use properties 88 88 89 -== 4. Assignment ==99 +== 4. Key takeaways == 90 90 91 -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. 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. 92 92 93 -== 5. Keytakeaways ==105 +== 5. Suggested Additional Readings == 94 94 95 - PeerreviewsareinstrumentalinanyDevOpsteam. Use theprovided listasyour team'speerreviewstartingpoint andtuneasyougoalong.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: 96 96 97 -== 6. Suggested Additional Readings == 98 - 99 -You will find plenty background items available on the Internet. 100 - 101 -== 7. Silent demonstration video == 102 - 103 -As this is a more theoretical microlearning we have no video for this.)))((({{toc/}}))){{/container}}{{/container}} 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}}