| A | B | C | D | E | F | G | |
|---|---|---|---|---|---|---|---|
1 | |||||||
2 | The "Event Tracker Format" is a template for data tracking requirement that involves product managers, engs and data team | ||||||
3 | The format is designed in detail and it is rather exhaustive, as it is aimed for collaborative document across functions | ||||||
4 | We shows an implementation on filling the tracking requirement, from one of products at Merdeka Mengajar Platform | ||||||
5 | |||||||
6 | |||||||
7 | |||||||
8 | The guiding principals | ||||||
9 | * Saving all footprints, with no deletion | ||||||
10 | * Setting clear expectation and details per role | ||||||
11 | * Helping to smoother the tracking development | ||||||
12 | |||||||
13 | |||||||
14 | |||||||
15 | Role and accountability on each column | ||||||
16 | Responsible | Responsible to initially fill the column | |||||
17 | Review | Responsible to review the column and change according to their expertise in the same column | |||||
18 | Review in different col | Responsible to review the column and change according to their expertise in the different column | |||||
19 | Agree | Must agree or accepting the value on the column. If not, raise your concern to the responsible role | |||||
20 | Consulted | To be consulted when create context for respective column | |||||
21 | Informed | Only be informed or aware of the context of respective column | |||||
22 | |||||||
23 | |||||||
24 | Explanation of Each Column | ||||||
25 | Column | Role and Responsibilities | Explanation | ||||
26 | Team | PM: Responsible Data: Informed Eng: Informed SQA: Informed | The team that develops the event | ||||
27 | Platform | PM: Responsible Data: Informed Eng: Informed SQA: Informed | Platform where the event being developed Examples: Android Apps, iOS Apps, PWA, Web | ||||
28 | Epic | PM: Responsible Data: Informed Eng: Informed SQA: Informed | One big chunk of a feature or product flow (need review from product) | ||||
29 | Development Type | PM: Responsible & Agree Data: Review & Agree Eng: Review & Agree SQA: Review & Agree | Tracker development type per param, options: "Creation": new param/event, no existing event/param. If this is a new event, then all row would be "Creation" "Deletion": delete an existing event/param "Update": update an event/param, for example: change trigger, update value definition | ||||
30 | Flow Class | PM: Responsible & Agree Data: Review & Agree Eng: Informed & Agree SQA: Informed | A certain flow in user journey to group some events. Example: Pemberian akses akun | ||||
31 | Screen when event triggered | PM: Responsible & Agree Data: Review & Agree Eng: Informed & Agree SQA: Informed | A screenshot of certain screen when the event is expected to be triggered. The aim of this section to give clear picture or indication on the exact part for the tracked-event | ||||
32 | Trigger General | PM: Responsible & Agree Data: Review in different col & Agree Eng: Informed & Agree SQA: Informed | A trigger expected from an event. Filled by PM only | ||||
33 | Trigger collecting | Data: Responsible & Agree PM: Decide & Agree Eng: Informed & Agree SQA: Informed | A trigger when start to collect data tracker. Example: the event is form confirmation, but we want to record time when user fill the form, then the trigger collecting would be "form starting to be filled by user". If the event is collected and sent at the same trigger, then you can fill this field similar with "Trigger sent" field | ||||
34 | Trigger sent | Data: Responsible & Agree Eng: Informed & Agree PM: Informed & Agree SQA: Informed | A trigger when the event is expected to be sent | ||||
35 | Goal | PM: Responsible & Agree Data: Review & Agree Eng: Informed & Agree SQA: Informed | A statement of purpose for this event, i.e. the information that will be known by implementing this tracker | ||||
36 | Simple event name | PM: Responsible Data: Review in different col Eng: Informed SQA: Informed | A proposed-event-name from PM, no convention needed | ||||
37 | Fixed event name | Data: Responsible & Agree PM: Informed & Agree Eng: Informed & Agree SQA: Informed | A proposed-event-name from the data team. Prerequisite: an event tracker convention name | ||||
38 | Param | Enging: Responsible Data: Informed & Agree PM: Informed & Agree SQA: Informed | The reviewed-param, naming should follow convention naming | ||||
39 | Param description | Enging: Responsible Data: Informed & Agree PM: Informed & Agree SQA: Informed | The reviewed description param | ||||
40 | Param data type | Enging: Responsible Data: Informed & Agree PM: Informed & Agree SQA: Informed | The reviewed data type of param | ||||
41 | Param example | Enging: Responsible Data: Informed & Agree PM: Informed & Agree SQA: Informed | The reviewed data value, all possible predefined value must be listed | ||||
42 | Eng Confirmation | Enging: Responsible Data: Informed & Agree PM: Informed & Agree SQA: Informed | A confirmation from Enging related to the possiblities on the implementation on each param | ||||
43 | SQA latest tested date | SQA: Responsible Enging: Informed & Agree PM: Informed Data: Informed | Latest tested date for each param, filled by SQA | ||||
44 | PM PIC | PM: Responsible Data: Informed Eng: Informed SQA: Informed | PM person's name as the PIC | ||||
45 | Data PIC | Data: Responsible PM: Informed Eng: Informed SQA: Informed | Data person's name as the PIC | ||||
46 | Eng PIC | Eng: Responsible PM: Informed Data: Informed SQA: Informed | Eng person's name as the PIC | ||||
47 | SQA PIC | SQA: Responsible PM: Informed Data: Informed Eng: Informed | SQA person's name as the PIC | ||||
48 | |||||||