The Infomedia
Project Process

Infomedia's project process life cycle.

Each phase consists of multiple steps. The steps are either processes or milestones. A process is made up of essential steps that must be completed to ensure a successful project.

• Phase 1 - Content
  • 1. Agreement

    Initial document defining scope of work, price, and contractural items

    Responsible Party: Salesman

  • 2. Collecting Assets

    Content Coach is introduced by Project Manager. CC reaches out to client and begins collecting assets (DNS, copy, images, video, etc.).

    Responsible Party: Content Coach

  • 3. Internal Kickoff

    Brief incoming project with all team members.

    Responsible Party: Project Manager

  • 4. Kickoff

    Meeting with client with representation from all aspects of the project.

    Personnel Required

    • Client
    • PM
    • Designer
    • Developer
    • Copywriter
    • Sales

    Responsible Party: Project Manager

  • 5. Content Coaching

    Work with client in early in Phase 1 to attain copy and assets etc.

    Ask For

    • Sites client likes
    • Marketing materials
    • List of competitors

    Responsible Party: Content Coach

  • 6. Defined Scope

    Create document known as the "Defined Scope" to manage and agree with client upon expectations and scope of work.

    Notes

    • Any out of scope items should be upgraded to a “Change Order”, write up the Change Order yourself of 10% commission or take to Clay to spec and upsell.
    • Team discusses allotted hours.
    • Designer’s last chance to contest hours
    • Content Coach informs PM of client approval

    Responsible Party: Team. Content Coach sends to client

  • 7. Site Blueprint

    Formerly known as a "site map". Develop flowchart of site's navigation, page, and content structure.

    Notes

    • Copywriter’s last chance to contest hours
    • Content Coach informs PM of client approval

    Responsible Party: Facilitated by Design. Constructed and approved by team (Design, Dev, Copy and Content Coach). Content Coach sends to client.

  • 8. Copywriting

    Copywriter audits or writes copy regardless of copy purchased or not. Home page & additional. 2 hours max

    Responsible Party: Copywriter

• Phase 2 - Design
  • 9. Create Comps

    Create layered psd's of site designs. We promise the client a certain amount of comps in our "Defined Scope" document, but we require certain comps internally.

    Mandatory Deliverables

    • Homepage
    • Sub-page
    • Mobile
    • Style Guide
    • Favicon
    • Specialized content & Custom Post Type pages
    • Additional details
    • Iconography

    Responsible Party: Designer

  • 10. QC-1

    Discuss design with a developer throughout design to ensure that design is inline with our capabilities, best practices, and time efficient to build.

    Notes

    • Dev approves that site can be built within the allotted hours and scope.
    • If new hours are needed, team is responsible for justification. Team/PM approves new hours

    Responsible Party: Developer

  • 11. Communicate Design

    Send design link to team, Jason, Clay, and Content Coach

    Responsible Party: Project Manager

  • 12. Design Review

    Present site design to client.

    Responsible Party: Project Manager with Team

  • 13. Design Revisions

    Make necessary revisions to the design according to Design Review.

    Notes

    • Up to 2 rounds of revisions

    Responsible Party: Designer

  • 14. Design Approval

    Need written approval (email works) to proceed to Phase 3.

    Notes

    • Project Manager communicates to team that design has been approved

    Responsible Party: Project Manager

  • 15. Handoff to Development

    Designer meets with developer to provide all psd's, assets, etc required to develop.

    Notes

    • This should not the first conversation being had between two parties
    • Dev checks “For Developer” folder for all assets
    • Devs must tell Project Manager if they are missing any deliverables after handoff

    Responsible Party: Designer

• Phase 3 - Development
  • 16. Determine Content Entry Strategy

    Discuss strategy for content entry.

    Responsible Party: Developer

  • 17. Build Site

    Develop site using Infomedia standards and best practices.

    Responsible Party: Developer

  • 18. Content Entry

    Refer content entry strategy and proceed entering agreed upon content.

    Responsible Party: Developer (possibly with others)

  • 19. QC-2

    Designer should review the site and compare it their design comps, and compile a list of necessary revisions that need to be made.

    Responsible Party: Designer

  • 20. QC-3

    PM should assign another developer a task to run “QC-3”, and secondary developer should compile a list of necessary revisions that need to be made. Project developer should have addressed all items listed in QC-3 prior to this point.

    Responsible Party: Developer

  • 21. Dev Revisions

    Make revisions according to Dev & Design QC’s

    Responsible Party: Developer

  • 22. Content Styling

    Designer may style and clean up any content recently entered/imported.

    Responsible Party: Designer

  • 23. QC-4

    Content Coach and Copywriter should run over site checking for missing content, assets, and grammar and spelling errors.

    Responsible Party: Copywriter & Content Coach

  • 24. Site Review

    Present working site to client

    Notes

    • Project Manager communicates to team that design has been approved

    Responsible Party: Project Manager with Developer

  • 25. Final Revisions & Finishes

    Make revisions according to client review. If any items are out of scope a Change Order should be created or items should be voided.

    Responsible Party: Developer

  • 26. Client Training

    Supply client with 1 training prior to launch (Their support package allows them additional trainings)

    Notes

    • Train on basic usage of WordPress and custom functionality

    Responsible Party: Project Manager with Developer

  • 27. Launch Prep

    Launch process begins, these steps must be completed prior to client giving "Go For Launch"

    Items to Address

    • Enter any last minute content, SEO data etc.
    • Designers may QC any newly entered content. All other quality checks by designer should have been dealt with by now.
    • Enqueue minified css/js
    • Remove any non-essential themes and plugins
    • Ensure all system emails are routing to correct users
    • Add spam blocker plugin i.e. Akismet
    • Run link checker (Mac: Integrity)
    • Setup necessary 301 redirects
    • Ensure that we have access to control the DNS

    Responsible Party: Developer

  • 28. Go For Launch

    Developer, Designer, and PM sign off that site is ready to launch. We can/should begin billing for support at this point.

    Responsible Party: Team

• Phase 4 - Launch
  • 29. Launch

    Push that site live.

    Notes

    • Launch in the morning Monday-Wednesday. Be available for emergencies (keep your phone with you at lunch etc.)
    • Must have DNS information at this point
    • Project Manager sends team launch email

    Items to Address

    • Ensure site's LIVE url is added to WO and Infonet
    • Ensure site is "crawlable" by Google (uncheck "Discourage search engines from indexing this site")
    • Setup Google Analytics
    • Setup Webmaster Tools & XML

    Responsible Party: Team

  • 30. Transition to Support

    Project Manager transitions client to support. Send "transition" email

    Responsible Party: Project Manager

  • 31. Cleanup & QC

    Production cleanup after site has been transitioned.

    Items to Address

    • Verify Analytics is setup
    • Have developer check that backups are running (at least 1 day after site launch)
    • Archive Project - Trello, WO, Google Drive (Move drive directory to "Projects - Complete")

    Responsible Party: Support