IDZ Production Workflow - New Project

Nullam id dolor id nibh ultricies vehicula ut id elit. Nullam quis risus eget urna mollis ornare vel eu leo. Donec id elit non mi porta gravida at eget metus. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum.

Project Requested

STAKEHOLDER submits ticket in YouTrack or has requested a new space on IDZ.

PROJECT MANAGER creates a kickoff meeting.

 

Kickoff Meeting & Master Tickets Created

Kickoff meeting with STAKEHOLDER, EDITORIAL, and UX to define scope of project and schedule.

If scope is not finalized, a discovery meeting is set to define scope. If scope is finalized, the following artifacts are created:

• Master Ticket created with the following structure (please duplicate this EXAMPLE MASTER TICKET):
  • Overview Scope
    • New/migration/content update?
    • No. of pages (approx)
  • Stakeholders
  • BC Team
    • PM assigned
  • Site Content
    • Sitemap
    • GatherContent
    • Wireframe
    • Design Comps
    • Preview URL section
  • Schedule
    • Initial schedule is created and validated offline
    • Training meeting setup for tools (if needed)
      • GatherContent
      • Youtrack
      • Author Training
      • Book Training

 

Sitemap Created

UX creates sitemap (this sometimes happens in kickoff, but may need to be post meeting) and adds links to master ticket.

Example:

[insert image of sitemap]

 

GatherContent Created

EDITORIAL creates GatherContent project based on UX sitemap, adds links to copy ticket and assigns ticket to PM.

If any training is required, EDITORIAL arranges a GatherContent training session.

 

Content Outline Created

STAKEHOLDER adds a content outline to GatherContent. This will help inform the wireframes and copy guidance.

STAKEHOLDERS provide all visual assets for DESIGN team to reference.

Example: [link to a GC space with an example?]

 

Wireframes Created

UX creates wireframes based on the copy outline and adds links to design ticket. 

 

Copy & Initial Design Comps Created

STAKEHOLDER adds copy to GatherContent and obtains all team and legal reviews or approvals. This copy should be created according to design layout, trademark and branding, and style guidelines.

Copy should be at 90% complete.

PROJECT MANAGER watches status of GC and alerts EDITORIAL when copy is ready for editor review.

 

AT THE SAME TIME...

DESIGN creates comps based on the wireframes and content outline. If there are any issues, DESIGN waits till the initial copy has been added to GC (for problematic pages). DESIGN updates the design ticket.

DESIGN presents comps to STAKEHOLDER for validation.

 

Copy Review

EDITORIAL updates workflow status in GatherContent through all stages of editing, and then changes status to “Approved” when complete.

EDITORIAL informs design if any issues may be present.

EDITORIAL updates copy ticket with appropriate information and assigns to PROJECT MANAGER.

During the time EDITORIAL is reviewing final content, DESIGN should verify that no changes are needed to the design comps.

If excessive changes are required, DESIGN lets the PROJECT MANAGER know.

If design comps are good to go, DESIGN preps assets for upload and assigns design ticket to PROJECT MANAGER.

 

Web Production Tickets Created

PROJECT MANAGER creates webops tickets at this point. This ensures that we don't have a backlog of tickets waiting while content is being finalized.
PROJECT MANAGER informs DESIGN and EDITORIAL and requests they add assets and GC links to appropriate tickets.

PROJECT MANAGER assigns tickets to WEBOPS.

 

Web Pages Built

WEBOPS builds pages.

WEBOPS adds links to design ticket and sends pages to UX and EDITORIAL for a QA review before stakeholder review.

 

Web Page Reviews

EDITORIAL and DESIGN review layout and content to ensure everything matches comps and GC.

Once Complete,DESIGN & EDITORIAL inform the PROJECT MANAGER.

The PROJECT MANAGER sends links to STAKEHOLDER for review and updates master ticket with details.

STAKEHOLDER reviews links in design ticket and feedback (changes are limited to legal or factual errors) is provided in the following tools:

GatherContent for copy changes YouTrack Master Ticket for all other changes

 

Final Updates

UX, EDITORIAL, DESIGN, and WEBOPS update per feedback and mark as "ready to launch" in appropriate webops ticket.

 

Go No-go and Launching

PROJECT MANAGER schedules a "Go No-Go" meeting with all team members including STAKEHOLDER.

Any changes during this meeting should be focused on

Will we get sued if this goes live? Will the STAKEHOLDER get fired if this goes live? Is some fact just plain wrong?

 

PROJECT MANAGER holds all webops tickets for localization while the site stabilizes (typically 2 weeks unless otherwise specified).

If links work and are correct If content is correct If last minute changes are complete If all the redirects are set up

WEBOPS makes as many changes as they can during this meeting.

Sometimes the Go-No Go meeting becomes the launch call if there are no issues with content and the pages have no embargo date.

The PROJECT MANAGER schedules a launch call (if one isn't already scheduled).

THE LAUNCH CALL
All team members attend and review content as it is pushed live.

Team will check:

If links work and are correct If content is correct

• If last minute changes are complete
• If all the redirects are set up

 

PM holds all webops tickets for localization while the site stabilizes (typically 2 weeks unless otherwise specified).