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