22:
167:
While continuous delivery and agile software development provide for faster execution on a project level, the accelerated pace made possible by continuous delivery creates challenges for less-agile components in an IT portfolio. ERM provides organizations with a comprehensive view of software change
122:
packages changes together for execution and delivery, so an enterprise release is a mechanism for integrating and managing multiple, independent programs and projects that impact the enterprise. ERM takes an end-to-end life cycle perspective addressing the (strategic) planning, execution and delivery
126:
An enterprise release consolidates and integrates the deliverables of multiple projects (or more generally, change initiatives) that have to be time-boxed or synchronised so they can be tested and released as a whole. By stressing the need for a cohesive release architecture, ERM aims to supplement
130:
While traditional release management addresses fine-grained changes and provides technical support for the project, ERM supports enterprise portfolio/project management (PPM) and brings a pragmatic architectural and execution perspective to the selection and planning to an enterprise release.
168:
across a large collection of related systems allowing project managers and IT managers to coordinate projects that have adopted more continuous approaches to software delivery with projects that require a slower, more sequential approach for application development.
155:
is starting to influence how software transitions from development to release. With continuous delivery, transitions from development to release are continuously automated. Changes are committed to code repositories, builds and tests are run immediately in a
109:
supporting the orchestration of people, process, and technology across multiple departments and application development teams to deliver large, highly integrated software changes within the context of an IT portfolio.
81:(ERM) is a multi-disciplinary IT governance framework for managing software delivery and software change across multiple departments in a large organization. ERM builds upon
127:
portfolio prioritization with greater design governance that serves to improve productivity and reduce change disruption by executing related features together.
123:
of an organization's entire change portfolio, even though in reality it is often confined to the latter integration, test and implementation stages of delivery.
196:
65:
43:
36:
140:
218:
Taborda, L.J. (2011). Enterprise
Release Management: Agile Delivery of a Strategic Change Portfolio, Artech House.
139:
Organizations practicing
Enterprise Release Management often support software projects across a wide spectrum of
171:
Enterprise
Release Management provides enterprises with a model that can adopt the localized effects of both
161:
160:
system, and changes can be released to production without the ceremony that accompanies the traditional
231:
148:
151:. With the increasing popularity of agile development a new approach to software releases known as
98:
30:
106:
157:
47:
90:
86:
8:
176:
152:
119:
102:
82:
144:
225:
94:
197:"The Irresistible Rise of Agile Development - Wall Street & Technology"
172:
134:
85:
and combines it with other aspects of IT management including
143:. An IT portfolio often incorporates more traditional
147:projects alongside more iterative projects using
223:
113:
135:Influence of Continuous Delivery and DevOps
66:Learn how and when to remove this message
29:This article includes a list of general
101:. ERM places considerable emphasis on
224:
15:
13:
35:it lacks sufficient corresponding
14:
243:
141:software development methodology
20:
189:
1:
182:
179:to the larger IT department.
79:Enterprise release management
201:Wall Street & Technology
7:
162:Software release life cycle
10:
248:
149:Agile software development
114:Managing Multiple Releases
99:Configuration management
107:IT portfolio management
50:more precise citations.
158:continuous integration
91:IT service management
87:Business-IT alignment
118:Just as traditional
177:Continuous delivery
153:Continuous delivery
120:release management
103:project management
83:release management
232:Change management
76:
75:
68:
239:
211:
210:
208:
207:
193:
71:
64:
60:
57:
51:
46:this article by
37:inline citations
24:
23:
16:
247:
246:
242:
241:
240:
238:
237:
236:
222:
221:
215:
214:
205:
203:
195:
194:
190:
185:
145:Waterfall model
137:
116:
72:
61:
55:
52:
42:Please help to
41:
25:
21:
12:
11:
5:
245:
235:
234:
220:
219:
213:
212:
187:
186:
184:
181:
136:
133:
115:
112:
74:
73:
56:September 2011
28:
26:
19:
9:
6:
4:
3:
2:
244:
233:
230:
229:
227:
217:
216:
202:
198:
192:
188:
180:
178:
174:
169:
165:
163:
159:
154:
150:
146:
142:
132:
128:
124:
121:
111:
108:
104:
100:
96:
95:IT Governance
92:
88:
84:
80:
70:
67:
59:
49:
45:
39:
38:
32:
27:
18:
17:
204:. Retrieved
200:
191:
170:
166:
138:
129:
125:
117:
78:
77:
62:
53:
34:
48:introducing
206:2015-08-11
183:References
31:references
226:Category
44:improve
173:DevOps
97:, and
33:, but
175:and
105:and
228::
199:.
164:.
93:,
89:,
209:.
69:)
63:(
58:)
54:(
40:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.