ePrivacy and GPDR Cookie Consent by Cookie Consent Skip to main content

Project Management FAQ

This is a running & always in-progress document of FAQ and basic information needed to start and manage projects for a P, maintained by Quinn and sometimes updated by PMs.

General Protocols

 

Protocol for responding to clients

Within the working day. If we need more time to investigate, still acknowledge the email within the working day and let the client know that we will get back to them soon. 

 

Protocol for when the client reports an error in their instance

  1. Acknowledge that we have received it 
  2. Try to re-create the error (to verify that it is indeed a platform problem) , or ask for client for link / screenshot of error message 
  3. If it’s problem related to product , report in Slack: #help_product (Note: if it’s a very urgent issue that needs fixed right away and it’s morning Asia timezone, please ping Quinn/ Jana to use urgent email to wake Europe dev team up)
  4. If it’s a problem that can be investigated or fixed by analyst, assign Paymo task to the analyst 
  5. Update the client within 24 hours and once problem is resolved 

 

What is the list of basic information/docs which need to be asked to the client if they want to add a new data source and destination?

 

 

Access & Credentials

 

Share / request credentials with clients or agencies

  1. Request in #help_it for Jan to create a new vault for the client.
    • Typically, for each new project we have a new vault in 1Password c_clientname to share credentials internally 
    • If we are sharing with client we need to create a new one c_ext_clientname
  2. Ask Honza to add client to this new vault through their email 
  3. The Client should receive an email with instructions from 1Password to create an account and leave their password in a secure way.

But what should I do if the client sends credentials over email? 

  1. Copy the credentials over to 1Password
  2. Ask client never to do it over email again 

 

Grant BE / MI access for new users

For Meiro team: Request in #help_it (Slack) and assign it to Jan. It will be granted via Okta. 

For users outside of Meiro team: 

  1. Get written confirmation from client that we can grant access 
  2.  Create a new User

 

Set up 2FA for an account? 

2FA (2 Factor Authentication) is used to enhance security of an account and ensure that only authorised personnel will be able to log in a certain account. When we start a new project, for example, we always create a new dedicated email for client: client@meiro.io  and this email credential is stored in 1Password under the relevant vault. 

Once the email (or similar accounts) is set up, please set up 2FA as follows: 

  1. From your email or user account, go to security setting -> set up 2FA 
  2. Select "Authenticator" option. A bar code will be generated. Take a screenshot of the barcode

     

  3. Go to 1Password record and create a new section with One-Time-Passwordimage-1638507802352.02.21 PM.png
  4. Click on the small barcode logo and the Code Scanner will appearimage-1638507991573.04.14 PM.png
  5. Drag screenshot of the barcode into code scanner

     

  6. Follow the rest of the instruction

 

Components 

 

Request for a new component

You should request for a new component (connector or loader) only when it is defined in the scope of work contracted with a client, not for prospective clients. If unsure, check with Quinn. 

The steps are as follows: 

  1. Ask for access & documentation: 
  • API: API documentation, base URL to access API, API token generated by client
  • Database: credential to log in DB with read-only access, ask if VPN is required / URL needs to be whitelisted, data model/ERD, data dictionary 
  • sample data from the intended data source
  • Fill in the component request form in Zoho (guide here)

Once a component request is received, it will be assessed and development work will be planned for during Dev team’s weekly meeting. 

 

List of existing components

Occasionally you will be asked by sales team for an estimate of project timeline, and it's important to take into consideration time taken to develop a component needed in the project if we don't have it already. 

This is existing components list which is updated by documentation team:  

 

List of Projects using a specific components 

The fastest way is to request from Jan in #help_it (Slack) to pull a list from docker registry. 

 

Confirm feasibility of a component

Sometimes we would get a question from sales team or from client whether we can integrate with a source/destination (provided it's not in the list of existing component - see above). If it's from a prospect (not yet a client) or if there is not commitment from client, there is no need to officially request a component to be built yet.

In this case, please ask Dev team (default person: Pepa) to check the API document to confirm that it's feasible and a standard document (ie. no complexity expected and it should not take significantly more than other components to build). 

 

Project Planning

 

How do I estimate work hours for project planning?

In the initial project planning we will need to estimate work hours (how many Man-Days / Man-Hours it will take to complete certain tasks. Note: 1MD = 8 MH) 

For standard project tasks (initial implementation of projects, with tasks we've done before) we can base on past actual hours spent to estimate. Please refer to this Project | Work Hours estimates document.

Actual hours spent may still vary based on complexity of the project, skills level of the analyst, hosting (on premise or cloud), etc... 

 

Others

 

Adding new client contacts to welcome emails & product newsletters

image-1645095639817.png

Not automated clients I.i.e. Clients with instances on premise or instances not managed by Meiro

>Process to be updated 

Automated clients i.e. Clients with instances on cloud managed by Meiro

  1. SiaPM Fongrequests getsfor newmonitoring URL + password to client's instance from #help_it at the start of the project when requesting for instances to be created
  2. PM will inform Glenn to add the monitoring URL + password of the client's instance to the internal workspace https://mi.internal.meiro.io/workspaces/5
    • Any users fromwho PMslogged whominto instancesthe areCDP notthe automatedfirst fortime will receive welcome emails and product newsletters
    • Sia Fong will create or update MailChimp database with new users.
      1. For Emtek & BCA, it will be added to New Emtek & BCA users - 27 Oct 2021 specifically.
      2. For welcome emails, Sia Fong will tag the emails with "New users - since 1 Sept 2021" tag and emails will automatically be sent
  • Go to MailChimp
  • Click Audience > Select MEIRO.IO GENERAL > Manage Audience > Import Contacts > Copy & Paste or Upload file > select audience, status and check “Update any existing contacts”
  • Choose a tag:
  • Sia Fong will update Karina for product newsletters
  • Karina will send out product newslettersnewsletters. 

 

Automated

  • PM clients

    to check off tasks on Zoho project.

    • List of clients with automation set:set currently

    • cdp.banking.demo.meiro.io
    • cdp.ecomm.demo.meiro.io
    • cdp.internal.meiro.io
    • cdp.bat.meiro.io
    • cdp.chemist.meiro.io
    • cdp.drmax.meiro.io
    • cdp.megapixel.meiro.io
    • cdp.rombii.meiro.io
    • cdp.uem.meiro.io
    1. Respective PM should include this in the 
    2. Sia Fong assigns an analyst to add to workspace
    3. Analyst will load user emails from workspace to MailChimp. Any new emails added after 1 Sept 2021 will automatically receive welcome email.

       

    4. Sia Fong will update Karina for product newsletters
    5. Karina will send out product newsletters

     

    Hosting of Meiro Events 

    What are the steps involved in setting up & hosting Meiro Events? 

    Step 1: Meiro team to create a new server for receiving events from our SDK. Please request this from Jan. At the moment, our product does not have multiple domain support, so if the client has more than one website, we need to create one new server for each website. 

    Step 2: Send the IP address(es) of the newly created server(s) to client. 

    Step 3: Client to set up subdomain for Meiro Events. This ensures first party data collection. 

    Example: if client's website is data.com then subdomain will be me.data.com

    Step 4: Client to Set up DNS record, as explained here. This essentially establish the IP address that should be associated to that domain. So, when an action happens on the website and our Meiro Events SDK captures it, it is sent to the IP address of the server that we created (therefore our analysts can access and ingest that data into the CDP). 

     

    Back to top