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.
Step 1: Project Requested
STAKEHOLDER submits ticket in YouTrack, or has contacted the BC team about the request.
PROJECT MANAGER creates a kickoff meeting.
Step 2: Kickoff Meeting & Master Tickets Created
Kickoff meeting is held with STAKEHOLDER, PROJECT MANAGER, EDITORIAL, and UX.
Meeting agenda:
- Outline clear goals and success metrics of the new project
- Determine all team members needed to be involved
- Walk STAKEHOLDERS new to our process through the onboarding presentation
- Define scope (if time, a sitemap is created during meeting)
- Define development requirements
- Deadline requirements
- Design requirements
If scope is not finalized during the kickoff meeting or the project is a larger initiative, a discovery meeting is created by UX.
After the kickoff meeting the PROJECT MANAGER...
- Creates a master ticket, a design ticket and a copy ticket based on meeting notes.
- Assigns the design ticket to UX.
- Assigns the copy ticket to EDITORIAL.
- Creates a rough schedule and adds to the master ticket.
- Ensures training meetings are setup for tools (if needed).
- GatherContent (GC) - EDITORIAL trains
- Youtrack - Online self serve training
- Author Training - WEBOPS trains
- Book Training - WEBOPS trains
Step 3: Sitemap Created
UX creates sitemap and adds links to design ticket.
UX informs the PROJECT MANAGER that the GC space can be created.
Step 4: GatherContent Created
EDITORIAL creates GatherContent project based on UX sitemap, adds links to copy ticket and assigns ticket to PROJECT MANAGER.
If any training is required, EDITORIAL arranges a GatherContent training session.
Step 5: 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?]
Step 6: Wireframes Created
UX creates wireframes based on the copy outline and adds links to design ticket.
Step 7: 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.
Step 8: 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.
Step 9: Web Production Tickets Created
PROJECT MANAGER creates web production tickets. This ensures that we don't have a backlog of tickets waiting while content and design are 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.
Step 10: Web Pages Built
WEBOPS builds pages based on designs and GC copy.
WEBOPS adds links to master ticket and lets PROJECT MANAGER know they're ready for a QA review.
PROJECT MANAGER lets EDITORIAL, UX and DESIGN know pages are ready for review.
Step 11: Web Pages Reviewed
EDITORIAL and DESIGN review layout and content to ensure everything matches comps and GC. They provide feedback in appropriate webops tickets.
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 master 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
Step 12: Final Updates
UX, EDITORIAL, DESIGN, and WEBOPS update per feedback and mark as "ready to launch" in appropriate webops ticket.
Step 13: Go No-go and Launching
GO NO-GO
PROJECT MANAGER schedules a "Go No-Go" meeting with all team members including STAKEHOLDER.
This is sometimes combined with the launch call if everything goes well.
Any changes during this meeting should be focused on:
Will Intel get sued if this goes live as is?
Will anyone get fired if this goes live as is?
Is something just plain wrong (typically a spec # or a link is going to the wrong place)?
PROJECT MANAGER, EDITORIAL, DESIGN, UX and WEBPOPS will:
- Check If feeds are showing the right content
- Check If all their changes have been implemented
- Ensure that all documentation and supporting content is pushed live
STAKEHOLDER will:
Check If links are going to the correct location
Anything else should be entered as a post-launch update ticket.
If everything is ready and you have enough time, the Go-No Go meeting can sometimes becomes the launch call.
If the team needs more time, the PROJECT MANAGER schedules a launch call.
THE LAUNCH CALL
All team members attend and review content as it is pushed live.
UX, DESIGN, WEBOPS, PM will:
Check If links work (no 404 errors) Check If last minute changes are complete Check If layout, design, copy is correct. Check If all the redirects are set up
After launch, PROJECT MANAGER holds all tickets for localization while the site stabilizes (typically 2 weeks unless otherwise specified).