Professional Documents
Culture Documents
Test - Tasks (AutoRecovered)
Test - Tasks (AutoRecovered)
Rename this file by adding your name to the filename. For example, if your name is John
Doe, change the filename to Test_tasks_JohnDoe.
Complete all tasks in the renamed file exactly as instructed. Do not create separate
documents for each test task.
Do not change or delete the instructions given in italics for each task.
Task 1
Explain to an elderly person how to send an SMS using a smartphone.
Step-by-step procedure
No screenshots
Roles’ responsibilities:
1. DM interacts with the customer (gets new tasks, updates the customer on progress, solves
issues), and the publishing team (distributes tasks, controls execution, answers process
questions, serves as a channel of communication with the customer).
2. Publishers create content, check against a checklist, and publish content in a CMS, interact
with each other (QA’ing each others’ tasks, resolving issues), interact with the DM (update on
task completion, ask questions to be directed to the customer, inform of rejected tasks due to
missing information, such as content omissions or lack of metadata), deal with task
iterations, update internal KB on fixes, and so on.
Systems involved: MS Excel tracker for a unified view of all tasks, JIRA to keep track of tasks and
time, SharePoint for keeping customer’s original content, CMS, graphic-editing tools, Confluence.
Desired outcome: a diagram that clearly identifies the happy flow + deals with the most common
extra situations and exceptions, including those that can be inferred from the task description.
Report queries from Publisher and gets response Gets Customer queries and gives response (SharePoint
(SharePoint and Confluence ) and Confluence )
Reports rejected tasks due to missing information and Gets rejected tasks due to missing information and
gets missing info to the publisher (SharePoint and gives missing info after communication with Customer
Confluence ) (SharePoint and Confluence )