Theme

Category: sophiabilyk

  • QA Process & Procedures

    (синяя звезда) Overview

    The QA process in development is an important step to ensure the quality and functionality of a product.
    It involves testing and verifying that the product meets the specified requirements and specifications.
    This documentation provides an overview of the QA process including PM, QA, Dev responsibilities.

    (синяя звезда) Preparation for the Project’s start (pre-development stage)

    • QA should be assigned to the Project as a dev team by PM, i.m.
      — Added to the Project’s group chat/channel in the Slack
      — Added to the Jira Project
      — Added to Time Doctor
      — Involved in the Estimation phase, QA time should be added to the separate column in the Estimation file

    Estimation should include time spent on preparing QA & PM’s documentation

    • PM should create Project Passport & Requirements documentation

    • PM should discuss with the Client his preferences regards QA Approaches & Supported browsers and devices and pass it to the QA
      (Examples (синяя звезда) )

    QA Approaches (examples):

    • 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

    • Based on the above information, QA should prepare QA Documentation (Supported browsers and devices, Test Strategy, Test Cases*, Bug Report Instructions) in the Confluence Project’s space
      *Test Cases is a new procedure, which would not be applied to all project just yet

    Supported browsers and devices, Test Strategy documentations should be approved by PM, each team member & Client as well*
    * It’s PM’s responsibility to bring & present it to the Client

    • PM should add all tasks divided by Epics/Stories describing main functionalities of the project
      — All Issue details should be written in English and well described
      — For all Issues, where it’s needed, should be added Acceptance criteria in the “QA Scope” field
      (Examples)

    (синяя звезда) Development + QA stages

    • QA should test the whole Epic/Story, when FE+BE is completed (avoid FE or BE testing first – required for the new Projects, which were done from scratch), in the all other cases (Support, CR, specific functionality) – Task/Epic/Story

    • After Task/Epic/Story is completed and initially tested by the Dev, Dev (in some cases PM) should assign it for the QA and change status for “Ready for Testing / QA“

    • All Bug tasks should be created by the example of this template and linked to the certain Task/Epic/Story

    • After the Bug is fixed, it is tested once more by the Dev, and afterwards sent to QA for Bug verification

    • After the testing is successfully done, Task/Epic/Story should be transferred to the “QA Approved“ status by QA

    • The Task/Epic/Story could be considered as “Done”, when it’s uploaded to the production by Dev

    • For all Issues in status “Done“, the verification on production is a MUST
      QA could use Regression or Smoke testing on production depending on Project needs

    (синяя звезда) General Communication orders:

    • Daily meetings w/ team, including QA

    • Retrospective after each Sprint, once in 1-2 weeks (depends on project’s needs)

    • Priorities of Projects for testing should be communicate each week on the PM meeting / Workload planning or directly in the #pm channel during the week by PM

    There should be not more than 2 projects for the QA a day to test

    // Should be added to Test Strategy template for OneLine projects

    For all ONELINE projects, make sure that the information about CHE IT is deleted, i.m.

    • Information about devs, check site – here

    • Personal emails in the contact form configurations, admins emails

    • Names of users in the admin panel

  • Weekly report 20.02-03.03

    Project Schedule & Scope Status

    Scope/Projects

    Status

    Initial ETA

    Current ETA

    Initial Budget

    Current Budget
    (February-03.March)

    Team

    Update

    ROCKEN

    ON TRACK

    –

    –

    –

    1535h

    ROCKEN team

    • Working mostly on new system + support requests

    • Animation – continue the work

    • Continuing practice the internal demo

    • Received first pages of the corp site to development (involving Ihor Havrilenko as FE dev)

    • Involving Vika (QA) to the project

    Flyttesiden

    ON TRACK

    –

    –

    –

    46h

    Oleh Honcharuk
    Elvin Agaragimow
    Filipp Antonov

    • Worked with Vipps payment integration + complete few ongoing tasks

    • Waiting for approve of the Vipps account to set it up live

    RiefMedia: MBCA

    ON TRACK
    (redesign)

    Dec 2022

    –

    396-516h

    387h – overall

    Tetiana Tkachuk
    Filipp Antonov

    • Working on the documentation with instructions on how to use admin panel and working with the content

    • Waiting for the green light from MBCA that we can move forward with the content (they need to check/add it) – still no feedback (Jordan pings them)

    RiefMedia: S&Sinc.

    PAUSED

    –

    –

    –

    69h*
    *23h – February

    Dima Nagaev
    Oleksii Reshetnyk
    Filipp Antonov

    • Completed new page development (billed 14h in February, 9h – March)

    RiefMedia: Avanti

    PAUSED

    –

    –

    –

    82h

    Dmytro Melnyk
    Dmitriy Nagaev
    Filipp Antonov

    • Received info from Brant that they would have more pages for the development last week – still don’t get it

    • 8h which was spent (November) would be added to the next invoice (when we receive new pages)

    RiefMedia: CredHub, ServeFirst

    ON TRACK
    (support)

    –

    –

    –

    6h

    Artem Simonchuk

    • Small support tasks

    OneLine: Porsche

    ON TRACK
    (support)

    –

    –

    –

    1,5h

    Dima Sviridenko

    • Small support tasks

    Implementation report (13.02-17.02)

    Task

    Status

    ETA

    Update

    Jira administration

    IN PROGRESS

    –

    • Plan to work with permission schemes

    Tempo integration + Jira features & automation

    IN PROGRESS

    –

    • Need the call with Coreteka to finalize decision regarding Yaware

    Support process

    IN PROGRESS

    –

    • Worked with forms, portal customization – had few questions to Ira so now she is working on it

    Documentations & Procedures

    IN PROGRESS

    –

    • Presented Communication documents for the PM team on Friday

    • Prepared example of Daily Meeting notes doc

    • Next steps are to present Estimation & Planning, and after that QA

    PM team KPIs

    IN PROGRESS

    –

    • Prepared the list of PMs responsibilities with Slava, need to discuss with Alex how to move forward with that

    Code Review process

    ON HOLD

    –

    • ON HOLD, until guys will prepare the documentation/rules for devs and think how to improve it

  • [PM_Name] Projects to handover [Date from – Date to]

    Project Name + Link to Jira

    Client

    Team

    Communication channel

    Comment/What needs to be done

    Responsible PM

  • [Template] PM Handover checklist

    Before you start planning your Handover, please copy this page to your personal Confluence space and mark all checkboxes before you start vacationing. Add your name/surname and vacation dates to the name of the page.

    📋 Initial Communication & Handover Scope preparation

    Example of the text message:
    Subject: [PM_Name] Vacation [Date start – Date end]

    Text:
    Hi team,

    I would like to request leave / vacation for the following dates [from and to].

    Please approve.

    Thanks,
    [Your name]

    📍 Golden rule: [Date of the request for the vacation / day off] >= [Time of the vacation * 2]
    (e.x. You plan vacation for 1 week, then you should notify management team about your vacation at least in 2 weeks before planned vacation date)

    📍 Make sure your vacation time do not coincide with any releases

    • Prepare the list with all your projects using this template
    • Assign responsible PMs to handover your projects

    • Discuss w/ management team who can handover your projects (if needed)

    • Send the Handover file to #pm (notify & tag responsible PMs)

    • Send message/email with notification about your vacation / day-off to your clients (Slack/email)
    • Add responsible PM to the chat with client
    • Send notifying message to your team members about your vacation / day-off
    • Add responsible PM to chats with team members

    🔎 Tasks & Projects

    • Do preparation work with the customer before you go

    • Discuss the scope of work, which should be done during your absence

    • Define the priorities & deadlines

    • Ask if this possible to not add new requests during your absence (bugs not included)

    • Check all new client’s requests / dedicated scope for the projects

    • Make sure tasks’ statuses are up-to-date

    • New tasks should be created in the Jira project

    • Clear & specific description should be added to all tasks

    • Assignee should be added to each task

    • Due dates & priorities should be inserted for each task

    • Check & make sure project documentation is up-to-date

    • Accesses file

    • Project Passport

    • Meeting notes

    💻 Internal communication & handover

    • Make a call w/ team & responsible PM for each project

    • Discuss the scope which should be done during your absence

    • Make sure everyone (team & responsible PM) understand tasks and all questions/details are specified in the task’s description

    🏝Enjoy your vacations!

  • Overview

    Shared with your team. Learn about space permissions and restrictions.

    Greetings!

    Think of your personal space as a folder of storing all the documents that don’t currently belong anywhere else. It’s all yours. Customize this page by clicking the edit button on top.

    What’s inside this space?

    Sample Pages






    Недавние обновления

    Показать больше
    Пожалуйста, подождите