4. Red Bull Street Art
•Microsite and mash-up
•Always on Destination
•User Generated Content
•Google Maps API
•HTML/Ajax
•Flash
•Facebook Connect API
•Twitter Auth API
•User Experience
Monday, October 10, 2011
9. Digital Production: the Role of
the Producer
•SOFTWARE AS CONCEPT: Base understanding of
software development, examples.
• PLANNING: Timing,Teams, Documents
• PRODUCING: Ensure collaboration and coordination of
all UX, Design, Assets, and Code - Tools and
Documentation examples
Monday, October 10, 2011
10. SOFTWARE
•Aninteractive system that supports a User
Experience
Monday, October 10, 2011
12. SOFTWARE (on the web)
•Browser
•Application
•Server
Monday, October 10, 2011
13. SOFTWARE (Client and Server)
•Browser Displays Code
•Client Side = Front End: HTML, FLASH
•Server
Side = Back End - Data, Data Processing,
WWW Server OS and Hosting (ISP)
Monday, October 10, 2011
15. SOFTWARE Objects + Connectivity
•Objects in a Browser or Applications
•Connectivity to internet +
•Display and Data
•APIs = (Application Programming Interface) -
objects talk to eachother, and share functionality
•Objects on a device
•SDK (Software Developer Kit) applications talk
to device hardware
Monday, October 10, 2011
16. What Is Digital Advertising?
•Banners (Polite and Rich)
•Interactive and Video
•Websites (Basic, Dynamic, Enterpise)
•Microsites, Facebook Tabs, Youtube Channels
•Applications (Web based, Mobile)
•Facebook Applications, iPhone & iPad
Applications, Android and windows phones and
tablets
Monday, October 10, 2011
28. PLANNING
•Why you need to plan (a lot!): The People,
Documents, and Tools you need to map out an
experience
Monday, October 10, 2011
29. Producer vs. PM Producer
•Producer: Works out of Lead Agency to Manage
Specialist Agency
•ProjectManager: Works out of Specialist Agency,
manages specific resources and tasks... (and Lead
Agency)
Monday, October 10, 2011
30. Digital Planning
Architects Documentation
Interactive
Experience
Code & Asset
integration, and Tools & Services Coders
host
Monday, October 10, 2011
31. Phases - Lifecycle
Project Plan
Discovery
Define
Design
Build Alpha -> Beta ->Gold
QA Testing
Monday, October 10, 2011
32. Planning Arsenal
Documents,
People/ Solutions
Tools &
Resources
Services
The Production Matrix
Monday, October 10, 2011
33. Solutions
•Digital Systems/Platforms
Resources
•Microsites/Flash
•Microsites/NOFLASH
•Tablet apps
•OS widgets/apps •Mobile apps
•Digital Installations
•Banners/Rich
•Banners/Stnd
Time: 6 weeks 6 months and up
Cost: $5-40K $20-200K $100K - $250K $200 and up
Scope [time & cost]
Monday, October 10, 2011
34. Planning the experience
•Creative Development
•Functionality
•Technology
•User Experience
Monday, October 10, 2011
35. Planning: Feasibility Philosophy
•Translate Creative Concept
•Producer Collaborate with experts to reverse
engineer experiences, and verify requirements are
possible
•Always source existing similar examples
•Agree on What it does: Functional Requirements
Monday, October 10, 2011
36. Team
•Associate Producer
•Producer
•Sr. Producer
•Exec. Producer
•Art Director
•Copy Writer
•Information Architect
•Interactive Strategist
•Creative Technologist
•Interaction Designer
•Technology Engineer
•Front End coder HTML, HTML5, xHTML, ajax, ruby on rails, etc.
•Front End coder ASPx
•Front End coder FL
•Front End Coder animation FL
•Back-end Coder - PHP, asp, js, flash, Objective C., etc.
•Back-end Coder Data - MySQL, SQL
Monday, October 10, 2011
37. Team
•Associate Producer
•Producer
•Sr. Producer
•Exec. Producer
•Art Director
•Copy Writer
•Information Architect
•Interactive Strategist
•Creative Technologist
•Interaction Designer
•Technology Engineer
•Front End coder HTML, HTML5, xHTML, ajax, ruby on rails, etc.
•Front End coder ASPx
•Front End coder FL
•Front End Coder animation FL
•Back-end Coder - PHP, asp, js, flash, Objective C., etc.
•Back-end Coder Data - MySQL, SQL
Monday, October 10, 2011
50. Functional Requirements
•How a particular experience functions, what a
system is supposed to accomplish
•A typical functional requirement will contain a
unique name and number, a brief summary, and a
rationale. This information is used to help the reader
understand why the requirement is needed, and to
track the requirement through the development of
the system.
•EG:
Video Player: FF, RW, PAUSE, PLAY, REPLAY,
SCRUB, FULL SCREEN, FEATURE LINK
Monday, October 10, 2011
51. Technical Requirements
•How a system is supposed to accomplish the
functional requirements
•A typical Technical requirement will contain a unique
name and number, and a description of the technical
criteria for a particular funciton
•EG: The dimensions of the site are a minimum of
1024x768, but should elegantly accommodate for
larger browser windows up to 1440x900.
Monday, October 10, 2011
52. Functional & Technical
Specifications
•How a particular experience functions, what a system is supposed to
accomplish
•a specification is a document that clearly and accurately describes the
essential technical requirements for items, materials, or services including the
procedures by which it can be determined that the requirements have been
met. Specifications help avoid duplication and inconsistencies, allow for
accurate estimates of necessary work and resources, act as a negotiation and
reference document for engineering changes, provide documentation of
configuration, and allow for consistent communication among those
responsible for the eight primary functions of Systems Engineering. They
provide a precise idea of the problem to be solved so that they can efficiently
design the system and estimate the cost of design alternatives. They provide
guidance to testers for verification (qualification) of each technical requirement.
Monday, October 10, 2011
53. PRODUCING
•What and how the People, Documents, and Tools
need to work together to create the experience
Monday, October 10, 2011
64. Site Testing: Quality Assurance
•Quality Assurance Plan: Mirrors Functional and
Technical Specs
•Uses wireframes as a guide
•Cycles with site Builds
•Online Bug Tracking Tool protocol - Bugs,
identify, describe, assign, resolve, retest
Monday, October 10, 2011
65. Hosting Specification
•Defines where and how the site will be hosted
•Comply with Client digital governance
•Feasibility of project depends on hosting restrictions
•Ownership of Domain Names and Name Servers
Monday, October 10, 2011
66. How Hosting Works
register.com
Rackspace
www name
servers
ISP: AT&T
Browser
Monday, October 10, 2011
72. Take away Pointers
•Collaborate with experts to plan and produce
•Reverse engineer similar whenever possible
•Invention: No solution is the same, but there are
lots of similarities.
•Verify: It’s OK if it’s never been done, it’s NOT OK if
it can’t be
•Tools enable resources to create a better
experience more efficiently
Monday, October 10, 2011
73. Appendix:
Production Menu Matrix!
Monday, October 10, 2011
