Management Part

Manage the Setup of the necessary development environment/other resources (stage, Git, accesses)

Develop and distribute status reports (as identified in the Communication Plan)

Manage project’s issues, risks and changes. Take appropriate action as necessary

Update documentation/Baseline/Schedule along the way when necessary

Monitor and Document items for Lessons Learned – Best practices

Daily/weekly statuses

Conduct Retrospectives

Manage the Team’s issues, risks, changes (1-on-1’s)

Do iterative Estimating and Planning (choose one of the techniques)

Monitor Metrics/ adjust processes

Present an overview of every sprint before starting

Report about the updates after the release, perform a demo after the end of every sprint. Ideally, the team-lead takes part in a demo with the client.

Technical Aspects

Set up a stage access to for the client

Stablish monitesation strategy from a customer

Connect a domain name + access to the domain

Mailchimp setup (create the account & letter template, receive api key & list ID)

SMTP configuration for email sending

When transferring a client’s database to our stage server, check if there are any triggers that automatically send mailing to users

After moving the site to live, delete test users and change passwords in WP / admin-panel; change test emails to client’s emails

Create the accounts for the clients

Determine the optimal transfer time and make sure it is not Friday

Receive all accesses (cPanel, ftp, phpMyAdmin, etc)

Prepare the backup – rollback plan

Transfer file database in advance

Check cookies popup

Add client’s email to the contact forms

Check redirects www/http/https

Update the database for the presence of hard links from the stage (the same applies to emails)

Set up 301 redirects

Transfer & check NS for emails

Check SSL Secure http://prntscr.com/pwuqip

Use cacher (Gzip & Cache)

Create 404 page

Asset minification

Asset compressions

SEO

Clarify what methods of website promotion the customer plans to use (focus on our SEO checklist)

Copy (find out) all tracking codes and links with third-party services and install

Propose to use Hotjar for error analysis

Check h1/h2/h3 (h1 should be bigger than h2, etc)

Help with Google Analytics setup

Google Ads setup

Setup webmaster tools

index vs no-index – remind the client about the indexing of the site in Google Webmaster tools, after transferring the project to live. – https://prnt.sc/10zx5z1

Implement pagespeed guidelines

Record page speed stage + after go-live

Add Sitemap & Robots.txt + send to google Sitemap

Check OG markup and structured data markup

Checking for errors in Search Console after reindexing

Add meta-titles and descriptions

Discovery Checklist

Identify & Interview the Stakeholders:

• Get their vision/initiate the process of setting goals for the project

• Get their vision/initiate the process of setting Success Criteria for the project

• Document in main project doc. their overall expectation for the project, which will have to be managed in the future

Choose the Project Management Approach towards the project, approve with stakeholders and sponsor

Identify who & where (Slack, email) will receive updates on the project and when (Communication/Reporting Plan)

Identify how to communicate the changes from customer to PM (slack, email, etc.)

Determine a set of Metrics to track

Conduct Event Storming/User Story Mapping

Design Checklist

Site structure

Resolutions + Mobile/tablet version

UI kit

Exportable assets

SVG icons

Fonts (paid or free/google fonts link or archive)

Animations

Email templates

404 page

Thank you page

Website under construction page (if needed)

Check images & fonts licences

Notifications styles (error messages, popup,..)

Favicon

Project Planning

Create checklists

Determine QA criterias

Create a Project Space in Confluence to store all developed documentation:

• Project Charter (link to template)

• Change/Issue/Risk Management ()

• Internal/External Reporting (link to template)

Create Slack channel for internal communication

Create a project in Jira

Hold a Technical Analysis meeting after designs are approved:

• It’s has to be done by the Tech Lead, who is appointed by CTO (or/and CTO himself), and with the Product Lead support, appointed by the VP of Product.

• The result of this meeting should be a detailed understanding of how this project will be developed from technical point of view, and what technical risks will be present.

Finalize the Scope, create backlog in Jira

Create Milestone Breakdown and Schedule for the project (Baseline):

• This should be done with the team, via in person meetings. Make sure Product Lead is synced with project Sponsor on the priorities and vision for the project. Breakdown the project into milestones, estimate the activities, and develop project schedule.risks

• The people who will be execution the project – should estimate it

• Estbalish budget for project

• Establish a deadline

Get content from the customer (text, images, etc)

Go to Prod strategy:

• Offer the hosting configuration support, best options for the hosting (WPengine, DigitalOcean)

Establish change proces (design change,etc)

Kickoff Meeting (by PM and client):

• Present development plans with objectives and milestones for the project (timeline, iterations) in a standardised format. Possibly get the client acquainted with the team-lead.

ON TRACK

10/11/21

10/11/21

100h

50h

WITH RISK

10/11/21

10/15/21

100h

50h

DELAYED

10/08/21

10/18/21

100h

50h

Issue: Missing designs for Phase 2.0

RESOLUTION IN PROGRESS

This will have an impact on the ETA for Phase 2.0

Follow up with the customer to provide design ASAP.

Risk: 3rd party library

HIGH RISK

This might have an impact on the project timeline

Do a SPIKE to investigate and update estimation on library implementation

Change Requests:

Additional requirements for Phase 2.0

EVALUATION IN PROGRESS

budget increase for 20h

Confirm budget, timeline and scope changes with the client after evaluation.

• PM acts as the face of the campaign in front of the client, therefore, high-quality communication is the key to successful cooperation

• Motivating, supporting and guiding the project team

• Mentoring others in the area of project management

• Promptly respond to any client’s requests

• Coordinating the development of design and software solutions, taking full ownership of the process if needed

• Continually monitoring and improving delivery quality against best software development practices

• Understanding the business of our clients, and working in a way to help them grow and succeed through our services

• Have a proper technical knowledge allowing smooth communication with developers, product designers and QA specialists

• Reviewing and improving the current processes, creating new ones, implementing novel tools and solutions

• Assisting our clients in making key decisions at every stage of product development

• Backlog management (acting as Product Owner)

• Check, track and predict developers workload

• Using data and appropriate metrics to drive your decisions and improve your projects

• Agile / Lean delivery champion (acting as Scrum Master)

• Visibility/Transparency on overall Program & individual project’s status & plans (roadmap, milestones, etc)

• Being ready to face unpredictable situations and coming up with the best possible solutions

• Dependency Management

• Resources allocation/Capacity Management;

• Have a good command of written and spoken English

• Risks escalation & management

• Visibility/Transparency on overall Program & individual project’s status & plans (roadmap, milestones, etc)

• Change management

• Be proactive in providing updates and project status.

• Visibility/Transparency on Commitment’s status & plans

• Release Cycles management;

• SDLC management and improvement

• Execution, delivering on time, on scope, quality

• Removing impediments within day to day work