project management

89
PROJECT MANAGEMENT Simon Collison Business of Web Design Online Conference 17th August 2010 http://www.slideshare.net/collylogic/presentations

Upload: simon-collison

Post on 28-Jan-2015

2.653 views

Category:

Business


0 download

DESCRIPTION

In this session Simon will share his considerable experience of managing projects; from the initial client meetings to getting sign-off on designs to finally going live, and all that comes inbetween.

TRANSCRIPT

Page 1: Project management

PROJECT MANAGEMENTSimon Collison

Business of Web Design Online Conference17th August 2010

http://www.slideshare.net/collylogic/presentations

Page 2: Project management

Everybody does it differently.This is my way.

Page 3: Project management

Choosing projects

Page 4: Project management

• Instinct and warning signs

• Timescales and phases

• Budgets

• Payment structures

• Analysing anomalies

• Third parties

• Willingness to take bold steps

• Flexibility

• Personalities and experience

Page 5: Project management

Contracts and finances

Page 6: Project management

• Issuing contracts

• Payment staging

• Insurance

• Variation notices

• Adjusting budgets

Page 7: Project management

Client documents

Page 8: Project management
Page 9: Project management

• The original RFP, project sheet or brief

• Sitemaps, wireframes, mind maps

• Spreadsheets and flowcharts

• Pre-prepared content

• Brand guidelines

• Images, downloads and other assets

Page 10: Project management

Specification document

Page 11: Project management

Timescales and deadlines

Page 12: Project management

• Dictating the schedule

• Adding contingency

• Ability to move milestones

• Resources across all projects

Page 13: Project management

Meetings and communication

Page 14: Project management

• In person

• Set-up meetings and workshops

• Skype and telephone

• Email

• Basecamp and other apps

Page 19: Project management

Goal-directed design

Page 20: Project management

• Immovable constants

• Project backbone

• Engaging with the client

Page 21: Project management

Collaboration

Page 22: Project management

• The creative team

• The creative team & the client

• The creative team, the client & the audience

Page 23: Project management

Audience

Page 24: Project management

• Accountability

• User cases

• Audience grouping

• Audience hierarchies

• Tools and techniques

Page 25: Project management

Environment

Experience

Environment

Others

Me

Instruction

Interaction

Page 26: Project management

UnderstandingControl Outcome

Page 27: Project management
Page 28: Project management

http://www.logovisual.com

Page 29: Project management
Page 30: Project management
Page 31: Project management
Page 32: Project management

Features versus Requirements

Page 33: Project management

Methodology

Page 34: Project management

• Waterfall

• Agile

• Sprint

• Freestylin’

Page 35: Project management

Waterfall

Research, process, build, test, launch, pub.

Page 36: Project management

Agile

Research, process, build, test, launch, pub. Learn, repeat, relaunch, pub. Learn, repeat, relaunch...

Page 37: Project management

Sprint

Pub, build, test, launch, pub. Nervous breakdown.

Page 38: Project management

Roadmap

Page 39: Project management

Content

Page 40: Project management

• Content audit

• Content strategy

• Client guidance

• Rules and suggestions

Page 41: Project management

Web writing is...

Good writing adapted to the limits of the web as a medium and the needs of users.

Page 42: Project management

Reflected and Projected Light

Reading on paper, we see light reflected off paper

Computers do not reflect light, they project it.

Thus light is shooting into our eyes, rather than gently reflecting.

As a result, we are not reading in the way we learned...

... we get tired faster.

Page 43: Project management

Other limits...

People read about 25% slower on screen.

Attention span. It is said that users have time to read at most 28% of the words during an average visit; 20% ismore likely.

Scanning. Higher-literacy users are much more likely to scan text on websites than read it in detail.

Findability. Numerous alternative sources of information

Page 44: Project management

User needs...

Trust in the the website and information source.

Brevity and swift delivery of information

Retrieval of key facts and information very quickly.

Understanding the context of the page and website.

Looking for calls to action or next steps.

Email, print or respond to information immediately.

Page 45: Project management

How a visitor decides...

1. Scan the headlines to see what the content is about.

2. Look at the pictures to see what the content is about.

3. If the pictures are compelling, read the captions.

4. If the headlines, pictures, and captions are compelling, read the rest of the copy—if they have time.

Page 46: Project management

Trust and credibility...

Domain name, branding and design.

Links - verification through inbound and outbound links.

Sources - evidence of findings.

Volume - the more you write...

Voice - what are you writing about, and who is it for?

Duration - match length to intended audience and subject.

Credits - about the author and their experience.

Page 47: Project management

Voice...

Your character and nuances of you personality show up in...

• the words you choose• the grammatical choices you make• the phrasing you choose

Ensure your style matches your subject matter. The best writers manage to express their voice or personality across whatever writing style they engage in.

Page 48: Project management

Techniques...

Relevance, Titles and Headings

Blurbs

Pull quotes

Icons, drop-caps and images

Descriptions

Linkage and Sources

Lists

Summarise

Page 49: Project management

Body copy...

• Does the copy get to the point quickly?

• Is the copy shy about the subject?

• Is it easy to respond to?

• Does the copy overcome every objection to replying, leaving the reader with no

choice but to act?

• Does the copy use simple words?

• Does the copy use active language (does it address the site visitor as ‘you’)?

• Is the copy broken down into simple sections and bullet points?

Page 50: Project management

True?

• Website content is internally rather than publicly focused?

• Much of it is copy/pasted from paper and press releases?

• Too many buzzwords, too much jargon and multi-syllable phrasing?

• Too little exploitation of the publishing tools available?

• Not enough organisational pride in publishing the website?

• No shared voice, tone or approach?

