Jira Fundamentals: Effective Scrum Project Management

Create a Jira Scrum project by selecting the Scrum template, choosing a company-managed project, naming it top story, with the key TS prefilled.

Explore how Jira uses issues to track work items, with pending, in-progress, and complete statuses, and learn how different issue types map to real-world tasks.

Explore Jira issue types—story, bug, task, and epic—and map user authentication and profile items to the right type, using epics to group related work.

Map course requirements to Jira epics and stories, and define the initial Jira issues across account management, search, viewing, cart, purchase, and wish list, plus alerting and monitoring.

Prioritize and groom your backlog in Jira by ranking epics, stories, and tasks to reflect project priorities, using quick actions to top or bottom the backlog.

Estimate effort in backlog using the Fibonacci sequence and story points in Jira, and customize the task issue type to capture estimates globally for sprint planning.

Estimate capacity using two developers and eight days per person to define a sixteen-day sprint, then create seven sprints in Jira with non-numeric names.

Plan sprints by balancing backlog stories with dependencies under a 16-day effort cap, prioritizing view product details and create account to maximize sprint utilization in Buick and Acura.

Start, monitor, and close sprints in Jira by assigning issues to team members and balancing workload. Explore sprint planning, issue details, and progress reports to coordinate collaboration.

Learn to use Jira's powerful search features at both project and global levels, including backlog and active sprint filtering, quick filters, and advanced search to locate issues by attributes.

Use advanced search with JQL to locate all issues assigned to Johnny across all Jira projects. Save the query as a permanent filter named Johnny's work for quick access.

Explore the burnup chart to track sprint progress by completed work, separate from scope changes, and compare it with the burndown chart to understand granular sprint dynamics.

Review how the sprint report summarizes progress with a burndown chart and issue status list, including completed, incomplete, and removed or outside-sprint work, for sprint retrospectives.

Discover how the velocity chart in Jira reflects team capacity by comparing committed versus completed points across completed sprints, guiding future sprint planning.