This has been agile 101 101 puppies and 101 other working titles
101 Exciting Tips ToGet The Site You NeedWhile Saving Time And       Money(And Get That Promotion You  Deserve In The Proc...
Which is pretty much the nonsense title       (or the hook)
I am
Andre Molnar
Drupal
Drupal                 8.5 Years(Has it really been that long? It really has)
Web Application  Developer
Web Application  Developer     13(ish) Years
First Web Page      1994
First Web Page      1994    18 Years Ago
18
18+13
18+13+8
18+13+8=101  years of experience
Freelancer
Currently at
They’re Pretty Cool
They’re Pretty CoolA lot of talks here this year by smart myplanet folks!
Plug
Get Paid to Learn          DrupalMyplanet Academy (see MPD table in the main room)
I’m talking from my  own experience
Tip #1
Always come to workeach day prepared to      be fired
Don’t *try* to get fired
Be willing to do things      differently
We’ll come back to        that
Getting the website     you need
Different from thewebsite you want
Answer this question
Answer this question   Over and over and over again
Why?
Whyare you building this site?
Whydo you want that feature?
Whydo you want it to be exactly the way you specified it?
What is the business     reason?
Good Reasons:
Good Reasons:    Increase sales
Good Reasons:Comply with the law (e.g. accessibility)
Good Reasons:Improve conversion of visitors to customers
Good Reasons:Create awareness around “product X”
Good Reasons:     others?
Bad reasons:
Bad reasons: ummm... I don’t know
Bad reasons:  we want to go viral
Bad reasons:our competition has it we want it too
Bad reasons:Drupal is supposed to solve all our problems
Drupal MIGHT solvesome of your problems
But you need to know in detail which ones
More good reasons:
More good reasons:Its too painful for our staff to use what we have
More good reasons:    Employee satisfaction
More good reasons:      Rebranding
More good reasons:Rebranding (assuming there was a good reason                  for that)
There are far too many  projects where the reason or purpose is     far too vague
For each and everyfeature answer this:
Which will provide the    highest ROI
Return on Investment
For every dollar we      spend
For every dollar we      spend(Because your vendor doesn’t work for free)
how will thefunctionality it buys get us closer to achieving  our business goals?
If you can’t answerthese questions your project is doomed
How many of your have    issued RFPs?
Responded to them?
Request for Proposal
Do:
Do:Have your objectives clearly defined.
Do:Be completely honest
Do:Be completely transparent
Do:Ask tough questions of potential vendors
Do:Ask for examples of work
Do:Ask questions about process
Do:Ask questions about staff
Do:Ask for references
Don’t
Don’ttreat it as a request for quote
Don’t   treat it as a request for quote(if it is, issue a request for quotes)
Don’tthrow in every feature you ever imagined
Doyour homework
Dofind out if your vendor is capable of doing things
Dofind out if your vendor is capable of doing things   (even if you never ask them to do them)
Because you alreadyknow all your ‘whys’      right?
You asked for aproposal, right?
Accept proposals
Accept proposals    Be open to ideas
Don’tuse your RFP as a requirements document that is set in                        stone
Accept that you don’t have all the answers
Accept that you don’t have all the answers         (yet)
Pick a project or product owner
If you are that owner      see tip #1
And all the other tips
Give them the  authority
Give them the  authority  To make decisions
Give them the  authority  To provide answers
Give them theresources (time)
Give them theresources (time)  To work with your vendor
Give them theresources (time)    To be available
Support them
Support themBy getting them answers they don’t have
Support themBy getting them resources they request (data, source                   material etc.)
Maybe its more than   one person
BUT NEVER
EVER
Have a committee
They are too slow
Time is quite literally   money in web   development
Be Agile
Agility matters
I’m not necessarily  talking about AgileSoftware Development     Methodology
Be quick
Adapt to change
Reprioritize on the fly
If a resource is delayed
have the next highest priority item ready        to go
Be aware of AgileSoftware Development
Educate yourself
Many of your vendorswill claim to be Agile
Know what it means
If you choose an Agile        vendor
Be prepared for the      process
NEWS FLASH
NEWS FLASHThat’s what I’ve been doing
NEWS FLASHPreparing you for Agile vendors
But these tips are just as valid for waterfall
Or other processes
But lets talk about Agile     for a moment
Agile Manifesto
...we have come to           value:Individuals and interactions over processes and tools
Don’t do anything forthe sake of sticking to       process
Don’t avoid thingsbecause they don’t fit    your process
Your vendors/clientsare people too. Talk to        them.
...we have come to           value:Working software over comprehensive documentation
For you this is a ROI              question. documentationHow much value does comprehensive               give you?
Compare that to a working website
...we have come to          value:Customer collaboration over contract negotiation
Work with your vendor/client
Communicate
Communicate ALL THE      TIME
CYA, but only as much    as necessary
...we have come to       value:Responding to change, over following a plan
Not everything goes to        plan
Priorities change
Opportunities arise
Higher ROI itemspresent themselves
Be prepared to pivot      quickly
Other Random Tips
MoSCoW
Must HavesShould Haves
Could HavesWon’t Haves
Have good reasons
Be ready willing andable to defend thosechoices to your boss
and to demand them from your vendor
Demand accountability
Demand demos
Regularly
See the progress
Don’t sweat it if designis not pixel perfect in        demos
Don’t sweat it if designis not pixel perfect in             demos like)     (I can tell you why if you
DO demand that software defects arefixed if present in demo
DO demand pixelperfection for launch
Provide feedback often
Provide constructive   feedback often
Know the difference between a defect
and something that isn’tquite how you imagined          it
A defect is something that doesn’t work
or does not meet the required objective
or does not meet the required objective(you know, the ‘why the thing was being done in the                    first place’)
If it works, and meets      the objective
but could be better...
Consider the ROIbefore asking for the       change
Questions?
Horror Stories?
Oh wait...
Puppies
Inspirational Music
Thank You
This has been agile 101 101 puppies and 101 other working titles
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)
Upcoming SlideShare
Loading in …5
×