• Not enough proofreading or drafting?

Page 51: Project management

AA1000 AssuranceAccountAbility 1000APPG on CSRAssuranceAuditBenchmarkingBest PracticeBrown electricityCarbon NeutralCarbon TradingCause-based or community investingCause Related MarketingCFCs (chlorofluorocarbons)Child LabourClean Development MechanismClimate ChangeCO2 (Carbon Dioxide)CommunityCorporate CitizenshipCorporate GovernanceCorporate Responsibility (CR)Corporate Responsibility IndexCorporate Social ResponsibilityDigital Divide (digital inclusion)DiversityDow Jones Sustainability Indices (DJSI)Earth SummitEco-efficiencyEco-LabelEHS (environment, health, safety)EMAS (Eco-Management and Audit Scheme)EnvironmentEnvironment AgencyEnvironmental FootprintEnvironmental Impact AssessmentEqual OpportunitiesEquator PrinciplesEthical AccountingEthical AuditingEthical BookEthical purchasingEthical screeningEthical tradeEthics

FairtradeGlobal compactGlobalisationGreen electricityHuman RightsImpact areasMarketplaceMillennium Development GoalsNGONot-for-profitOff-Set AgreementPhilanthropyRecycleRenewable EnergyReputation AssuranceResponsible businessShareholder InfluenceSocial Accountability 8000 (SA8000)Social AuditSocial capitalSocial EnterpriseSocial ExclusionSocial FirmSocial InclusionSocial InvestmentSocially Responsible Investment (SRI)Social Return on Investment (SORI)Stakeholder dialogueStakeholdersSustainabilitySustainable DevelopmentTriple Bottom LineVenture PhilanthropyWork-Life BalanceWorkplace

BITC, CR, CSR, 8000, NGO, SRI, SORI, EHS, EMAS, DJSI, APPG, AA1000 etc

Triple bottom lineVenture PhilanthropyGlobal compactEquator principlesEtc...

Page 52: Project management

The Business Action on Economic Renewal Leadership Team guides Business in the Community's work on regeneration and economic renewal.

Page 53: Project management

What should boards do to ensure companies behave responsibly, and why? Both corporate responsibility and corporate governance have climbed the corporate agenda in recent years. But there has been little consideration of how these two areas interrelate or about the specific board contribution to corporate responsibility. Both the Combined Code on Corporate Governance and the new Company Law Reform Bill give directors duties related to corporate responsibility. This report outlines the challenge boards face in fulfilling them, and the actions they can take in order to do so.

Page 54: Project management

Narrative

Page 55: Project management

• A single design direction

• In tandem with Basecamp

• Signals not noise

• Demonstrating a clear direction

• Dedicated staging area

Page 56: Project management
Page 57: Project management

Creativity

Page 58: Project management

• Fast, confident design and build sessions

• Organic collaborative process

• Scrapbooking, moodboards and other tools

• Physical project space

Page 59: Project management
Page 60: Project management

Conventions

Page 61: Project management

• Quality control

• Team conventions

• Benefits of convention

• A reusable package

Page 62: Project management

A base layer of rules and conventions that

act as starting points for HTML, CSS,

JavaScript and CMS for all projects.

Page 63: Project management

• Basic HTML files & naming conventions

• PHP for basic templates prior to CMS integration.

• CSS: Stylesheets, IE-specific, reset, scratch files etc.

• JavaScript: jQuery, onload triggers, transparency support

• Other Assets such as folders for images, Flash etc.

Page 64: Project management

A bumper compendium of cascading CSS

files, naming conventions, modules,

plugins and scripts that ensure any

project will stay on convention, and be

simple for anyone to step into and work

with at any time.

Page 65: Project management

• Allows better collaboration within the team; the designer can jump into the developer’s code and vice-versa.

• Anyone who hasn’t even worked on a certain project can jump in and quickly solve problems because everything is on convention.

• Keeps output fresh and ensures use of best practices.

• Establishes a thoroughly connected layer of base files allowing for swift CSS and JavaScript implementation and other assets.

• Makes life easier for developers and designers... and anyone really

• Helps maintain quality control

Page 66: Project management
Page 67: Project management

• Naming conventions

• HTML & XHTML

• HTML5 ?

• JavaScript

• jQuery & Libraries

• PHP

• Templating

• Wireframing

• IE6, IE7 & IE8

• Reset browser defaults

• CSS Frameworks

• Scratch files

• Mobile & Handheld

• Print stylesheets

• PNG support

• Flash and SWF

• Image folders

• Content Management

Page 68: Project management

Communicating your design

Page 69: Project management

• Sketching

• Prototyping

• Designing in the browser

• Explanations and context

Page 70: Project management
Page 71: Project management
Page 72: Project management
Page 73: Project management
Page 74: Project management
Page 75: Project management
Page 76: Project management
Page 77: Project management
Page 78: Project management
Page 79: Project management

Feedback

Page 80: Project management

• The working prototype

• Soft-launch

• Gauging user feedback

• Private testing

• Iterating the prototype

Page 81: Project management
Page 82: Project management

Sign-off

Page 83: Project management

• Establishing sign-off points

• Personal discussion

• Tools and apps

• Training and documentation

• Testing

Page 85: Project management

Launch

Page 86: Project management

• Preparing all parties

• Checklists and procedures

• Something isn’t right

• When to delay

• Your commitments

Page 87: Project management

Post-launch

Page 88: Project management

• Bug fixing, feature requests and support

• Evaluation

• Documentation and promotion

• Subsequent phases

• Costed phases, quick features, retainers

• Keeping the relationship sweet

Page 89: Project management

Thanks

Simon Collison

http://colly.com@simoncollison

http://slideshare.net/collylogic