Incident reduction process flow (Sophia’s offer)

Proper Resource Allocation

• PM should add a note to the “Requests” tab in the Workload file about planned start date of the project and its details

• On the Workload call, PMO should assign proper resources for the project (depends on the devs skills & workload)

• Team-leads should approve the dev team assigned to the project

INITIAL SETUP

–

PMO / Team-leads

At the start of each project, with ongoing adjustments as needed

External Kick-off call

• External kick-off call should be arranged by PM at the beginning of the project

• PM & Client should participate on the call (Team-lead could be included if needed)

• All points discussed on the call should be documented

DISCOVERY

Сheck-list for client’s briefing
SOW

PM

At the start of each project

Internal Kick-off call

• Internal kick-off call should be arranged by PM at the beginning of the project

• PM, Dev team, QA, Team-leads should participate on the call

• PM should be prepared to introduce the project goals & scope, design, client needs to the team

• Team-leads should make their conclusions about complexity of the functionality: discuss with the team all difficulties which could happen, pick the right methods and make sure FE, BE devs follow TL instructions/vision

• After all technical details are cleared, the features should be precisely estimated with the whole team, timeline should be created/updated accordingly

DISCOVERY

• Project passport

• Added feature/s development decisions to SOW

• Updated Timeline

PM

At the start of each project

Estimate

Project setup

• PM should make decomposition of the features, all features should be well described (consulted with devs or TL)

• PM should add issues to the Jira with all estimates and deadlines

• TL has to make sure project setup correctly with stage/Git/..

DEVELOPMENT

Project setup check-list

PM / Team-leads

One-time setup, periodic review as needed

Communication procedures & tracking of the progress

• PM should conduct daily meetings with the team, checking devs progress, involving and updating TL if needed

• All decisions / notes discussed on the calls should be documented in the Meeting notes

• Weekly reporting by Team-leads regarding tech details of the projects where TL was involved to notify management & PMO

DEVELOPMENT

• Meeting notes

• Updated SOW

• Weekly reports

PM / Team-leads

Continuously

Documenting changes

• All technical decision changes made by team must be approved by TL

DEVELOPMENT

• Updated SOW / Timeline

PM

With each change, continuously

Code review

• PM should make sure that issues are moving according to the workflow, each page or feature should go through the Code review after its completing

• TL should review the issue within 1 day after it appears in the code review status

• Self check by devs

DEVELOPMENT

• Conclusions/ common mistakes added to the Performance Review document

PM / Team-leads

With each code change, continuously

QA / Testing

• QA should test each issue after FE+BE completed

• Automated testing?

DEVELOPMENT

• Test cases

• Browsers & devices

With each code change, continuously

Release procedures

• Go-live check-list must be divided by FE,BE,PM and checked by TLs before launch

• Remember about backups

PRE-LAUNCH

Go-live check-list

PM / Team-leads

Before each release, periodically according to schedule

Go-live

LAUNCH

• Go-live check-list

• Instructions for devs

PM / Team-leads

During each release, periodically according to schedule

Retrospective

LAUNCHED

Retrospective document

PM

After each project release

Performance review

• Despite of the flow there should be procedures as self-development, review of the team members by the Team-leads

• Competencies review document for each team member

• List with dev’s skills

Team-leads

Once in 3 months

Devs Handover