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