Skip to Content
Version 1.1 by eMagiz on 2022/05/22 21:29
Show last authors
1 {{html wiki="true"}}
2 <div class="ez-academy">
3 <div class="ez-academy_body">
4
5 <div class="doc">
6
7
8
9 = Using ILM tollgates while executing sprints =
10
11 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.
12
13 Should you have any questions, please contact academy@emagiz.com.
14
15 * Last update: May 9th, 2021
16 * Required reading time: 9 minutes
17
18 == 1. Prerequisites ==
19
20 * Basic knowledge of the eMagiz platform
21
22 == 2. Key concepts ==
23
24 This microlearning centers around using ILM tollgates.
25 With tollgates, we mean: A list of items that can be inserted into Definition of Done lists that are used
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
35
36
37 == 3. Using ILM tollgates while executing sprints ==
38
39 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.
40
41 Key aspects are
42
43 * Organized around the Integration LifeCycle of eMagiz
44 * A good business ready designs for every integration
45 * Ensure all steps required are taken
46 * Can help with peer reviews
47 * Increases quality of the work that is delivered
48
49 In the remainder of this section, we will zoom in on these various tollgates. Before we do so first introduce the concept a little bit more.
50
51 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.
52
53 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.
54
55 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.
56
57 <p align="center">[[image:novice-devops-perspectives-using-ilm-tollgates-while-executing-sprints--tollgates-in-combination-with-ilm-phases.png||]]</p>
58
59 === 3.1 Tollgate T1 – Business Ready ===
60
61 The objective of this tollgate is to validate the business value to add new integrations before starting the actual change in eMagiz.
62
63 * Background and necessity of the new integration
64 * Sense of urgency and deadlines
65 * What are the business processes involved
66 * What is the criticality of the business process and what indicators are used to measure this
67 * What type of information is exchanged?
68 * What are the assumptions, preconditions, and dependencies from a business point of view
69 * Are there legal implications or requirements
70 * What is the impact on architectural principals
71 * Is there formal approval from key stakeholders to implement this integration?
72
73 === 3.2 Tollgate T2 – Discovery Done ===
74
75 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.
76
77 * Clarity on scope, effort, risks, and impact (story points)
78 * Capture 100% completed
79 * Design 100% completed (CDM, Message definitions, and Design Architecture)
80 * Definitions from both system stable and final
81 * High-level design available
82 * Impact on eMagiz Cloud resource known
83 * Impact on timelines with associated teams and involved application agreed
84 * Summary presentation available with a summary of Discovery and approved by key stakeholders
85
86 === 3.3 Tollgate T3 – Delivery Ready (to start) ===
87
88 The objective of this tollgate is to validate if the create phase can start * are all information elements available?
89
90 * Connectivity test on environments from source and target system completed
91 * Handover from eMagiz Architect to eMagiz DevOps team completed
92 * Definitions from both system stable and final
93 * example messages available and representative
94 * Test scenario's created by business ready and available
95
96 == 3.4 Tollgate T4 – Delivery Done ==
97
98 The objective of this tollgate is to validate if the Create phase has been properly completed * focus on review and peer review.
99
100 * Create completed
101 * All flows are part of a Release and are running stable without errors on Test
102 * Unit tests are available and stable
103 * Peer review completed
104 * End to end test with business completed
105 * Test report presented and agreed with business stakeholders
106
107 == 3.5 Tollgate T5 – Ketentest Ready (to start) ==
108
109 The objective of this tollgate is to ensure the business can test the new or changed integration in the Acceptance environment.
110
111 * Unit test completed on Acceptance
112 * Test scenarios are accepted by the business
113 * Criteria for a successful end to end test known
114 * Acceptance environments of involved systems are representative for the integration to test
115 * Dates are agreed jointly to run the test
116 * eMagiz specifics
117 * All flows are released on Acceptance
118 * Connectivity check done on Acceptance
119 * Properties are properly configured on Acceptance
120
121 == 3.6 Tollgate T6 – Go-live Ready ==
122
123 The objective of this tollgate is to prepare the Go-live of the Release to production
124
125 * End to end test completed
126 * Go live plan ready and reviewed
127 * Go live date agreed with the business
128 * Rollback scenario's ready
129 * Risk assessment completed and actions set out
130 * eMagiz specifics
131 * All flows are inside a proper release
132 * Connectivity check done on Production
133 * Properties are properly configured on Production
134 * Deploy Architecture current
135
136 == 3.7 Tollgate T7 – Go-live Done ==
137
138 The objective of this tollgate is to validate the production environment if the Release is running on Production.
139
140 * No warnings or errors that can't be explained or for which no plan is in place
141 * Alerting updated
142 * Transfer to Support completed in case of a Model SLA
143 * All systems are live.
144
145 ===== Practice =====
146
147 == 4. Assignment ==
148
149 Determine for the project(s) you are currently working on to which extent you are using the above tollgates and identify possible improvement points to increase the quality of work.
150
151 == 5. Key takeaways ==
152
153 * Key aspects are
154 * Organized around the Integration LifeCycle of eMagiz
155 * A good business ready designs for every integration
156 * Ensure all steps required are taken
157 * Can help with peer reviews
158 * Increases quality of the work that is delivered
159
160
161
162 == 6. Suggested Additional Readings ==
163
164 If you are interested in this topic and want more information on it please read up on Scrum.
165
166 == 7. Silent demonstration video ==
167
168 As this is a theoretical microlearning no video is made.
169
170 </div>
171
172 </div>
173 </div>
174
175 {{/html}}