Help/VersionOne.htm at master · Rollins/Help · GitHub

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
<html><head>

<meta http-equiv="X-UA-Compatible">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="Using VersionOne to track requests, tasks, and defects against the sprint cycle">
<meta name="keywords" content="version,one,track,progress,sprint,cycle,scrum,develop,deploy,business,owner,user,story,stories,task,description,conversation,approv">
<title>Using VersionOne</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>
<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;amp;lt;p&amp;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;amp;lt;/p&amp;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">
  <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">
  <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>
  <title></title>
  <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;">Using VersionOne</p></h1>
<p align="left" style="margin-left:40px; margin-bottom:40px">Rollins Marketing uses VersionOne to manage the software development process. This tool tracks requests, tasks, and defects against the sprint cycle. <br>
  <strong>It is important that all contributors to Marketing software projects plan, track, and update their projects in this central tool.</strong></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="#v1access">Accessing VersionOne</a></p>
  <p><a href="#v1track">Tracking Progress in VersionOne</a></p>
    <p><a href="#v1story">Adding User Stories</a></p>
    <p><a href="#v1task">Adding Tasks</a></p>
    <p><a href="#v1convo">Using the Conversations Feature</a></p>
    <p><a href="#v1bo">Business Owner Approval</a></p>
    <p><a href="#v1moreinfo">Read More About VersionOne</a></p>
    <p><a href="#v1related">Related Topics</a></p>

   </ul>
</div>
<div class="body">
  <h4 id="v1access" style="margin-left: 40px; margin-top: 100px; border-top: thin solid #bcbeb0; width:30%">Accessing VersionOne</h4>
  <p style="margin-left:40px">The Rollins Marketing team can access our VersionOne tool at <a href="https://www11.v1host.com/Rollins">https://www11.v1host.com/Rollins</a>. <br>
    <br></p>

    <p style="margin-left:40px"> To request login credentials, email <a href="mailto:marketingtechnology@rollins.com">marketingtechnology@rollins.com.</a></p>
    <p style="margin-left:40px"></p>

  <h4 id="v1track" style="margin-left:40px; margin-top:100px; border-top: thin solid #bcbeb0; width:30%">Tracking Progress in VersionOne</h4>
  <p style="margin-left:40px">All contributors to Rollins Marketing projects use the VersionOne tool to track the progress of projects. <br>This ensures that Marketing Technology, Rollins contributors, and agency partners are aware of all project elements.</p>
  <p id="v1story" style="margin-left:40px"><br>
    <strong>Adding User Stories </strong><br>
    <br>
    Add a user story in VersionOne to track your contribution. Follow these guidelines:<br>
    <br>
  </p><ul style="list-style-type:disc; margin-left:30px">
    <li>Create your user story from the pre-defined Rollins User Story Template.<br>
      <br>
      <font color="red"> <strong>IMPORTANT: </strong></font> To avoid overwriting the template, change the title of the user story before saving.<br>
      <br>
    </li>
    <li>Use a descriptive title for the user story. The user story must be easily identifiable in lists, boards, and reports.<br>
      <br>
    </li><li>Leave the Sprint field blank. This will be determined by the scrum master or product owner when the user story
      is prioritized.<br>
      <br>
    </li><li>Use this standard Agile format to describe the user story and define acceptance criteria:<br>
      <br>
      <strong>Executive Summary</strong><br>
      <p style="margin-left:40px"><i>insert a brief description of the requested work</i></p>
      <br>
      <b>User Story Description</b><br>
      <p style="margin-left:40px">As a <br>
        I want to<br>
        So that<br>
      </p>
      <b>Acceptance Criteria</b><br>
      <p style="margin-left:40px">Given that <br>
        When<br>
        Then </p>
      <br>
    </li><li>In the Estimated Development Complete Date field, enter the targeted deployment date, based on the current Sprint calendar. </li>
    <br>
    <li>Leave the Product Owner field blank. This will be determined by the scrum master or product owner when the user story is prioritized. </li>
    <br>
    <li>Enter your name in the Owners field.</li>
    <br>
    <li>Use the default Medium Priority. The scrum master or product owner adjusts this priority as-needed. Contact the product owner to request a higher priority for your user story. </li>
    <br>
    <li>Select Place Holder in the Status field. This will be changed by the scrum master or product owner when the user story is prioritized. </li>
    <br>
    <li>If you are unsure of other user story selections; for example, Backlog Group, use the VersionOne Conversations tool to request input from the scrum master or product owner.</li><br>
  </ul>
  <br>

