Category: Implementation board

1. Statistics / Reports

One of the main problem connected with creating Reports or gaining Statistics is Time Tracking.
Please check if continuing using TimeDoctor as a Time Tracker is possible to save spent time for each task to the Jira + using this time in the reports (see the spent time for each task / sprint / project overall)
OR Propose the alternative for tracking tool which allows creating user-friendly reports, Jira saving spent time
❗️Important for us in using TD is overview of the dev’s work (there is a Dashboard which allows us to see what dev is doing at the moment / in the selected date or time range; available tool for making screenshots) + we using it as a billing tool for our Clients.

Operation Statistics per Team (internal)

Issue: Management team want to measure Teams’ (dev, QA, PM) KPIs by having statistics for the following points👇🏻 .
The stats should be:
– available for each project,
– presented in the user-friendly way (charts, tables),
– automatically updated (saved formulas, filters) OR easy to gain,
– easy to filter by date range / sprint, project, user

Developers:

• How many tasks were returned from QA to development: by developer / project
  (basically, analyzed quality of developers and the whole project)

• How many tasks were reopened after QA: same as above

• Estimated vs spent hours per page (task) / project

QA: 

• How many bugs were open by client 

• Estimated vs spent hours per page (task) / project

PM:
(General list of all projects which each PM has)

• How many project each PM has

• Status of each project

• See the deadline of each project

• How many missed deadlines on the project, is project behind the schedule/overbudget?

General reports per Project (internal)

(Similar to Stats for PM team, but in separate Dashboard if possible)

• Board of all projects by status: active vs support projects, and ability to filter by PM

• Timeline of the project with final deadline – which task on what stage, and their progress

Reports for Clients by Project (external)

Issue: We’re currently using TimeDoctor’s standard reporting system for creating general Reports regarding Project’s time spent, but it doesn’t give us “full picture” for the most demanding Clients.
Ideally, we want to have more detailed statistics and be able to share it with client in user-friendly format (f.e. pdf).

• How many tasks were closed

• Estimated VS Spent time

• Spent time for dev / QA

• How many bugs VS CR

2. Automatization

Project / Tasks

• Possible to automate project creation (tips and advices are welcome)

• Pick the standard Workflow scheme (few options) during creating New Project + Columns on the Board are auto-created per Scheme

• Add Confluence page with Project Passport template automatically to the New Project

• Generate tasks templates that should be done on all project

• Automate task creation based on estimation file
  (estimation is created in separate Google Sheet)

• Support form – to get support tickets submitted and converted in Jira board

• Converting feedback doc (Google Sheets) into Jira Tasks

3. Confluence organization

• Organization of Spaces in the Confluence (visibility of connection between Projects spaces & PMs spaces)

• Create the space with all documentations / flows / checklists – user-friendly usability – dividing by teams (dev, PM, HR, QA)

• Create the space with all Projects and its details (Name, Duration, Link to the project passport) – to have the list with all projects for the Onboarding (HR team), Portfolio (Sales), ..
  (Accounts Partners → Projects, Requirements for account companies)

4. Processes set up

• QA must be a must-have process
  Without QA the task can’t be closed, subtasks are not required

• Code review board
  Separate board, which would be available only for TeamLeads, when task go to the “Code Review“ status → it appears on separate “Code Review“ board as well
  Front-end tasks comes to one a separate person front-end/back-end

• Support board – set up priority, most urgent goes on top

• Integration Jira + GitLab
  Our devs are making via API – we have local GitLab server

• Invite Client to the specific project
  We are currently creating a separate Permission scheme and Group for each Project, is it possible to make it more simple?

🤝Team

 Description

Issue overview:

Scope of work:

References:

🔗Accesses & Useful links

 Milestones

 Requirements / functionality

 Open Questions

🆘 Change Requests

 Out of Scope

Jira Project’s Documents

• Why do we need it (points from sophiabilyk & Ivan Hodoniuk)

• Create project’s space in Confluence

• Project Passport (Template, Example)

• Meeting notes (Example 1, Example 2)

Tasks rules

• Description in English + good examples

• QA scope – Ivan Hodoniuk few tips / good examples how to describe it better

• Assignee change after changing status from “In progress“ to “Ready for QA“

• Only reporter can close the ticket (in case if QA was reported bug, only he can close it after check-up)

Project’s Workflow

• General workflow process description (Dev → QA / CodeReview (later))

• Differences between Status / Column

• Presentation of the standard workflow scheme
  Transitions need to be double-checked by sophiabilyk

• How to add workflow scheme to your project

QA Resources

• Divide QA resources by PMs, make the – Ivan Hodoniuk few words why do we need it, what are advantages of this model from QA team perspective

• Ask PMs who they prefer to work with & make a table

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)