This title slide features the main heading "Jira Foundations: Planning, Tracking, and Collaborating as a Team." The subtitle describes it as a refresher and introduction for cross-functional teams.

Jira Foundations: Planning, Tracking, and Collaborating as a Team

A refresher and introduction for cross-functional teams

Source: Internal Jira Training

Jira is a team-wide shared to-do list for planning, tracking, and delivering work. It supports all teams, from Agile and software to marketing and ops, with desktop and mobile access.

What Is Jira?

• Team-wide shared to-do list
• Plan, track, and deliver work
• For all teams: Agile, software, marketing, ops
• Desktop and mobile access

Teams use Jira to tackle chaos and scattered work by assigning clear ownership and accountability. It makes project status visible to everyone and serves as a single source of truth.

Why Teams Use Jira

• Tackles chaos and scattered work
• Assigns ownership and accountability
• Makes status visible to everyone
• Provides a single source of truth

Source: Jira Foundations presentation - Slide 3

The "How Jira Helps Teams" slide features a grid of six key benefits: full transparency for real-time visibility and commenting, boosted efficiency via task breakdown, enhanced collaboration through centralized discussions, clear task ownership, progress monitoring, and a single source of truth. Each feature includes an icon and concise description emphasizing Jira's role in team productivity.

How Jira Helps Teams

{ "features": [ { "icon": "👁️", "heading": "Full Transparency", "description": "Everyone can see and comment on work in real-time." }, { "icon": "🚀", "heading": "Boost Efficiency", "description": "Break big projects into manageable, trackable pieces." }, { "icon": "🤝", "heading": "Enhance Collaboration", "description": "Centralize discussions and decisions in one place." }, { "icon": "🎯", "heading": "Assign Ownership", "description": "Clearly assign tasks and ensure accountability." }, { "icon": "📈", "heading": "Real-Time Visibility", "description": "Monitor progress and status across the team." }, { "icon": "📋", "heading": "Single Source of Truth", "description": "All work details in one reliable location." } ] }

Source: Jira Foundations Presentation

Jira helps prioritize important work and plan your week visually. It also tracks tasks and teammates’ progress while enabling easy updates sharing.

How Jira Helps You

• Prioritize important work
• Plan your week visually
• Track tasks and teammates’ progress
• Share updates easily

Source: Prioritize work. Visual weekly planning. Track tasks & progress. Easy updates.

This agenda slide outlines core Jira concepts: Work Items for tracking individual tasks with progress and discussions, Spaces (Projects) as collections of related items for teams or initiatives, and Boards as visual workflow displays from start to completion. It concludes with how these elements interconnect for unified organization, accountability, and transparency.

Navigating Jira: Core Concepts

1. Work Items

Individual pieces of work to track progress, updates, and discussions.

2. Spaces (Projects)

Collections of related work items representing teams or initiatives.

3. Boards

Visual displays of workflow statuses from start to completion.

4. How They Connect

Unified structure for organization, accountability, and transparency. Source: Work items, Spaces (projects), Boards. See how they connect for organization.

A Work Item is an individual piece of work that tracks progress, updates, and discussions. It includes descriptions, comments, attachments, and links.

What Is a Work Item?

• Individual piece of work
• Tracks progress, updates, discussions
• Includes descriptions, comments, attachments, links

Source: Jira Foundations: Planning, Tracking, and Collaborating as a Team

A Space (Project) is a collection of related work items, with each item belonging to exactly one space. It represents a team, product, or initiative.

What Is a Space (Project)?

• Collection of related work items
• Each item belongs to one space
• Represents a team, product, or initiative

Source: Jira Foundations

The slide "What Is a Board?" defines a workflow board using four key statuses: To Do (assigned but unstarted, e.g., plan new feature), In Progress (actively worked on, e.g., develop code), In Review (completed awaiting feedback, e.g., test & review), and Done (finished and accepted, e.g., deploy to production). It presents this in a table format with columns for Status, Description, and Example.

What Is a Board?

{ "headers": [ "Status", "Description", "Example" ], "rows": [ [ "To Do", "Work assigned but not started", "Plan new feature" ], [ "In Progress", "Actively being worked on", "Develop code" ], [ "In Review", "Completed, awaiting feedback", "Test & review" ], [ "Done", "Finished and accepted", "Deploy to production" ] ] }

Source: Visual work view in a space. Columns = workflow statuses. Work flows start to finish. Simple diagram.

The slide "Types of Boards" compares Kanban and Scrum boards in two columns. Kanban enables continuous work flow without fixed iterations, limiting progress for steady throughput in ongoing or unpredictable tasks, while Scrum organizes work into fixed sprints (e.g., 2 weeks) for iterative planning in projects with defined cycles.

Types of Boards

Source: Jira Foundations

The slide "Common Work Item Types" is a table listing five key types: Epic (large parent body of work), Story (user-focused deliverable), Task (specific piece of work), Bug (problem or defect), and Sub-task (small step toward a larger item). It provides concise descriptions for each to clarify their roles in project management.

Common Work Item Types

{ "headers": [ "Type", "Description" ], "rows": [ [ "Epic", "Large body of work (parent item)" ], [ "Story", "User-focused deliverable" ], [ "Task", "Specific piece of work" ], [ "Bug", "Problem or defect" ], [ "Sub-task", "Small step toward larger item" ] ] }

To create work items, write a clear, concise description including what, why, and acceptance criteria. Update items by dragging them across status columns (e.g., To Do → In Progress → Review → Done) to reflect progress, and add comments with @mentions, files, or links.

Creating & Updating Work Items

{ "headers": [ "Step", "What to Do", "Tips" ], "rows": [ [ "Create", "Write a clear description", "Include: What, Why, Acceptance criteria. Keep it concise and actionable." ], [ "Update", "Drag item to new status column", "e.g., To Do → In Progress → Review → Done. Reflect real progress." ], [ "Comment", "Add comments for Q&A and updates", "@mention teammates, attach files, link related items." ] ] }

Source: Clear descriptions → Update status → Comment for Q&A/updates. Step-by-step icons.

This slide on "Adding Context: Attachments & Links" explains how to attach files like images, documents, and logs. It also covers linking related work items, Confluence pages, and external resources for easy reference.

Adding Context: Attachments & Links

• Attach files (images, documents, logs, etc.)
• Link related work items for easy reference
• Link Confluence pages and external resources

Source: Jira Foundations Presentation

This conclusion slide highlights integrations with Slack for real-time notifications, AWS for cloud workflow integration, and Tenable+ for auto-creating items from alerts, under the subtitle "Seamless tools for better teamwork." It wraps up with the bold message: "Aligned, accountable, productive teams!"

Integrations & Wrap-Up

• Slack: Real-time notifications

• AWS: Cloud workflow integration
• Tenable+: Auto-create items from alerts

Aligned, accountable, productive teams!****

Seamless tools for better teamwork

Source: Jira Foundations Presentation