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

15.05 Wed 11am

Daily

• Last status before I go to vacation

• Introduce the plan for next 2 weeks for the team

• Motivation speech from Ihor

Release plan

16.05 Thur 11am

Daily

• Check team’s status

• Check how much free time left for each team member in the Sprint 69

• Discuss the tasks left for the Processes

• Create and assign Processes tasks if possible (if not leave them for Sprint 70)

Tasks left for Processes:
Filters the same as now without Archived – доробити
Forecast – зробити
Search – доробити (

RT-3871

RT-3872

)
Adding – готово
Change status – дизайн ін прогрес+дев
Interview dates negotiation – є дизайн, треба девелопмент
Listing and collapse – є дизайн, треба девелопмент

17.05 Fri 11am

Daily

• Check team’s status

• Ask what they plan to finish during Friday and whats left for the next sprint

• Remind to the team that they should prepare for the demo on Mon

Ask Ihor how the things going with Company bugs

20.05 Mon 11am

Daily
Demo
Sprint planning

Daily

• Check team’s status

• Ask if they completed what was planned for Friday

• Ask how much time they need to finish the tasks from Sprint 69 (those will be moved to Sprint 70)

• Calculate free time for Sprint 70 for each team member

Demo

• Ask each team member to show what they did during last sprint

Sprint planning

• Add tasks from the file to JIRA

• Estimate those tasks with the team and pick the assignees

• Pick the bug hunter for the Sprint 70 (last Bughunter was Dasha, so this time it should be Anton)

• Check the tasks we already have in Sprint 70 and set up the priorities, if something is more urgent – leave in this Sprint, other – move to Sprint 71

• Make sure each time member has a full workload for the Sprint (10 days) and everyone understands what they should do in the assigned tasks

Check the following existing tasks in Sprint 70 with Julia and Ihor:

• Open tasks – how urgent it is?

• Dev blocked tasks on Valya – what should we do with it? what is the real status of each?

• Bugs – Sprint 70 or post-release?

Ihor should finish by the end of Sprint 69:

• Company bugs, all tabs tasks, Communication module

21-23.05 Mon-Thu 11am

Dailies

• Check team’s status and make sure everyone & everything goes according to the plan

• Each team member must say – what they did yesterday / what they plan to do today

24.05 Fri 11am

Daily + Half-sprint retro (if needed)

• Check team’s status and make sure everyone & everything goes according to the plan

• If you don’t like the progress, connect with Ihor and Julia and plan what you should do to speed up the process

• Talk with Julia and Ihor (depends on progress) when & how Julia plans to gave the stage link to the Rocken team

27-30.05 Mon-Thu 11am

Dailies

• Check team’s status and make sure everyone & everything goes according to the plan

31.05 Fri 11am

Daily + retro

• I come back

• Success result: All tasks from the list planned for Sprint 69 + Sprint 70 are done from the dev’s side

Estimated

Spent

Estimated

Spent

ON TRACK

–

–

369h

–

–

ROCKEN team

• Vika&Ivan test CRM/Talent; Dima works on Orders; Sasha worked on Company page connect to API and bugs; Dasha continue working on Applications reports for BI; Anton worked on migrations; Valya works on Vacancy view

ON TRACK
(support)

–

–

101h

–

–

Laravel: Slavik Syvyniuk
Laravel Lead: Yurich
QA: Ilya Bilyk

• Working for final requests for Porsche (small tasks)

• No new requests for Harley Davidson – they are working on the design and finalizing requirements with the client

Estimated

Spent

Estimated

Spent

ON TRACK

–

–

1102h

–

–

ROCKEN team

• Vika&Ivan test CRM/Talent; Dima worked on Chats & Files; Sasha worked on Company page connect to API and bugs; Dasha continue working on reports for BI; Anton worked on migrations; Valya worked on Publication, Vacancy and Process lists

• Slavik works on stylecloud, didn’t want to interrupt him for now, but will discuss this week with him internally the possibility to start asap

ON TRACK
(support)

–

–

98h

–

–

Laravel: Slavik Syvyniuk
Laravel Lead: Yurich
QA: Ilya Bilyk

• Waiting for final requests for Porsche

• No new requests for Harley Davidson – they are working on the design and finalizing requirements with the client

Estimated

Spent

Estimated

Spent

ON TRACK

–

–

824h

–

–

ROCKEN team

• Vika&Ivan test CRM/Talent; Dima worked on Chats; Sasha worked on Company and Users page connect to API; Dasha works on Paas reports for BI; Anton worked on bugs; Valya worked on Company page and Publication list

• Completed Questionnary landing

• Slavik works on stylecloud, didn’t want to interrupt him for now, but will discuss this week with him internally the possibility to start asap

ON TRACK
(support)

–

–

98h

–

–

Laravel: Slavik Syvyniuk
Laravel Lead: Yurich
QA: Ilya Bilyk

• Received final requests for Porsche brochures, will work on it this week

• No new requests for Harley Davidson – they are working on the design and finalizing requirements with the client

Estimated

Spent

