Lifecycle of a Drupal Project

V Enter your name in master view www.appnovation.com

Scott Bell– Senior Creative Lead [email protected] - ca.linkedin.com/pub/sco9-‐bell/8/b7a/b64/

LIFECYCLE OF A DRUPAL PROJECT

ATLANTA • BOSTON • LONDON • MONTREAL • NEW YORK • SAN FRANCISCO • VANCOUVER


Appnovation is one of the world’s TOP OPEN SOURCE DEVELOPMENT SHOPS.


SERVING GLOBAL ENTITIES AND REACHING THEM AROUND THE WORLD

CANADA VANCOUVER HQ 300-152 West Hastings St Vancouver BC, V6B 1G8 MONTREAL OFFICE 5455 de Gaspe Avenue, #370 Montreal Quebec, H2T 2A3 UNITED STATES SAN FRANCISCO OFFICE 315 Montgomery St. #800 & 900 San Francisco, CA, 94104 ATLANTA OFFICE 3414 Peachtree Road, #1600 Atlanta Georgia, 30326-1164 NEW YORK OFFICE 845 Third Avenue, 6th Floor, New York, NY 10022 BOSTON OFFICE 225 Franklin Street, 26th Floor, Bostom MA, 02110 UNITED KINGDOM LONDON OFFICE Davidson House, Forbury Square, Reading, RG1 3EU


JUST A FEW OF OUR HAPPY CLIENTS


Appnovation is the only company in the world that is both an Enterprise Select Acquia partner, MuleSoft Partner, and a Platinum Alfresco partner. We also provide community support for the HTML5 based SproutCore framework.

OUR PARTNERS


Those looking for their place in the web development industry Those new to Drupal Freelancers Project Managers Sales people Project Sponsors


•  Get The Project

•  Requirements Gathering

•  Design

•  Development

•  QA

•  Project Management


Get The Project 1


•  Risk / Reward

•  Woo the client

•  Try to get a phonecall

•  Don’t get emotionally attached (yet)

•  Figure out who the decision makers

are and cater your deliverable to

them

•  Do as much as you think is

necessary

•  Wireframes •  Mockups •  Case Studies •  Sitemaps •  IA •  Examples of previous work •  Quote


•  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

•  Google them/ LinkedIn

•  Speak their language

Hint: Killer design skills will help


Gathering Requirements 2


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 CREEP


•  Business Requirements

•  Functional Requirements

•  Technical Requirements

•  Begin with 3 weeks of on-‐site informaLon discovery and requirements gathering


•  Reasons for change

•  Identify bottlenecks

•  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.


•  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?


•  Increase sales on out of season products

•  Improve the checkout process

•  Get more repeat customers

•  Automate tasks to reduce the need for in-person services.

•  Increase monthly subscribers by x%


•  Describes what the system must DO

•  Fullfill business requirements

•  Develop Use Cases

•  Process flows


•  The system must display products marked as featured

•  User story

•  User story

•  The system must support user profiles

•  User story

•  User story

•  The system must display products based on user behavior

•  User story

•  The system must calculate shipping rates based on …

•  User story


•  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 wall

•  Title (goal)

•  Primary Actor

•  Goal (Business Objective)

•  Precondition

•  Priority


TITLE: As a user, I want to handpick products for the homepage PRIMARY ACTORS: AdministraLve users, Content Managers BUSINESS OBJECTIVE: Increase sales on out of season products PRECONDITION: User must be logged in with sufficient privileges PRIORITY: HIGH


•  How the system guides users from point A to point B

-  Publishing Workflows -  User registration -  Checkout Process


•  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

•  Constraints


Design 3


•  OmniGraffle

•  Axure

•  Fireworks

Prototypes IA/Wireframes Mockups

•  Photoshop

•  Fireworks

•  Illustrator

•  TextEditor

•  Axure

•  Frameworks


•  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 contract


Develop 4


•  Developers need to develop •  They don’t like distracLons (meeLngs,

etc) •  Project manager really needs to take

control of things here. •  Lead developers can delegate Lckets


•  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!


•  http://nvie.com/posts/a-

successful-git-branching-

model/

•  Get a ticket

•  Create a branch

•  Work on ticket

•  Push branch

•  Merge into main


Quality Assurance & User Acceptance 5


•  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 TesLng


Project Management 6


•  Project Plan

•  Meeting Invites & Agendas

•  Meeting Minutes

•  Task lists

•  Scope Control

•  Escalation

•  Status Reports

•  The product!


GANTT Chart

•  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?


QUESTIONS?

Thank You For Your Participation!

Your Full Name – Your title [email protected]

ATLANTA • LONDON • MONTREAL • NEW YORK • SAN FRANCISCO • VANCOUVER www.appnovation.com

Lifecycle of a Drupal Project

Technology

Transcript of Lifecycle of a Drupal Project