Lifecycle of a Drupal Project

2,807
-1

Published on

Presentation slides by Scott Bell from his Drupal Camp Vancouver 2012 session

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,807
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Lifecycle of a Drupal Project

  1. 1. presents Lifecycle of a Drupal Project Scott Bell – Senior Creative Lead scott@appnovation.comScott Bell V Saturday June 2, 2012
  2. 2. •  Those new to the Web Industry •  Those new to Drupal •  Freelancers •  Project Managers •  Pretty much anybody * Based on Waterfall, but most of it applies to Agile projectsScott Bell V Saturday June 2, 2012
  3. 3. •  Introduction / About Me •  Get The Project •  Requirements Gathering •  Design •  Development •  QA •  Project ManagementScott Bell V Saturday June 2, 2012
  4. 4. •  Hobby and user of <blink><table> •  Netscape, Mosaic, Lycos, Infoseek •  1994 14.4k Modem •  I have the lowest ICQ number out of most people I know. (2791847) •  BCIT I’m from Edmonton. •  At Appnovation since 2008 (4 years) I love the Oilers. Say what you want. •  Designer, Developer, Project Manager, Business AnalystScott Bell V Saturday June 2, 2012
  5. 5. What we useScott Bell V Saturday June 2, 2012
  6. 6. Some of Our ClientsScott Bell V Saturday June 2, 2012
  7. 7. Scott Bell V Saturday June 2, 2012
  8. 8. •  Risk / Reward •  Wireframes •  Woo the client •  Mockups •  Case Studies •  Try to get a call •  Sitemaps •  IA •  Don’t get emotionally attached (yet) •  Examples of previous work •  Figure out who the decision makers are and cater your deliverable to them •  Do as much as you think is necessaryScott Bell V Saturday June 2, 2012
  9. 9. •  Are they Technical people nor not? •  Are they product owners? •  Who makes the final call? •  Does the decision come from higher up? •  Find out by asking •  Find out by being inquisitive •  Google It •  Take a wild guess! Hint: Killer design skills will helpScott Bell V Saturday June 2, 2012
  10. 10. Scott Bell V Saturday June 2, 2012
  11. 11. CLIENT: I want a basic e-commerce site YOU: Great, Ubercart should give you what you need! CLIENT: It works great, but can you do me small favor? I forgot to mention that on odd numbered days we ship internationally for the price of domestic shipping except when the shipment weighs over 15lbs and it’s raining. YOU: That wasn’t in the original requirements that you signed off on, so I’ll put together a change request SCOPE CREEPScott Bell V Saturday June 2, 2012
  12. 12. •  Business Requirements •  Functional Requirements •  Technical RequirementsScott Bell V Saturday June 2, 2012
  13. 13. •  Requirements for business users such as customers, employees, vendors. •  Reasons for change •  Success factors for the future •  To gain agreement with stakeholders •  Provide a foundation to communicate •  Provides input into the next phase(s) •  Describe what not how customer/business needs will be met by the solution.Scott Bell V Saturday June 2, 2012
  14. 14. •  Why? •  Why? •  Why? •  Why?Scott Bell V Saturday June 2, 2012
  15. 15. •  What are your goals in developing this system? •  How will the system change the way you are currently doing things? •  How will the system help you be more efficient? •  What are your current problems? •  What do you do manually that you would like to automate? •  What types of reports do you need? •  Who will be using the system? •  What is most important for the success of the application?Scott Bell V Saturday June 2, 2012
  16. 16. •  Increase sales on out of season products •  Improve the checkout process •  Get more repeat customersScott Bell V Saturday June 2, 2012
  17. 17. •  Describes what the system must DO •  Fullfill business requirements •  Develop Use Cases •  Process flowsScott Bell V Saturday June 2, 2012
  18. 18. •  The system must display products marked as featured •  The system must support user profiles •  The system must display products based on user behavior •  The system must calculate shipping rates based on …Scott Bell V Saturday June 2, 2012
  19. 19. •  Title (goal) •  Primary Actor •  Goal (Business Objective) •  Precondition •  Priority •  As the admin, I want to handpick products for the homepage •  As a user, I want to upload a profile picture •  As a user, I want to comment on a product •  As a user, I want to share a product on my facebook wallScott Bell V Saturday June 2, 2012
  20. 20. TITLE: As a user, I want to handpick products for the homepage PRIMARY ACTORS: Administrative users, Content Managers BUSINESS OBJECTIVE: Increase sales on out of season products PRECONDITION: User must be logged in with sufficient privileges PRIORITY: HIGHScott Bell V Saturday June 2, 2012
  21. 21. •  How the system guides users from point A to point B -  Publishing Workflows -  User registration -  Checkout ProcessScott Bell V Saturday June 2, 2012
  22. 22. •  The system must process payments in 12 seconds or less •  System downtime is only acceptable between 2AM – 4AM Sunday morning. •  The System must handle large spikes in traffic •  Non-functional requirements •  Quality of Service requirements •  ConstraintsScott Bell V Saturday June 2, 2012
  23. 23. Scott Bell V Saturday June 2, 2012
  24. 24. Scott Bell V Saturday June 2, 2012
  25. 25. Scott Bell V Saturday June 2, 2012
  26. 26. IA/Wireframes Mockups Prototypes •  OmniGraffle •  Photoshop •  TextEditor •  Axure •  Fireworks •  Axure •  Fireworks •  Illustrator •  Fireworks •  DreamWeaverScott Bell V Saturday June 2, 2012
  27. 27. Scott Bell V Saturday June 2, 2012
  28. 28. Your nameScott Bell V Saturday June 2, 2012
  29. 29. Your nameScott Bell V Saturday June 2, 2012
  30. 30. Your nameScott Bell V Saturday June 2, 2012
  31. 31. Your nameScott Bell V Saturday June 2, 2012
  32. 32. Your nameScott Bell V Saturday June 2, 2012
  33. 33. Your nameScott Bell V Saturday June 2, 2012
  34. 34. Your nameScott Bell V Saturday June 2, 2012
  35. 35. Your nameScott Bell V Saturday June 2, 2012
  36. 36. Your nameScott Bell V Saturday June 2, 2012
  37. 37. Scott Bell V Saturday June 2, 2012
  38. 38. Your nameScott Bell V Saturday June 2, 2012
  39. 39. Your nameScott Bell V Saturday June 2, 2012
  40. 40. Your nameScott Bell V Saturday June 2, 2012
  41. 41. Your nameScott Bell V Saturday June 2, 2012
  42. 42. •  Don’t send your raw files to the client •  Organize your layers (http://photoshopetiquette.com/) •  Be prepared to explain your decisions (Don Draper) •  Use separate PSD files for each page •  Be pixel perfect – Use grid system •  Make a working prototype (static HTML) to communicate intended behavior (animations, hovers, responsiveness) •  Wireframe EVERY page (sitemap) •  Mockup KEY pages •  Specify the number of revisions in the contractScott Bell V Saturday June 2, 2012
  43. 43. Scott Bell V Saturday June 2, 2012
  44. 44. Scott Bell V Saturday June 2, 2012
  45. 45. Scott Bell V Saturday June 2, 2012
  46. 46. •  Set up code repositories (GIT / SVN) •  Set up environments (local, dev, staging, prod) •  Work with PM to create task lists •  Documentation / Training Material •  Demos •  The product!Scott Bell V Saturday June 2, 2012
  47. 47. Scott Bell V Saturday June 2, 2012
  48. 48. •  Test plan derived from FRD / Use cases •  Bug Tracking system (Bugzilla, Jira) •  Test in all major browsers, on windows, mac, mobile, tablet •  Delivers internally tested product to client for UAT •  UAT = User Acceptance TestingScott Bell V Saturday June 2, 2012
  49. 49. Scott Bell V Saturday June 2, 2012
  50. 50. Scott Bell V Saturday June 2, 2012
  51. 51. Scott Bell V Saturday June 2, 2012
  52. 52. Scott Bell V Saturday June 2, 2012
  53. 53. •  Project Plan •  Meeting Invites & Agendas •  Meeting Minutes •  Task lists •  Status Reports •  Demos •  The product!Scott Bell V Saturday June 2, 2012
  54. 54. •  What is the work that will be performed on the project? •  What are the deliverables? •  Who is involved and what are their responsibilities? •  What is the project timeline? •  What are the Milestones? GANTT ChartScott Bell V Saturday June 2, 2012
  55. 55. Scott Bell V Saturday June 2, 2012
  56. 56. Scott Bell V Saturday June 2, 2012
  57. 57. •  Milestones •  Changes •  Existing – Things that have been accomplished •  Time Spent (PM, Designer, Developer, QA) •  Invoicing (invoice #, date, amount) •  Recent Tasks •  Next Week Tasks •  Risks & Issues (Description, Mitigation/Impact, Status) •  DecisionsScott Bell V Saturday June 2, 2012
  58. 58. Questions?Scott Bell V Saturday June 2, 2012
  59. 59. Thank You! From Appnovation Technologies Scott Bell – Senior Creative Lead scott@appnovation.comScott Bell V Saturday June 2, 2012

×