Estimated

Spent

ON TRACK

–

–

501h

–

–

ROCKEN team

• Vika&Ivan test CRM/Talent; Dima works on Forget password + Orders; Sasha is working on bug fixing + Company page connect to API; Anton works on bugs and started migrations; Valya worked on CRM Users page

• Working on second Landing should be finished this week

• Slavik onboarding plans from the next week

ON TRACK
(support)

–

–

98h

–

–

Laravel: Slavik Syvyniuk
Laravel Lead: Yurich
QA: Ilya Bilyk

• Waiting for Porsche approve to transfer changes live, had few minor requests

• Prepared stage for Harley Davidson

Estimated

Spent

Estimated

Spent

ON TRACK

–

–

1508h

–

–

ROCKEN team

• Vika&Ivan test CRM/Talent; Dima worked on Candidate Interview, Talent Contact Info API; Sasha is working on bug fixing; Anton worked on Localization, Reject & accept actions for Companies and started migrations; Valya works on CRM Users page

• Had an issue with dev work (Landing) – we didn’t meet the deadline and Rogkov communication was not professional. Landing was published live.

• Critical issue with sending invitations to real people from stage – had a retro with team, wrote the sum-up to the Rocken dev channel

ON TRACK
(support)

–

–

96h

–

–

Laravel: Slavik Syvyniuk
Laravel Lead: Yurich
QA: Ilya Bilyk

• Waiting for Porsche approve to transfer changes live

• Had a call with Egzon & Danny regarding the Harley Davidson project – they should have final call on 13.11 and start the design after that, in the meantime we will work on preparing stage, copying Porsche, clearing the database

• Digital Koala is a new name of the OneLine’s brochures product

Estimated

Spent

Estimated

Spent

ON TRACK

–

–

1128h

–

–

ROCKEN team

• Vika is testing Talent; Dima prepared stage for CRM and started with Orders functionality; Sasha is working on bug fixing; Anton is working on enhancing Companies actions; Valya works on CRM Users page

ON TRACK
(support)

–

–

96h

–

–

Laravel: Slavik Syvyniuk
Laravel Lead: Yurich
QA: Ilya Bilyk

• Waiting for Porsche approve to transfer changes live

Estimated

Spent

Estimated

Spent

ON TRACK

–

–

872h

–

–

ROCKEN team

• Vika is testing Talent; Dima finished CRM Applications & next week will start gathering CRM components on stage; Dasha continue working on BI board (charts connecting FE to BE); Sasha is working on bug fixing; Anton is working on Localization; Valya works on CRM Users page

• Talent testing from ROCKEN side was finished, Julia added few tasks in the new epic (improvements and bugs)

• Had a demo call for Toni, updated release date is the end of the year

ON TRACK
(support)

–

–

96h

–

–

Laravel: Slavik Syvyniuk
Laravel Lead: Yurich
QA: Ilya Bilyk

• Had few minor requests

• Waiting for Porsche approve to transfer changes live

https://cheitgroup.atlassian.net/jira/software/c/projects/RT/boards/32

ROCKEN
Miriam, ROCKEN team

ROCKEN team

https://cheitgroup.slack.com/archives/CQU1BV57Z

• Discussed w/ Julia

Julia

https://cheitgroup.atlassian.net/jira/software/c/projects/PRSCH/boards/34

OneLine
Egzon, Danny – OneLine / partners

Slavik Syvyniuk
Yurich (Lead)

https://onelinemarketing.slack.com/archives/C02C3NQ44EL

• 
  PRSCH-122
  
  ,

  
  PRSCH-129
  
  is currently on review from the Client’s side
  Waiting for their feedback

Andrii

Jira administration

Instructions how to create project – https://cheitgroup.atlassian.net/l/cp/0y1GeHh4

Slava

Approve estimates

Alex

Problem with resources / Workload issues

Alec

Start new project / Go-live issues

Alex

Problems with clients (RiefMedia/OneLine)

Alex

Assigning projects / tasks to PMs

Alex

Approve day-offs in Hurma

Tanya

Anna

• Siento – landing ready for review 09.10

• Analyze spent/estimated time on Siento

• OneLine – re-audit SEO

• HeyLocate – 2 new pages (end of the next week)

• MYCON – go live

• Shopify project – ask client about price (cooperation with sales team)

• Presentation for estimation

Kate

• Swisskrono – next week go-live

• Aprico – new project from OneLine

• SMTP double-check multi language

• Rosarot requirements in google doc – Discovery phase

• Saclab – documentation for next year

• Casinor another project from Dan on Alex

Nastya

• RiefMedia – Music&Media fixes, Futures contact page

• CVshop – waiting for SEO articles (Tuesday)

• Performance – 26.10 deadline

Givi

• BussMurtonLaw – client should pay invoice

• Hochschule – change link structure + additional week of work

• New project – need proper design, start new project

• 2 new estimations waiting for approve

Andrii

• Stingray – main animation on the HP

• Support projects/tasks from OneLine

• Need better documentation for support projects

• Problem with resources