Meeting notes (QA)

PMs + QA call w/ Ivan
19.11.21

  • Access – need access to access card from each ticket

  • Description of QA scope: design match, google speed

  • Discuss priority in PM channel

  • Provide task description in English

  • Good example of tasks – ROCKEN

  • Unify workflow and status on each project – learn developers to follow it

  • Ready for QA – but some tasks are still on developer (incorrect assignee)

  • Added: Only the reporter can close the ticket (especially bug report), not anyone

    QA approaches:

  • Fully design matching – all elements are a must, fonts, global styles, sizes, spacing

  • Design-based testing – spacings are valid up to X1.5, elements can be excluded/changed/replaced, global styles should be followed, this approach needs additional discussion with PM to define the detailing level of testing

    General discussion of the QA process w/ Ivan
    25.05.22

  • Workflow unification in Jira to avoid the mess in the QA board

  • Divide projects to 3 categories: Rocken, bigger projects (e-commerce, platforms,..), other (small projects few pages, mostly front-end) – for each category should be template of the workflow statuses/columns

  • Best practice – Involve QA on the initial phase of discussion with client / start of the development

  • Create the basic initial documentation for projects

  • Update meeting notes in Confluence after each update in the projects (notes from the client’s/team’s calls, messages in Slack, etc.)

  • Automization of the board process for QA team -> Update the QA board, f.e. divide by assignees (for future)

  • Divide the QA resources – QA for particular projects, PMs

  • Discuss the problems of QA team (check the previous created list)

  • Meeting set up by Tanya with PM team to discuss the basics of QA work

26.07.22

  • Add time for QA for each estimation – discuss it later!

  • Involve QA to the estimation

  • Browser/device list from client – PM should ask client about this during inception phase (on this list would depend QA hours)

  • Divide QA resources – QA – PM (ask PMs with who from QA team they want to work)

Comments

Leave a Reply