In order to ease the usage of Jira and ensure a standardization of practices here are few tips and tricks.
Targeted users:
- Product Owner/Service Owner - Capturing the requirement and structuring the information (Backlog + Process)
- Project Manager/Scrum Master - Structuring the delivery and following up with the delivery evolution (Focus on the capacity, ressources and scope, backlog)
- Any experts within a dedicated field - Security, Enterprise Architect, Support team - Following at high level the evolution of the delivery and capturing possible deviation
- Agile Team - Filling, enhancing and following the backlog evolution and delivery (Requirement Analysis to the validation through tests)
- Data Platform experts - Following the delivery and decision that are taken within a team to make the delivery
- Stakeholders - They need to know the current status and product's evolution
- Leadership Team - They need to follow at High level the backlog to answer fw question regarding the team workload, velocity, risks & issues management,
- Resource Manager - Should not be required anymore
Required view and interactions:
- As ... IWL to have a HL view of a specific project to know the current status (% of achievement, % of inknown, number of Risks and Issues, )
- As .... IWL to see
Jira structure & conventions:
All User story and/Or tasks must us the structure below:
AS A <persona>
I WANT <feature>
SO THAT <business value>
Acceptance criteria:
<Criterion 1...>
<Criterion 2...>
Subtask
are used to clarify what needs to be done (precise content information)
Who could be interested :
What is the proposed solution?
Why have we put that solution in place?
How should we use it ?
----------------------------------------
Who could be interested :
What is the proposed solution?
Why have we put that solution in place?
How should we use it ?