101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)

384 views
338 views

Published on

Andre Molnar's presentation from Drupal Camp Toronto 2012.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
384
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • 101 Exciting Tips To Get The Site You Need While Saving Time And Money (And Get That Promotion You Deserve In The Process)

    1. 1. This has been agile 101 101 puppies and 101 other working titles
    2. 2. 101 Exciting Tips ToGet The Site You NeedWhile Saving Time And Money(And Get That Promotion You Deserve In The Process)
    3. 3. Which is pretty much the nonsense title (or the hook)
    4. 4. I am
    5. 5. Andre Molnar
    6. 6. Drupal
    7. 7. Drupal 8.5 Years(Has it really been that long? It really has)
    8. 8. Web Application Developer
    9. 9. Web Application Developer 13(ish) Years
    10. 10. First Web Page 1994
    11. 11. First Web Page 1994 18 Years Ago
    12. 12. 18
    13. 13. 18+13
    14. 14. 18+13+8
    15. 15. 18+13+8=101 years of experience
    16. 16. Freelancer
    17. 17. Currently at
    18. 18. They’re Pretty Cool
    19. 19. They’re Pretty CoolA lot of talks here this year by smart myplanet folks!
    20. 20. Plug
    21. 21. Get Paid to Learn DrupalMyplanet Academy (see MPD table in the main room)
    22. 22. I’m talking from my own experience
    23. 23. Tip #1
    24. 24. Always come to workeach day prepared to be fired
    25. 25. Don’t *try* to get fired
    26. 26. Be willing to do things differently
    27. 27. We’ll come back to that
    28. 28. Getting the website you need
    29. 29. Different from thewebsite you want
    30. 30. Answer this question
    31. 31. Answer this question Over and over and over again
    32. 32. Why?
    33. 33. Whyare you building this site?
    34. 34. Whydo you want that feature?
    35. 35. Whydo you want it to be exactly the way you specified it?
    36. 36. What is the business reason?
    37. 37. Good Reasons:
    38. 38. Good Reasons: Increase sales
    39. 39. Good Reasons:Comply with the law (e.g. accessibility)
    40. 40. Good Reasons:Improve conversion of visitors to customers
    41. 41. Good Reasons:Create awareness around “product X”
    42. 42. Good Reasons: others?
    43. 43. Bad reasons:
    44. 44. Bad reasons: ummm... I don’t know
    45. 45. Bad reasons: we want to go viral
    46. 46. Bad reasons:our competition has it we want it too
    47. 47. Bad reasons:Drupal is supposed to solve all our problems
    48. 48. Drupal MIGHT solvesome of your problems
    49. 49. But you need to know in detail which ones
    50. 50. More good reasons:
    51. 51. More good reasons:Its too painful for our staff to use what we have
    52. 52. More good reasons: Employee satisfaction
    53. 53. More good reasons: Rebranding
    54. 54. More good reasons:Rebranding (assuming there was a good reason for that)
    55. 55. There are far too many projects where the reason or purpose is far too vague
    56. 56. For each and everyfeature answer this:
    57. 57. Which will provide the highest ROI
    58. 58. Return on Investment
    59. 59. For every dollar we spend
    60. 60. For every dollar we spend(Because your vendor doesn’t work for free)
    61. 61. how will thefunctionality it buys get us closer to achieving our business goals?
    62. 62. If you can’t answerthese questions your project is doomed
    63. 63. How many of your have issued RFPs?
    64. 64. Responded to them?
    65. 65. Request for Proposal
    66. 66. Do:
    67. 67. Do:Have your objectives clearly defined.
    68. 68. Do:Be completely honest
    69. 69. Do:Be completely transparent
    70. 70. Do:Ask tough questions of potential vendors
    71. 71. Do:Ask for examples of work
    72. 72. Do:Ask questions about process
    73. 73. Do:Ask questions about staff
    74. 74. Do:Ask for references
    75. 75. Don’t
    76. 76. Don’ttreat it as a request for quote
    77. 77. Don’t treat it as a request for quote(if it is, issue a request for quotes)
    78. 78. Don’tthrow in every feature you ever imagined
    79. 79. Doyour homework
    80. 80. Dofind out if your vendor is capable of doing things
    81. 81. Dofind out if your vendor is capable of doing things (even if you never ask them to do them)
    82. 82. Because you alreadyknow all your ‘whys’ right?
    83. 83. You asked for aproposal, right?
    84. 84. Accept proposals
    85. 85. Accept proposals Be open to ideas
    86. 86. Don’tuse your RFP as a requirements document that is set in stone
    87. 87. Accept that you don’t have all the answers
    88. 88. Accept that you don’t have all the answers (yet)
    89. 89. Pick a project or product owner
    90. 90. If you are that owner see tip #1
    91. 91. And all the other tips
    92. 92. Give them the authority
    93. 93. Give them the authority To make decisions
    94. 94. Give them the authority To provide answers
    95. 95. Give them theresources (time)
    96. 96. Give them theresources (time) To work with your vendor
    97. 97. Give them theresources (time) To be available
    98. 98. Support them
    99. 99. Support themBy getting them answers they don’t have
    100. 100. Support themBy getting them resources they request (data, source material etc.)
    101. 101. Maybe its more than one person
    102. 102. BUT NEVER
    103. 103. EVER
    104. 104. Have a committee
    105. 105. They are too slow
    106. 106. Time is quite literally money in web development
    107. 107. Be Agile
    108. 108. Agility matters
    109. 109. I’m not necessarily talking about AgileSoftware Development Methodology
    110. 110. Be quick
    111. 111. Adapt to change
    112. 112. Reprioritize on the fly
    113. 113. If a resource is delayed
    114. 114. have the next highest priority item ready to go
    115. 115. Be aware of AgileSoftware Development
    116. 116. Educate yourself
    117. 117. Many of your vendorswill claim to be Agile
    118. 118. Know what it means
    119. 119. If you choose an Agile vendor
    120. 120. Be prepared for the process
    121. 121. NEWS FLASH
    122. 122. NEWS FLASHThat’s what I’ve been doing
    123. 123. NEWS FLASHPreparing you for Agile vendors
    124. 124. But these tips are just as valid for waterfall
    125. 125. Or other processes
    126. 126. But lets talk about Agile for a moment
    127. 127. Agile Manifesto
    128. 128. ...we have come to value:Individuals and interactions over processes and tools
    129. 129. Don’t do anything forthe sake of sticking to process
    130. 130. Don’t avoid thingsbecause they don’t fit your process
    131. 131. Your vendors/clientsare people too. Talk to them.
    132. 132. ...we have come to value:Working software over comprehensive documentation
    133. 133. For you this is a ROI question. documentationHow much value does comprehensive give you?
    134. 134. Compare that to a working website
    135. 135. ...we have come to value:Customer collaboration over contract negotiation
    136. 136. Work with your vendor/client
    137. 137. Communicate
    138. 138. Communicate ALL THE TIME
    139. 139. CYA, but only as much as necessary
    140. 140. ...we have come to value:Responding to change, over following a plan
    141. 141. Not everything goes to plan
    142. 142. Priorities change
    143. 143. Opportunities arise
    144. 144. Higher ROI itemspresent themselves
    145. 145. Be prepared to pivot quickly
    146. 146. Other Random Tips
    147. 147. MoSCoW
    148. 148. Must HavesShould Haves
    149. 149. Could HavesWon’t Haves
    150. 150. Have good reasons
    151. 151. Be ready willing andable to defend thosechoices to your boss
    152. 152. and to demand them from your vendor
    153. 153. Demand accountability
    154. 154. Demand demos
    155. 155. Regularly
    156. 156. See the progress
    157. 157. Don’t sweat it if designis not pixel perfect in demos
    158. 158. Don’t sweat it if designis not pixel perfect in demos like) (I can tell you why if you
    159. 159. DO demand that software defects arefixed if present in demo
    160. 160. DO demand pixelperfection for launch
    161. 161. Provide feedback often
    162. 162. Provide constructive feedback often
    163. 163. Know the difference between a defect
    164. 164. and something that isn’tquite how you imagined it
    165. 165. A defect is something that doesn’t work
    166. 166. or does not meet the required objective
    167. 167. or does not meet the required objective(you know, the ‘why the thing was being done in the first place’)
    168. 168. If it works, and meets the objective
    169. 169. but could be better...
    170. 170. Consider the ROIbefore asking for the change
    171. 171. Questions?
    172. 172. Horror Stories?
    173. 173. Oh wait...
    174. 174. Puppies
    175. 175. Inspirational Music
    176. 176. Thank You
    177. 177. This has been agile 101 101 puppies and 101 other working titles

    ×