nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

QA Workflow Advise

xxxx

Comments

Hi @Sagi Binder ,

Welcome to the community!

Configurations & Workflow:

I will suggest you take a look at the board configuration as there may be several statuses in the QA column.
Workflow review: (if you can share your workflow, it may help)
check that the workflow allows the transition of "Ready for Testing" to "In Progress"

The team's definition of done:

It is important to have an agreement with the team on the Definition of Ready and the Definition of Done

On your second challenge; the above suggestions will help provide visibility into what issues exist in the current way theta works and allow you to identify the areas that needs changing.

Thanks for your reply, it's help me to think.
In the same theoretic subject, if I have a situation that in the last several sprints, Developer A burned significantly more points than any other team member.

Which parameters will you use to identify the reason for this exceeded performance, based on JIRA’s capabilities.
which methods (quantitative or qualitative) will will apply outside of JIRA (or another tech tool) to identify the reason for this exceeded performance.

One factor that can contribute to your observation is Story estimation.
Although the volume of work may be more than the others, they may be less complex than the others.

Some questions to check out: How does the team currently estimate stories?

check this out: https://www.youtube.com/watch?v=VsSaolMtkKU

As you are new to the team, you may need to engage with them to understand how they do certain things and why they do it that way.

Joy

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

agile