Newsroom Articles
Naming convention should be:
Newsroom Article - BUSINESS UNIT: [CAMPAIGN] [DATE OF DROP] Article
Tasks will always be:
Write Draft
Copy Edit
Create Graphic
The graphic task should always have specs: 1200 x 630 for graphicgraphics.
Publish and Post
Share to Social
Example: https://cdamarketing.atlassian.net/browse/COMM-277
The subtasks should always be assigned to the writer - to assign out to designers etc. So if the writer is Joie, assign all tasks and the main job to Joie. If the writer has not been determined, assign to Sarah and she will assign all tasks out.
Digital Graphics
It would be great to create a template for this or use Jira Automation so that anytime a digital asset is created, these questions prepopulate.
The Digital Graphic questions that a designer will always have:
What is the purpose of the graphic? Who is the business line we are serving? Where will the graphic be used?
What are the specs?
What are the mandatory elements that need to absolutely be in the graphic?
Is there copy that needs to be in the graphic? Has copy been created? Does it need to be?
When is the deadline?
Any Task or Story, or Initiative (Epics, too)
Naming convention for subtasks and tasks linked to epics should be:
[TODO] - BUSINESS UNIT: [CAMPAIGN OR LINKED TASK] [DATE OF DROP] (date of drop if applicable, if not, leave out.)
Example: Create Article - CDAP: VM20 Comprehensive Email 3 090820
Another example:Write Up Copy - CDAP: VM20 Platform Leaderboard
Naming convention for tasks, epics and stories that are unlinked or their own thing:
BUSINESS UNIT: [CAMPAIGN] [ITEM] [DATE OF DROP] (date of drop if applicable, if not, leave out.)
Example:CDAP: VM20 Attendees
Another example: CDAF: CDA Cares Clinic 2020
Purpose: Primary audience, challenge, and objectives - the business unit
Brief/Background: 1 paragraph descriptions, current situation & product needed
Deliverables: CTAs, required text, and elements, including specs and sizing
Schedule: Deadline, in-hand date, production schedule
Reference: links to all supporting documents or references (include document paths)
Always be sure to include date/year in epics/stories.