-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
executable file
·307 lines (279 loc) · 10.5 KB
/
index.html
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
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Winning and delivering big projects from a small agency perspective - Ramon Vilar</title>
<meta name="description" content="Winning and delivering big projects from a small agency perspective">
<meta name="author" content="Ramon Vilar">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/beige.css" id="theme">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<!-- Any section element inside of this container is displayed as a slide -->
<div class="slides">
<section>
<h1>Winning and delivering big projects from a small agency perspective</h1>
<h3>DrupalCon Barcelona 2015</h3>
<p>
<small>By <a href="https://www.drupal.org/u/rvilar">Ramon Vilar</a> / <a href="http://twitter.com/rvilar">@rvilar</a></small>
</p>
</section>
<section>
<h2>Who Am I</h2>
<p>
explain who am I...
</p>
</section>
<section>
<h2>Index</h2>
<ol>
<li>Context</li>
<li>The team</li>
</ol>
</section>
<section>
<section>
<h2>Context</h2>
</section>
<section>
<h2>Small agency</h2>
<p>During this session, we can define a small agency as:<p>
<ul>
<li>Team with 3-10 people</li>
<li>Not focused in a specialization</li>
<li>Not hierarchical</li>
</ul>
</section>
<section>
<h2>Typical projects</h2>
<ul>
<li>1 to 4 months</li>
<li>Every project from a different client or sector</li>
<li>When working for big client, usually working through big agencies</li>
</ul>
</section>
<section>
<h2>Our desire</h2>
<p>We want to remove layers between us and our clients to work closely with them</p>
<p class="fragment">We want projects during at least 6 months to not change very often</p>
<p class="fragment">Try to repeat several projects with the same clients</p>
<p class="fragment">How can we do that and how we can transform our agency to be the <em>perfect one</em> for them?</p>
</section>
</section>
<section>
<section>
<h2>The team</h2>
</section>
<section>
<h2>The team</h2>
<ul>
<li>It's impossible to have all the expertise in our team (cause the size)</li>
<li>Two alternatives:
<ul>
<li>Generalists</li>
<li>Focus in some services</li>
</ul>
</li>
</ul>
</section>
<section>
<h2>Generalists</h2>
<ul>
<li>Our developers, as in SCRUM, won't have any specific area of expertise</li>
<li>They <em>can do</em> frontend or backend</li>
<li>Alike, you will usually have people in your team more specialist in back or front</li>
</ul>
</section>
<section>
<h2>Services</h2>
<ul>
<li>Focus your business in a specific set of services</li>
<li>As more focused in a set of services, your team will transform in more specialists on that</li>
<li>Big clients usually have specific needs in some areas: performance, frontend, etc. Transform your team in a solution for that need</li>
</ul>
</section>
<section>
<h2>Planning your resources</h2>
<ul>
<li>What about deadlines and working peaks with a smal team?</li>
<li class="fragment">Try to adapt your team to the work you usually have</li>
<li class="fragment">Beware the mistake of hiring new developers on working peaks</li>
<li class="fragment">Create a network of collaborators (freelance) and teach them your methodology</li>
<li class="fragment">Use them to solve working peaks</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Sales process</h2>
<p>How to introduce you in that customer type?</p>
<ul>
<li class="fragment">Classic</li>
<li class="fragment">Use same customer type to introduce you</li>
<li class="fragment">Be an expert and then try to be a need for them</li>
</ul>
<p class="fragment">For us, for example, it's easier to enter to a client for IT department instead of marqueting</p>
</section>
</section>
<section>
<section>
<h2>The methodology</h2>
</section>
<section>
<h2>Big in front of small</h2>
<ul>
<li>Usually big clients use classical methodologies into their organization</li>
<li>This involves a lot of "unnecessary" documentation and is usually too slow for our day-to-day work</li>
<li>It can be a pitfall for small agencies</li>
</ul>
</section>
<section>
<h2>Our methodology: internal</h2>
<ul>
<li>Using agile as methodology to organize our development (mandatory in small teams)</li>
<li>User stories in project backlog</li>
<li>Organizing with 2-3 weeks sprints</li>
<li>Retrospective at the end of every sprint to try to prevent pitfalls on development</li>
</ul>
</section>
<section>
<h2>Our methodology: external</h2>
<ul>
<li>Only one person or small group (2-3 people) as contact for the project development (include at least one IT person)</li>
<li>Try to extract all the requirements before starting development</li>
<li>More in depth on requirements during the development</li>
<li>Backlog priorization with the client</li>
<li>Demo meeting after every retrospective meeting with demo test plan for the client</li>
</ul>
</section>
<section>
<h2>Who should change</h2>
<ul>
<li>Clients usually don't use agile in their processes</li>
<li>Adapt their workflow to use agile</li>
<li>Don't try to use all agile techniques in the first project: slow progress during projects</li>
<li>Retrospective at the end of every project to show them the agile positive things (and what need improvement)</li>
<li>Introduce new changes in the methodology for next project</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Working closely</h2>
</section>
<section>
<h2>Closely with managers</h2>
<ul>
<li>As an small agency, you need to remove all the classic layers</li>
<li>Replace sales person for a technical that sales projects</li>
<li>Use plain and direct language</li>
<li>Don't hide problems nor benefits</li>
</ul>
</section>
<section>
<h2>Closely with IT department</h2>
<ul>
<li>Integrate you with the IT department: try to be their conselor</li>
<li>You should not be a simple provider. You must be their helper</li>
<li>Be part of their team</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Culture</h2>
</section>
<section>
<h2>Team culture</h2>
<ul>
<li>How you explain to a client that the team won't work this week for DrupalCon? And DevDays? And DrupalCamp?...</li>
<li>How to explain that you "waist" project time in module fixes and patches?</li>
<li>Be plain in your explanation</li>
</ul>
</section>
<section>
<h2>Project and community</h2>
<ul>
<li>It's a benefit for them to improve Drupal as a platform</li>
<li>Introduce them to the community culture</li>
<li>Help them to create a page in d.o and give credit to the patches and modules developed for them</li>
<li class="fragment">This benefits them into the community too</li>
</ul>
</section>
</section>
<section>
<section>
<h2>Impact in your business</h2>
</section>
<section>
<h2>Finances</h2>
<ul>
<li>Big clients are usually slow on payments or have a very strict process</li>
<li>This can be dangerous for finances in a small agency</li>
<li>Introduce agile in your budgets for large projects</li>
<li class="fragment">Invoice at the end of every sprint or <em>n</em> sprints</li>
</ul>
</section>
<section>
<h2>Team</h2>
<ul>
<li>Developers may end up bored to work in big projects</li>
<li>Be carefull with rotation</li>
<li>Try to combine big and small projects on teams</li>
<li>Involve them in all project phases</li>
<li class="fragment">Motivation is the key</li>
</ul>
</section>
</section>
<section>
<h2>Conclusions</h2>
<ul>
<li>This is not a TODO to follow, is a recipe</li>
<li>Take care of your team</li>
<li>Humanize the relationship with your client</li>
<li>IT department is better than marketing to introduce you</li>
</ul>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// Optional reveal.js plugins
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>