-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathSprint_Deploy.htm
More file actions
269 lines (249 loc) · 13.2 KB
/
Sprint_Deploy.htm
File metadata and controls
269 lines (249 loc) · 13.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
<html><head>
<meta http-equiv="X-UA-Compatible">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="Exploring the Rollins software development life cycle">
<meta name="keywords" content="sprint,deploy,agile,scrum,change,control,track">
<title>Sprint Cycle and Deployment</title>
<!--?xml version="1.0" encoding="utf-8"?-->
<style type="text/css">
@import url("css/base-admin-3.css");
@import url("css/font-awesome.min.css");
</style>
<link href="https://fonts.googleapis.com/css?family=Open+Sans" rel="stylesheet">
<style type="text/css">
</style>
<link href="page-vflzfYSfI.css" rel="stylesheet" type="text/css">
<link href="css/main-vflaPAd44.css" rel="stylesheet" type="text/css">
<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">
<style type="text/css">
body {
background-image: url(none);
}
</style>
<link href="css/bootstrap.css" rel="stylesheet" type="text/css">
<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body style="width:100%">
<iframe frameborder="0" scrolling="no" align="left" width="100%" height="80px" src="header.htm" name="framehead" id="framehead">
&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;p&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;iframes are not supported by your browser.&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;lt;/p&amp;amp;amp;amp;amp;amp;amp;amp;amp;amp;gt;
</iframe>
<br>
<a href="header.htm" target="framehead"></a><br>
<div class="body" style="margin-top:40px">
<style type='text/css'>
/***** Side Content *****/
#sidecontent
{
margin-right:10%;
margin-left: 30px;
padding:20px 20px 20px 20px;
float:right;
border: 2px solid #CC092f;
border-radius: 5px;
}
#sidecontent ul
{
color:#333;
list-style:none;
padding:0 0 10 0;
margin:0;
background:inherit;
}
#sidecontent li
{
padding: 0.1ex 0 5px 0;
}
#sidecontent li a
{
color:#000;
text-decoration:none;
font-size:1em;
display:block;
padding:8px 20px;
background:inherit;
}
#sidecontent li a:hover
{
background:#CC092F;
color:white;
}
#sidecontent h4
{
font-size:1em;
font-weight:bold;
margin:0;
text-align:center
}
</style>
<p align="left" style="margin-left:40px; margin-bottom:50px"><a href="index.htm"><br>
<span>Back to Help</span></a></p>
</div>
<div class="topichero">
<div id="sidecontent">
<h4><br>
Jump To:</h4>
<br>
<ul>
<li><a href="FAQ.htm">FAQ</a></li>
<li><a href="downloads.htm">PDFs</a></li>
<li><a href="VersionOne.htm">VersionOne</a></li>
<li><a href="Sprint_Deploy.htm">Sprint Cycle</a></li>
<li><a href="GitHub.htm">GitHub</a></li>
<li><a href="bestpractices.htm">Technical Procedures and <br>Best Practices</a></li>
<li><a href="international.htm">International Franchise</a></li>
<li><a href="risk.htm">Troubleshooting</a></li>
<li><a href="mcc.htm">Marketing Command Center</a></li>
<li><a href="Glossaries.htm">Glossaries</a></li>
</ul>
</div>
<div class="title-text">
<div class="HomeHeroSection">
<div class="centered-text">
<div>
<h1> <p align="left" style="margin-left:40px;">Sprint Cycle and Deployment</p></h1>
<p align="left" style="margin-left:40px; margin-bottom:40px">A sprint is the period of time in which the Marketing Technology team commits to delivering a viable set of new technological features, enhancements, or updates to Rollins products.
<br>
Deployment of these updates occurs on designated dates during the sprint. </p>
<p align="left" style="margin-left:40px; margin-bottom:40px"><a href="documents/currentcalendar.pdf" target="new">Click here for the current sprint calendar.</a></p>
<!-- CSS styles for standard search box -->
<!-- HTML for SEARCH BAR --> </div>
</div>
</div>
</div><p></p>
</div>
<p></p><p></p>
<div align="left">
<div class="body">
<p align="left" style="margin-left:40px;"><strong>In this article:</strong></p>
<ul>
<p><a href="#changemgt">Software Change Management</a></p>
<p><a href="#appliedrol">Applied Change Management in Rollins Marketing</a></p>
<p><a href="#sprintagile">About Agile Software Development</a></p>
<p><a href="#sprintscrum">Scrum Methodology</a></p>
<p><a href="#moreinfosprint">Learn More About Agile Software Development</a> </p>
<p><a href="#sprintrelated">Related Topics</a></p>
</ul>
</div>
<div style="margin-left:40px" class="body">
<h4 id="changemgt" style="margin-top: 100px; border-top: thin solid #bcbeb0; width:30%">Software Change Management</h4>
<p>Software change management is the discipline of tracking and controlling changes during the software development and deployment process. Some aspects of this discipline include:</p>
<div>
<p><strong>Change Control</strong></p>
</div>
<p>Change control is a process that ensures changes to software are monitored and controlled, to avoid arbitrary or unapproved changes that may result in disruption of service, errors in the software, or overwriting of code contributed by other developers.</p>
<div>
<p><strong>Build Management</strong></p>
</div>
<p>A build is the result of converting software code into software artifacts. These artifacts are functioning software tools or, in the case of Rollins Marketing, functioning websites.<br>
Build management ensures that the process and tools are properly implemented and result in quality builds.</p>
<div>
<p><strong>Process Management</strong></p>
</div>
<p>Process management ensures that all contributors adhere to the established software development process.</p>
<div>
<p><strong>Team Building</strong></p>
</div>
<p>Promoting a supportive team environment facilitates effective interactions within the software <br>
development process.</p>
<div>
<p><strong>Defect Tracking</strong></p>
</div>
<p>Defect tracking discloses defects and traces them to the source, ensuring defects are mitigated in the future.</p>
<h1> </h1>
<p style="margin-left:40px"> </p>
<p style="margin-left:40px"></p>
<h4 id="appliedrol" style="margin-top:100px; border-top: thin solid #bcbeb0; width:30%">Applied Change Management in Rollins Marketing</h4>
<p>Rollins Marketing adheres to industry-standard change management concepts. The following section outlines some specifics of the Rollins Marketing process. </p>
<p><strong>Rollins Marketing Sprint Cycle</strong></p>
<p>The Rollins Marketing Technology team and all contributors adhere to a <a href="popsprintcal.html" target="popup" onclick= "window.open('popsprintcal.html','popup','width=1100,height=1000,scrollbars=no,resizable=no'); return false;">
defined Agile sprint cycle.
</a>Sprints are four weeks, and changes are deployed to production every two weeks. </p>
<div>
<p><strong>Requesting Off-Cycle Deployments</strong></p>
</div>
<p>Because the sprint cycle allows two production deployments per month, off-cycle deployments are rarely authorized.<br>
In the event of a crisis that requires an off-cycle deployment, the Business Owner must request the deployment in VersionOne.<br>
The Marketing Technology team requires written authorization from a member of the Rollins Marketing Executive Leadership team before scheduling an off-cycle deployment.</p>
<p> </p>
<p> </p>
<h4 id="sprintagile" style="margin-top:100px; border-top: thin solid #bcbeb0; width:50%"> About Agile Software Development</h4>
<p> Marketing Technology uses Agile software development methods. Agile developement is based on principles under which requirements and solutions evolve through the collaborative effort of cross-functional teams. It advocates adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change.</p>
<p>The <a href="http://agilemanifesto.org/" target="_blank">Agile manifesto</a> describes values such as:</p>
<dl>
<dt>Individuals and interactions</dt>
<dd>Self-organization and motivation are important, as are interactions like co-location and pair-programing.</dd>
<dt>.</dt>
<dt>Working software</dt>
<dd>Working software is more useful and welcome than just presenting documents to clients in meetings.</dd>
<dt> </dt>
<dt>Customer collaboration</dt>
<dd>Requirements cannot be fully collected at the beginning of the software development cycle, therefore continuous customer or stakeholder involvement is very important.</dd>
<dt> </dt>
<dt>Responding to change</dt>
<dd>Agile methods are focused on quick responses to change and continuous development.</dd>
</dl>
<p>The Agile manifesto is based on the following <a href="http://agilemanifesto.org/principles.html" target="new">principles</a>:</p>
<ol>
<li>Customer satisfaction by early and continuous delivery of valuable software</li>
<li>Welcome changing requirements, even in late development</li>
<li>Working software is delivered frequently (weeks rather than months)</li>
<li>Close, daily cooperation between business people and developers</li>
<li>Projects are built around motivated individuals, who should be trusted</li>
<li>Face-to-face conversation is the best form of communication (co-location)</li>
<li>Working software is the principal measure of progress</li>
<li>Sustainable development, able to maintain a constant pace</li>
<li>Continuous attention to technical excellence and good design</li>
<li>Simplicity—the art of maximizing the amount of work not done—is essential</li>
<li>Best architectures, requirements, and designs emerge from self-organizing teams</li>
<li>Regularly, the team reflects on how to become more effective, and adjusts accordingly</li>
</ol>
<p> </p>
<h4 id="sprintscrum" style="margin-top:100px; border-top: thin solid #bcbeb0; width:50%"> Scrum Methodology</h4>
<p>Agile supports several software development methodologies. The Marketing Technology team uses the Scrum methodology.</p>
<p>Scrum is an iterative and incremental framework for managing product development. A key principle of Scrum is its recognition that during product development, the stakeholders may change their minds about what they want and need, leading to requirements volatility<a href="https://en.wikipedia.org/wiki/Scrum_(software_development)#cite_note-4">.</a> </p>
<p>Scrum is based on the following values:</p>
<dl>
<dt>Commitment</dt>
<dd>Team members individually commit to achieving their team goals, each and every Sprint.</dd>
<dt>Courage</dt>
<dd>Team members know they have the courage to work through conflict and challenges together so that they can do the right thing.</dd>
<dt>Focus</dt>
<dd>Team members focus exclusively on their team goals and the Sprint Backlog; there should be no work done other than through their backlog.</dd>
<dt>Openness</dt>
<dd>Team members and their stakeholders agree to be transparent about their work and any challenges they face.</dd>
<dt>Respect</dt>
<dd>Team members respect each other to be technically capable and to work with good intent.</dd>
</dl>
<p>The Scrum team relies on three core roles:</p>
<li>The Product Owner represents the product's stakeholders and customers, and is accountable for ensuring that the team delivers value to the business. </li>
<li>The Development Team is responsible for delivering potentially shippable increments of product at the end of each Sprint.</li>
<li>The Scrum Master is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables.</li>
<p> </p>
<p>For more information on Scrum, see the <a href="documents/CollabNet_scrumreferencecard.pdf">Scrum Reference Card.</a></p>
<p> </p>
<h4 id="moreinfosprint" style="margin-top:100px; border-top: thin solid #bcbeb0; width:50%">Learn More About Agile Software Development</h4>
<p>Explore these links to learn more:</p>
<ul style="margin-left: 0px">
<p><a href="https://www.agilealliance.org/agile101/">Agile Alliance</a></p>
<p><a href="http://www.collab.net/services/training/agile_e-learning">Scrum Training Series</a></p>
<p><a href="http://www.scrumguides.org/">Scrum Guide</a></p>
<p><a href="https://www.versionone.com/resources/">VersionOne Agile Resources</a></p>
</ul>
<p> </p>
</div>
<p id="sprintrelated" align="left" style="margin-left:40px; margin-top:100px"><strong>Related Topics:</strong></p>
<ul>
<p><a href="versionone.htm#v1track">Tracking Progress in VersionOne</a></p>
<p><a href="https://www.agilealliance.org/agile101/agile-glossary/">Agile Terminology</a></p>
<p><a href="bestpractices.htm">Best Practices</a></p>
</ul>
</div>
<!-- /row -->
<!-- /row --><!-- /span4 --> <!-- /span4 --> <!-- /span6 --><!-- /row -->
</a>
</body></html>