The document outlines the Scrum framework and Jira workflow, detailing project setup, roles, issue hierarchy, sprint management, backlog grooming, reporting metrics, and standard Jira workflow stages. It emphasizes the responsibilities of the Product Owner, Scrum Master, and Development Team, as well as the importance of continuous improvement. Key Jira reports such as Burndown Charts and Velocity Charts are highlighted for tracking progress and optimizing performance.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
5 views10 pages
Jira
The document outlines the Scrum framework and Jira workflow, detailing project setup, roles, issue hierarchy, sprint management, backlog grooming, reporting metrics, and standard Jira workflow stages. It emphasizes the responsibilities of the Product Owner, Scrum Master, and Development Team, as well as the importance of continuous improvement. Key Jira reports such as Burndown Charts and Velocity Charts are highlighted for tracking progress and optimizing performance.
Create a Scrum project using the Jira Scrum Software template
Assign a Project Lead for configuration and management Configure board with key columns: To Do, In Progress, Blocked, Ready for QA, Ready for Production, In Review, Done Use Swimlanes (grouping by Epic or Assignee) and Quick Filters (Priority, Story Points, Assignee) Set Story Points as the estimation field. 2. Roles and Permissions
Product Owner: Manages backlog and prioritization.
Scrum Master: Facilitates Scrum processes and Jira usage.
Development Team: Completes tasks, updates issues, collaborates.
Stakeholders: View progress with limited Jira interaction.
3. Jira Issue Hierarchy and Structure
Epic: Large feature or initiative.ages backlog and prioritization.
Story: User-centric requirement, aligned with DoR/DoD.
Task: Technical activity to fulfill a Story.
Sub-task: Granular steps within a Task or Story.
Issue Lifecycle: Created → Prioritized → Sprint Planning → In Progress → Completed.
4. Sprint Management and Process
Sprint Planning: Backlog refinement, prioritization, and story point estimation.
Daily Stand-ups: Progress tracking and task updates.
Sprint Review: Demo of completed work, verification by Product Owner.
Sprint Retrospective: Review Jira metrics, identify process improvements.
5. Management and Grooming of Backlog
Regular backlog refinement (weekly/bi-weekly).
Product Owner Responsibilities:
Maintain backlog, define stories with acceptance criteria
Link stories to Epics, ensure smooth sprint planning. 6. Reporting and Metrics
Key Jira Reports:
Burndown Charts – Track remaining work in a Sprint
Velocity Charts – Measure average story points per Sprint Cumulative Flow Diagram – Monitor workflow progress Sprint Reports – Breakdown of completed and pending issues.
Velocity and Throughput: Track and optimize sprint capacity.
7. Standard Jira Workflow To Do: New tasks/stories awaiting work. In-Progress: Active development. Blocked: Tasks that cannot proceed due to external dependencies or impediments. Ready for QA: Development complete, ready for testing. Ready for Production: QA team performed functional testing on staging(test) environment and it is ready to deploy. UAT/ In Review: Final review by Product Owner/stakeholders. Done: Work completed, tested, and approved. 8. Continuous Improvement