Wiki source code of Using ILM tollgates while executing sprints
Last modified by Erik Bakker on 2024/08/26 12:15
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
6.1 | 1 | {{container}}{{container layoutStyle="columns"}}((( |
| |
17.1 | 2 | In this microlearning, we’ll explore how to effectively use ILM tollgates while developing on the eMagiz platform within a sprint cadence. Tollgates are checkpoints that help ensure all necessary steps are completed and quality standards are met throughout the integration lifecycle. By incorporating these tollgates into your Definition of Done lists, you can enhance the quality of your work, support peer reviews, and ensure that every integration is business-ready. We’ll guide you through the key aspects of these tollgates and how they fit into the overall Integration Lifecycle of eMagiz. |
| |
1.1 | 3 | |
| |
6.1 | 4 | Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. |
| |
1.1 | 5 | |
| 6 | == 1. Prerequisites == | ||
| 7 | |||
| 8 | * Basic knowledge of the eMagiz platform | ||
| 9 | |||
| 10 | == 2. Key concepts == | ||
| 11 | |||
| 12 | This microlearning centers around using ILM tollgates. | ||
| 13 | With tollgates, we mean: A list of items that can be inserted into Definition of Done lists that are used | ||
| 14 | |||
| 15 | Key aspects are | ||
| 16 | |||
| |
11.1 | 17 | * Organized around the Integration Lifecycle of eMagiz |
| |
1.1 | 18 | * A good business ready designs for every integration |
| 19 | * Ensure all steps required are taken | ||
| 20 | * Can help with peer reviews | ||
| 21 | * Increases quality of the work that is delivered | ||
| 22 | |||
| 23 | == 3. Using ILM tollgates while executing sprints == | ||
| 24 | |||
| 25 | In this microlearning, we will focus on the use of tollgates while using the eMagiz platform to develop functionality for the customer (with the help of sprints). By using these tollgates you can increase the quality of work. | ||
| 26 | |||
| 27 | Key aspects are | ||
| 28 | |||
| 29 | * Organized around the Integration LifeCycle of eMagiz | ||
| 30 | * A good business ready designs for every integration | ||
| 31 | * Ensure all steps required are taken | ||
| 32 | * Can help with peer reviews | ||
| 33 | * Increases quality of the work that is delivered | ||
| 34 | |||
| |
12.1 | 35 | In the remainder of this section, we will zoom in on these various tollgates. Before we do so, lets first introduce the concept a little bit more. |
| |
1.1 | 36 | |
| 37 | Tollgates in this context are the list of items that can be inserted into Definition of Done lists that are used. These tollgates are organized around the Integration LifeCycle of eMagiz (Capture, Design, Create, Deploy and Manage), further referred to as the ILM. The ILM has the intention to take each new or changed integration through a guided process to ensure all steps required are taken. For most of these process steps, certain elements can be verified before continuing which can help peer reviews and prepare deployments. Further, these items will help you to make good business-ready designs for every integration. | ||
| 38 | |||
| 39 | Depending on the structure used in the user story writing for DevOps teams, these DoD items can be set properly at the right location. For instance, the Capture & Design ILM phases are often put into a single User Story so that tollgates T1 and/or T2 can be connected to this User Story as DoD items. Situations are different every time, the intention is to provide some inspiration to the DevOps team with daily eMagiz activities. | ||
| 40 | |||
| 41 | The tollgates are described below in terms of a list of suggestions per tollgate. For more information on the Integration Life Cycle, please check out the documentation menu to find out more. | ||
| 42 | |||
| |
6.1 | 43 | [[image:Main.Images.Microlearning.WebHome@novice-devops-perspectives-using-ilm-tollgates-while-executing-sprints--tollgates-in-combination-with-ilm-phases.png]] |
| |
1.1 | 44 | |
| 45 | === 3.1 Tollgate T1 – Business Ready === | ||
| 46 | |||
| 47 | The objective of this tollgate is to validate the business value to add new integrations before starting the actual change in eMagiz. | ||
| 48 | |||
| 49 | * Background and necessity of the new integration | ||
| 50 | * Sense of urgency and deadlines | ||
| 51 | * What are the business processes involved | ||
| 52 | * What is the criticality of the business process and what indicators are used to measure this | ||
| 53 | * What type of information is exchanged? | ||
| 54 | * What are the assumptions, preconditions, and dependencies from a business point of view | ||
| 55 | * Are there legal implications or requirements | ||
| 56 | * What is the impact on architectural principals | ||
| 57 | * Is there formal approval from key stakeholders to implement this integration? | ||
| 58 | |||
| 59 | === 3.2 Tollgate T2 – Discovery Done === | ||
| 60 | |||
| 61 | The objective of this tollgate is to ensure all aspects of the integration are properly validated and agreed upon with the business before creating the actual integration. | ||
| 62 | |||
| 63 | * Clarity on scope, effort, risks, and impact (story points) | ||
| 64 | * Capture 100% completed | ||
| 65 | * Design 100% completed (CDM, Message definitions, and Design Architecture) | ||
| 66 | * Definitions from both system stable and final | ||
| 67 | * High-level design available | ||
| 68 | * Impact on eMagiz Cloud resource known | ||
| 69 | * Impact on timelines with associated teams and involved application agreed | ||
| 70 | * Summary presentation available with a summary of Discovery and approved by key stakeholders | ||
| 71 | |||
| 72 | === 3.3 Tollgate T3 – Delivery Ready (to start) === | ||
| 73 | |||
| 74 | The objective of this tollgate is to validate if the create phase can start * are all information elements available? | ||
| 75 | |||
| 76 | * Connectivity test on environments from source and target system completed | ||
| 77 | * Handover from eMagiz Architect to eMagiz DevOps team completed | ||
| 78 | * Definitions from both system stable and final | ||
| 79 | * example messages available and representative | ||
| 80 | * Test scenario's created by business ready and available | ||
| 81 | |||
| 82 | == 3.4 Tollgate T4 – Delivery Done == | ||
| 83 | |||
| 84 | The objective of this tollgate is to validate if the Create phase has been properly completed * focus on review and peer review. | ||
| 85 | |||
| 86 | * Create completed | ||
| 87 | * All flows are part of a Release and are running stable without errors on Test | ||
| 88 | * Unit tests are available and stable | ||
| 89 | * Peer review completed | ||
| 90 | * End to end test with business completed | ||
| 91 | * Test report presented and agreed with business stakeholders | ||
| 92 | |||
| 93 | == 3.5 Tollgate T5 – Ketentest Ready (to start) == | ||
| 94 | |||
| 95 | The objective of this tollgate is to ensure the business can test the new or changed integration in the Acceptance environment. | ||
| 96 | |||
| 97 | * Unit test completed on Acceptance | ||
| 98 | * Test scenarios are accepted by the business | ||
| 99 | * Criteria for a successful end to end test known | ||
| 100 | * Acceptance environments of involved systems are representative for the integration to test | ||
| 101 | * Dates are agreed jointly to run the test | ||
| 102 | * eMagiz specifics | ||
| 103 | * All flows are released on Acceptance | ||
| 104 | * Connectivity check done on Acceptance | ||
| 105 | * Properties are properly configured on Acceptance | ||
| 106 | |||
| 107 | == 3.6 Tollgate T6 – Go-live Ready == | ||
| 108 | |||
| 109 | The objective of this tollgate is to prepare the Go-live of the Release to production | ||
| 110 | |||
| 111 | * End to end test completed | ||
| 112 | * Go live plan ready and reviewed | ||
| 113 | * Go live date agreed with the business | ||
| 114 | * Rollback scenario's ready | ||
| 115 | * Risk assessment completed and actions set out | ||
| 116 | * eMagiz specifics | ||
| 117 | * All flows are inside a proper release | ||
| 118 | * Connectivity check done on Production | ||
| 119 | * Properties are properly configured on Production | ||
| 120 | * Deploy Architecture current | ||
| 121 | |||
| 122 | == 3.7 Tollgate T7 – Go-live Done == | ||
| 123 | |||
| 124 | The objective of this tollgate is to validate the production environment if the Release is running on Production. | ||
| 125 | |||
| 126 | * No warnings or errors that can't be explained or for which no plan is in place | ||
| 127 | * Alerting updated | ||
| 128 | * Transfer to Support completed in case of a Model SLA | ||
| 129 | * All systems are live. | ||
| 130 | |||
| |
13.1 | 131 | == 4. Key takeaways == |
| |
1.1 | 132 | |
| 133 | * Key aspects are | ||
| 134 | * Organized around the Integration LifeCycle of eMagiz | ||
| 135 | * A good business ready designs for every integration | ||
| 136 | * Ensure all steps required are taken | ||
| 137 | * Can help with peer reviews | ||
| 138 | * Increases quality of the work that is delivered | ||
| 139 | |||
| |
13.1 | 140 | == 5. Suggested Additional Readings == |
| |
1.1 | 141 | |
| |
14.1 | 142 | * [[Novice (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]] |
| 143 | ** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Lifecycle Management.WebHome||target="blank"]] | ||
| |
15.1 | 144 | *** [[What is Lifecycle Management (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.Lifecycle Management.novice-lifecycle-management-what-is-lifecycle-management||target="blank"]] |
| |
14.1 | 145 | ** [[DevOps Perspectives (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.DevOps Perspectives.WebHome||target="blank"]] |
| |
15.1 | 146 | *** [[Annotations (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.DevOps Perspectives.novice-devops-perspectives-annotations||target="blank"]] |
| |
17.1 | 147 | * [[Tollgates (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22tollgates%22||target="blank"]] |
| |
1.1 | 148 | |
| |
6.1 | 149 | )))((({{toc/}}))){{/container}}{{/container}} |