The world of JIRA Wonders

The Acceptance criteria....

• The PM tells the team what the AC should be.

• You'll work these out with your team and the PM

• The PM, QA and Dev Manager work together to achieve an acceptable criteria

• is the same as the DoD

The Verified Fix Version should be the same as the

• Actual Fix Version for all Jiras in Preview and Production, and never lower than the Actual Fix Version.

• Actual Fix Version for all Preview Jiras

• Actual Fix Version + 2 weeks

• the sprint

The team that is implementing a jira should be indicated in...

• the component field and the Team Field

• the label field

• only the Team Field

• only the component field

The "Toggled by" field in a Story is used to indicate..

• the FixVersion of the Toggle

• the Sprint in which it got toggle

• the Epic or other Toggle

• who was the Dev that toggled it

Who should close the jira if the change is already in a production release?

• The Dev Manager, The person that opened it, the QA that verified it, PMO.

• The PM

• Only the Dev Manager

• The developer.

The FixVersion is...

• the real ActualFixVersion

• always the same as the intended Preview Delivery

• is the week when you completed the story YYYY.WW

• When the issue will be most likely go live in a production tenant.

A QA wants to verify a story:

• They can test in a Developer’s SUV to provide feedback but can’t Verify using this SUV.

• he can't because that's the PM's role.

• You can verify in a Developer’s SUV

• he should be kept in a quiet room until he emerges with a resolution.

In the context of a Story an Automator Dev should:

• Commit their work against the Story

• Create Sub Task Auto Jiras in Sprint Planning,

• Work in a separate story because automation always goes live independently

In a story that QA engineers will verify, they should

• wait until the Jira is in Production

• update "verified by" and when finished:

  update the status to Verified

  update "VerifiedFixVersion"

• wait until the Jira is in Preview

• only need to update the assignee to themselves.

Before a Sprint starts the PM will populate the following in a Jira Story:

• The FixVersion

• The number of story points

• The acceptance criteria

• Description. Also update the toggle jiras with the intended Preview and Prod delivery.