Involving Team-leads (Project process)

Estimation phase

• PMs, devs should read the incoming documentation very carefully. Developers need to understand all inputs.
  PMs should understand and highlight what they think are important points (step-by-step forms, integration, personal account) – add this points as a comment to involve Team-lead (internal estimation)

• In the case that some functionality is not clear, raises doubts or risks, the developer MUST inform the Project Manager about it. After that, the PM organizes a call with the Team leader and the developer

• Approval of a detailed estimate must always be confirmed by Team-lead

Pre-development phase

• Team leaders MUST be involved in the first kick-off call

• Team-lead MUST create environment (Git / stage) for the project

• Team leaders are involved in the project for consultation when the functional work will begin, which causes risks or difficulty of implementation

• When changing the tech-requirements on the project, PM MUST to notify the Team-lead immediately

Development phase

• Team-lead MUST be involved to the Code Review (by pages / particular parts of the scope)

• PM should gather a list of all plugins and components for the project and send it to Team-lead for approve

• Team-lead should participate in Daily meetings (ONLY in case some functionality scope is discussed or tech issues appear)

Go-live phase

• Before Go-live Team-lead should receive from PM all access details needed for transfer:
  – Domain control panel (if it needs to be parked on another hosting)
  – Production server
  – Hosting control panel
  – SSH\SFTP\FTP
  – Database
  – Access to product services (ex. Hubspot, Mail Chimp)
  Team-lead MUST check all accesses and let PM know if something is missed or not working

• Team leader MUST be involved in going-live process