<p></p><p id="v1task" style="margin-left:40px"><strong>Adding Tasks </strong><br> <br>Add tasks to the user story to track the phases of your project. Follow these guidelines:<br></p><ul style="list-style-type:disc; margin-left:30px"><br>


  <li>Add a task for each step of the development and  deployment process; for example:</li>
</ul>
<p></p><p style="margin-left:90px">Research and Planning<br>
  Development<br>
  Review</p>
<ul style="list-style-type:disc; margin-left:30px"><br>

  <li>The task’s estimated hours must be four hours or  less. Create ordinal tasks to subdivide large phases into short&nbsp; tasks; for example:</li>
</ul>
<p style="margin-left:90px">Development Phase One<br>
  Development Phase Two<br>
  Development Phase Three</p>
<ul style="list-style-type:disc; margin-left:30px"><br>

  <li>Use a short, descriptive title and write a brief  description of the task.</li><br>
  <li>When creating tasks, you can leave Status field  blank until the associated work is in progress. Remember to update the Status  field as-needed to reflect the current status of the task.</li><br>
  <li>Add the estimated hours in the Detail Estimate Hrs  field. </li><br>
  <li>Add to-do hours.&nbsp;  Typically, the estimated hours and to-do hours are the same, until the  associated work is in progress. Remember to update the to-do hours daily after  work on the task begins.<br></li>
</ul>
<p></p>


<h4 id="v1convo" style="margin-left:40px; margin-top:100px; border-top: thin solid #bcbeb0; width:30%">Using the Conversations Tool</h4>
<p style="margin-left:40px">Use the <a href="popv1con.html" target="popup" onclick="window.open('popv1con.html','popup','width=1230,height=560,scrollbars=no,resizable=no'); return false;">
    Conversations Tool
</a> to add notifications and questions, or to seek Business Owner approval. Click a User Story item in the list, and add your conversation comment in the left pane. It is helpful to tag a VersionOne user in the conversation.</p>

<h4 id="v1bo" style="margin-left:40px; margin-top:100px; border-top: thin solid #bcbeb0; width:30%">Business Owner Approval</h4>
<p style="margin-left:40px"> Rollins Marketing Business Owners review contributions and  approve them for deployment to production. Follow these guidelines: </p>
<ul style="list-style-type:disc; margin-left:30px">
  <li>After developing and testing your contribution  in a local environment, push the code to dev.orkin.com.</li><br>
  <li>Use VersionOne Conversations to notify the  Business Owner that the contribution is ready for review.</li><br>
  <li>Work with the Business Owner on adjustments and  revisions. If necessary, push updated code to dev.orkin.com for the Business Owner’s approval.</li>
</ul>
<div>
  <p style="margin-left:70px"> <font color="red"> <strong>IMPORTANT:&nbsp; </strong></font>Use VersionOne Conversations to track revisions and review cycles. </p>
</div>
<ul style="list-style-type:disc; margin-left:30px">
  <li>Ensure the Business Owner approves the final  contribution in VersionOne.</li>
</ul>
<h4 id="v1moreinfo" style="margin-left:40px; margin-top:100px; border-top: thin solid #bcbeb0; width:30%">Read More About VersionOne</h4>
<p style="margin-left:40px">For in-depth information and tutorials, visit the VersionOne Community at <a href="http://community.versionone.com/VersionOne-Lifecycle" target="_blank">http://community.versionone.com/VersionOne-Lifecycle</a>. </p>
</div>

<p id="v1related" align="left" style="margin-left:40px; margin-top:100px"><strong>Related Topics:</strong></p>
<ul>
  <p><a href="Sprint_Deploy.htm">Sprint Cycle and Deployment</a></p>
  <p><a href="Sprint_Deploy.htm#changemgt">Software Change Management</a></p>
  <p><a href="Sprint_Deploy.htm#appliedrol">Applied Change Management in Rollins Marketing</a></p>
  <p><a href="popsprintcal.html" target="popup" onclick= "window.open('popsprintcal.html','popup','width=1100,height=1000,scrollbars=no,resizable=no'); return false;">Rollins Marketing Release Cycle</a></p>
  <p><a href="Sprint_Deploy.htm#sprintagile">About Agile Software Development</a></p>
  <p><a href="Sprint_Deploy.htm#sprintscrum">Scrum Methodology</a></p>
</ul>
</div>

<!-- /row -->
<!-- /row --><!-- /span4 -->    <!-- /span4 -->    <!-- /span6 --><!-- /row -->
</a>

</body></html>