Free Software Tools learning guide
Jira for Beginners: Step-by-Step Guide to Mastering Agile Project Management
Jira for Beginners: Step-by-Step Guide to Mastering Agile Project Management — a free beginner-level guide covering learn to use jira for beginners....
What you will learn
- 1. Introduction to Jira and Agile Basics
- 2. Setting Up Your Jira Account and Navigating the Interface
- 3. Creating and Managing Projects
- 4. Working with Issues: Creating, Editing, and Tracking
- 5. Boards and Backlogs: Scrum and Kanban Basics
- 6. Workflows and Statuses: Customizing Your Process
- 7. Reporting and Dashboards: Monitoring Progress
- 8. Best Practices, Tips, and Integrations
1. 1. Introduction to Jira and Agile Basics
What Is Jira? Imagine a small software team that has just landed its first client project. The deadline is tight, the feature list is growing, and every day a new bug or request pops up in the developers’ inboxes. Without a single source of truth, the product owner cannot see what’s been promised, the developers cannot tell which task is highest priority, and the client receives conflicting updates. Enter Jira – a web‑based tool created by Atlassian that lets teams capture, organize, and track work in one place. At its core, Jira is an issue‑tracking system. In Jira terminology, an issue is any unit of work that needs to be completed – a user story, a bug, a task, a sub‑task, or even a change request. By storing all issues in a central repository, the team gains visibility, accountability, and a shared language for discussing work. Jira was originally built for software development teams, but over the years it has expanded to support marketing, HR, operations, and virtually any type of project that benefits from structured work tracking. Its flexibility stems from two design principles: 1. Customizable data model – you can add fields, create new issue types, and define workflows that match the way your team actually works. 2. Extensible ecosystem – a marketplace of add‑ons and integrations lets you connect Jira to source‑code repositories, test tools, chat platforms, and more. Because Jira is delivered as a cloud service (Jira Cloud) and also as a self‑hosted option (Jira Server/Data Center), teams of any size can start using it without worrying about infrastructure. --- Agile Foundations: Scrum and Kanban Before diving deeper into Jira, it helps to understand the two most common Agile frameworks that Jira supports out of the box: Scrum and Kanban. Both stem from the Agile Manifesto, a set of values and principles that emphasize delivering value early, embracing change, and collaborating closely with customers. Agile in a Nutshell - Iterative development – work is delivered in small increments rather than a single, massive release. - Customer collaboration – frequent feedback loops keep the product aligned with user needs. - Adaptive planning – plans are revisited regularly, allowing the team to respond to new information. - Cross‑functional teams – developers, testers, designers, and product owners work together, sharing responsibility for the outcome. Scrum Scrum structures work around time‑boxed iterations called sprints (usually 2‑4 weeks). The key events are: | Event | Purpose | Typical Duration | |-------|---------|------------------| | Sprint Planning | Choose a set of backlog items to deliver. | 1–2 hours for a two‑week sprint | | Daily Stand‑up | Share progress, impediments, and plan the day. | 15 minutes | | Sprint Review | Demonstrate …
2. 2. Setting Up Your Jira Account and Navigating the Interface
Why a Personal Jira Account Matters Imagine you’ve just been hired as the Product Owner for a fast‑growing startup. The team is already using Scrum, daily stand‑ups are happening, and a sprint backlog is waiting to be filled. Your first task? Log into the company’s Jira Cloud instance, set up your profile, and make sure you receive the right notifications so you never miss a sprint‑planning meeting or a critical bug report. Even before you can dive into boards and issues, you need a Jira Cloud account of your own and a clear sense of where the main navigation lives. This chapter walks you through every click, from signing up for a free trial to customizing the settings that keep your work visible and your inbox tidy. --- Creating Your Jira Cloud Account 1. Pick the Right Subscription Tier Jira Cloud offers several subscription tiers (Free, Standard, Premium, Enterprise). For a beginner or a small team, the Free tier is often enough: | Tier | Who it’s for | Core limits | |------|--------------|-------------| | Free | Up to 10 users, learning or small projects | 2 GB storage, 50 GB file upload, 2 GB attachment per file | | Standard | Growing teams that need more automation | Unlimited users, 250 GB storage, SLA 99.9% | | Premium | Large organisations needing advanced reporting | All Standard features + Advanced Roadmaps, 24/7 support | | Enterprise | Very large, regulated enterprises | Custom contracts, dedicated support | Tip: Start with the Free tier. You can upgrade later without losing any data. 2. Sign‑Up Walk‑through 1. Open a browser and go to <https://www.atlassian.com/software/jira. 2. Click “Try it free” (or “Get started” if you see a different landing page). 3. You’ll be asked for an email address. Use a personal or work email you can access—Jira will send a verification link. 4. Create a password that meets the on‑screen strength requirements (usually at least 8 characters, a mix of letters, numbers, and a symbol). 5. Choose a site name. This becomes part of your URL, e.g., https://myteam.atlassian.net. Pick something short and memorable. 6. Select a subscription tier (Free, Standard, etc.) and confirm the choice. 7. Accept the Atlassian Cloud Terms of Service. If you’re joining an existing organization, they may have a separate agreement you’ll need to sign later. 3. Verify Your Email After submitting the form, Atlassian sends a verification email: - Open the email and click the “Verify email” button. - If you don’t see the email within a few minutes, check your spam folder or request a new link. Once verified, you’ll be taken to the Jira Cloud onboarding wizard. You can skip the optional “Create a project” step …
3. 3. Creating and Managing Projects
Jump‑in: Your First Project in Jira Imagine you’ve just joined a small startup that builds a mobile app. The product owner has a backlog of features, the developers are ready to start sprinting, and the manager wants a single place to see what’s being worked on, who is responsible for what, and when work will be delivered. Your task? Create the project that will become the single source of truth for the whole team. In the next few pages you’ll walk through exactly that process—no prior Jira experience required. By the end of this chapter you will be able to: Create a new project using the Scrum, Kanban, or Business template of your choice. Set the project key, name, and description so the project is identifiable to anyone in the organization. Adjust project permissions and access roles to make sure the right people can see and edit the right things. --- 1. Starting a New Project 1.1 Where to Begin From the previous chapter you know how to navigate the Jira interface. To create a project, locate the Projects dropdown in the top navigation bar and select Create project. Tip: If you don’t see the “Create project” option, you may not have the Jira Administrator global permission. Ask your admin to grant you the Project Creation permission (covered in the permissions section below). 1.2 Choosing a Template Jira ships with three starter templates that map directly to common ways teams work: | Template | When to Use It | Core Features | |----------|----------------|---------------| | Scrum | Teams that work in time‑boxed iterations (sprints) and need backlog refinement. | Backlog view, sprint board, burndown chart. | | Kanban | Teams that focus on continuous flow, limiting Work In Progress (WIP). | Kanban board, cumulative flow diagram, WIP limits. | | Business | Non‑technical groups (HR, marketing, finance) that track tasks, requests, or approvals. | Simple issue types, custom fields, no sprint concepts. | Select the template that matches your team’s workflow. For our startup scenario, the product owner prefers Scrum, so we’ll click Scrum. Note: You can switch templates later, but it may involve re‑configuring issue types and workflows. It’s easier to pick the right one up front. 1.3 Naming the Project After selecting a template, a dialog appears with three mandatory fields: 1. Project name – A friendly, human‑readable label (e.g., Mobile App – MVP). 2. Project key – A short, uppercase identifier that prefixes every issue (e.g., MAP). This key appears in issue URLs, reports, and notifications. 3. Project description – Optional free‑text that explains the purpose, scope, or any special notes. This description is displayed on the project’s Summary page and can be useful for new team members. …
4. 4. Working with Issues: Creating, Editing, and Tracking
A Day in the Life of a New Jira User Imagine Maya, a junior product analyst who has just been added to a newly created project for an upcoming mobile app. Her manager asks her to capture the first batch of work items that the development team will tackle next week. Maya opens Jira, creates a handful of issues, fills in the necessary details, links a couple of bugs to a larger Epic, and then runs a quick search to see which items are still “To Do.” By the end of the hour she has a clean, searchable backlog that the whole team can rely on. If Maya can do this, so can you. The steps she follows are the building blocks of every Jira workflow: creating issues, populating fields, updating status, adding comments, and filtering with JQL. Let’s walk through each of these actions, layer by layer, so you can replicate Maya’s success on your own projects. --- 1. Creating Issues – The Core of Jira 1.1 What Is an Issue? In Jira, an issue is any unit of work that needs to be tracked. The platform is flexible enough to let teams call issues “Stories,” “Tasks,” “Bugs,” “Epics,” or any custom type they prefer. Each type carries its own default fields and workflow steps, but all share a common structure: a summary, a description, an assignee, and a status. | Issue Type | Typical Use | Typical Size | |------------|-------------|--------------| | Story | A user‑oriented feature or requirement | Small‑to‑medium (often fits in a sprint) | | Task | General work that may not map to a user story (e.g., documentation) | Variable | | Bug | Defect or error discovered in the product | Small, focused | | Epic | Large body of work that can be broken into multiple Stories/Tasks | Large, spans multiple sprints | 1.2 The “Create Issue” Dialog 1. Navigate to the project – From the project list you built in Chapter 3, click the project name (e.g., Mobile‑App‑Release). 2. Click the “Create” button – It sits in the top navigation bar and opens the Create Issue dialog. 3. Select the issue type – A dropdown lets you pick Story, Task, Bug, or Epic. 4. Fill in the required fields – At minimum you need: - Summary – A concise, one‑sentence title. - Description – A longer free‑text field where you can add context, acceptance criteria, or steps to reproduce a bug. - Assignee – The team member who will own the work. (If you leave it blank, the issue will be unassigned.) - Priority – Indicates the relative importance (e.g., Highest, High, Medium, Low). 5. Add optional fields – Depending on your …
5. 5. Boards and Backlogs: Scrum and Kanban Basics
A Real‑World Situation: The Release‑Ready Team Imagine a three‑person product team at a startup that just landed a new client feature request: “Add a customizable dashboard for end‑users.” The product owner (PO) has already broken the request into several user stories—design mock‑ups, API endpoint, front‑end widgets, and acceptance testing. The team needs a way to: see all the work items in one place, decide which items to tackle first, and track progress day‑by‑day. They have a Jira project already set up (see Chapter 3). Now they must choose the right board type—Scrum or Kanban—and learn the essential actions that keep the board useful. The steps below walk you through exactly that, from creating the board to running a sprint or managing flow, all inside Jira’s web UI. --- 1. Boards 101: Scrum vs. Kanban | Aspect | Scrum Board | Kanban Board | |--------|-------------|--------------| | Purpose | Organize work into time‑boxed iterations called sprints | Visualize continuous flow of work and limit Work‑In‑Progress (WIP) | | Backlog | Central place for prioritised items that will be pulled into a sprint | Optional backlog; items can be added directly to the board | | Planning cadence | Sprint Planning (once per sprint) | Ongoing pull‑in when capacity allows | | Metrics | Velocity, sprint burndown | Cumulative flow diagram, cycle time | | Typical use | Teams that deliver in regular releases (e.g., every 2 weeks) | Teams that need steady throughput or have unpredictable arrival of work | Both boards share the same underlying issues (stories, tasks, bugs) that you already know how to create (Chapter 4). The main difference lies in how you move those issues through columns and when you commit to work. Quick tip: If your team likes a regular cadence and wants to estimate effort, start with a Scrum board. If work arrives irregularly and you prefer a pull‑system, Kanban may be a better fit. --- 2. Setting Up a Scrum Board 2.1 Create the Board 1. From the project sidebar, click Boards View all boards. 2. Click Create board (top‑right). 3. Choose Scrum board → Create a Scrum board. 4. Name it (e.g., “Dashboard Feature – Scrum”) and select the project you created earlier. 5. Click Create board. Jira automatically generates three columns: To Do, In Progress, and Done, and links the board to the project’s backlog. 2.2 Populate the Backlog Navigate to the Backlog view (the left‑hand tab under the board name). Click Create issue or use the + button to add the user stories you identified: | Issue Type | Summary | Example | |------------|---------|---------| | Story | Design mock‑ups for dashboard | “UX: Create dashboard layout” | | Story | Build API …
6. 6. Workflows and Statuses: Customizing Your Process
Understanding Workflows and Statuses A workflow is the map that tells Jira how an issue moves from start to finish. Think of it as a flowchart: each box is a status (e.g., To Do, In Progress, Done) and each arrow is a transition that moves the issue from one status to another. When you created your first project in Chapter 3, Jira automatically attached the default workflow to every issue type. That workflow is deliberately simple so you can start tracking work right away. As your team matures, you’ll want the workflow to match the way you actually deliver value—adding review steps, QA gates, or any custom state your process requires. Scenario – The “Design‑Review‑Deploy” team The team uses the default workflow, but their definition of “Done” actually means “Deployed to Production”. They also need a separate “Design Review” step that only senior designers can perform. By customizing the workflow, they can make the board reflect the real life steps they follow, and prevent anyone from accidentally moving a ticket straight to Done without the required review. --- Visualizing the Default Workflow Diagram Where to Find It 1. Click the cog (⚙️) in the top‑right corner and choose Issues. 2. In the left sidebar, expand Workflows and select Workflow Schemes. 3. Click the name of the scheme that is attached to your project (usually Default Workflow Scheme). 4. In the list of workflows, click Diagram next to Default Workflow. The diagram that appears is the visual representation of the default workflow. What the Default Diagram Shows | Status | Description (beginner‑friendly) | |--------|-----------------------------------| | To Do | The issue has been created but work hasn’t started. | | In Progress | Someone is actively working on the issue. | | Done | The work is finished and accepted by the team. | Arrows (transitions) connect these statuses: - Start Progress – moves an issue from To Do → In Progress. - Stop Progress – moves an issue from In Progress → To Do (useful if work is blocked). - Resolve Issue – moves an issue from In Progress → Done. - Reopen Issue – moves an issue from Done → In Progress (if a defect is found). The default workflow is deliberately linear, but you can see how each transition is a path that a user can take. --- Adding, Editing, and Deleting Statuses 1. Adding a New Status 1. In the Workflow Designer, click Add status (the plus icon on the toolbar). 2. Give the status a name (e.g., In Review). 3. Choose a category: - To Do – for work not started. - In Progress – for work underway. - Done – for completed work. 4. Click Add. …
7. 7. Reporting and Dashboards: Monitoring Progress
A Real‑World Prompt: The Sprint Review That Went Wrong Imagine you are the Product Owner for a newly‑formed Scrum team. The sprint just ended, and you need to present the results to senior leadership. You open the sprint’s burndown chart, but the line is jagged and the scope‑change column is missing. The velocity numbers look lower than expected, and nobody can tell why. Meanwhile, the Kanban team next door is confidently showing a cumulative flow diagram (CFD) that clearly illustrates where work is piling up. What went wrong? Most likely the team never set up the right reports, didn’t configure a dashboard that surfaces the right gadgets, and the filters they rely on are hidden in a personal view that no one else can see. This chapter walks you through the exact steps to avoid that situation—turning raw issue data into clear, shareable visuals that keep your project health visible to every stakeholder. --- Generating Core Agile Reports Jira automatically creates several agile reports for every Scrum or Kanban board. These reports visualise the flow of work and help you answer the three classic questions of agile monitoring: | Question | Report | What It Shows | |----------|--------|---------------| | Are we on track to finish the sprint? | Burndown Chart | Remaining effort (story points or hours) versus time. | | How much work can we reliably deliver? | Velocity Chart | Amount of work completed per sprint, useful for forecasting. | | Where is work getting stuck? | Cumulative Flow Diagram | Count of issues in each status over time, highlighting bottlenecks. | Below are step‑by‑step instructions to generate each report for beginners. 1. Burndown Chart (Scrum) 1. Navigate to your Scrum board – From the Projects list, select the project you created in Chapter 3, then click the board name under Boards. 2. Open the Reports menu – In the left‑hand sidebar, click Reports. 3. Select “Burndown Chart.” Jira will display a graph with two axes: X‑axis: Days of the sprint (usually Monday‑Friday). Y‑axis: Remaining effort (story points by default). 4. Interpret the line – A smooth downward slope indicates steady progress. Spikes upward show scope changes (new issues added). If the line stays flat, the team isn’t completing work. 5. Adjust the effort unit – Click the gear icon on the chart and switch between Story Points, Original Estimate, or Remaining Estimate depending on what your team tracks. Tip: If you don’t see a burndown chart, verify that the board is associated with a Sprint (the sprint must be started and then closed). The chart only appears after a sprint has been completed. 2. Velocity Chart (Scrum) 1. From the same Reports menu, choose Velocity Chart. 2. …
8. 8. Best Practices, Tips, and Integrations
Naming Conventions & Issue Hierarchy: Building a Clean, Scalable Structure Imagine a newly‑formed product team that has just launched its first Scrum board in Jira. Within a week they have created dozens of user stories, bugs, and sub‑tasks. By the end of the sprint, the backlog is a chaotic mix of “Bug‑123”, “Story‑Login”, “Task‑UI‑Fix”, and “Improvement‑Performance‑Cache”. When it comes time to generate a sprint report (see Reporting and Dashboards), stakeholders can’t tell which items belong to which feature, and the Product Owner spends precious hours cleaning up the list instead of planning the next increment. A disciplined naming scheme and a clear issue hierarchy prevent this scenario from ever happening. Below are the core practices you can adopt immediately. 1. Adopt a Predictable Prefix System | Issue Type | Recommended Prefix | Example | |------------|-------------------|---------| | Epic | EPI- | EPI-User‑Management | | Story | STO- | STO-Login‑Page | | Bug | BUG- | BUG-Password‑Reset‑Fail | | Task | TSK- | TSK-Update‑Docs | | Sub‑task| inherit from parent (no prefix needed) | Sub‑task: UI‑Fix | - Why it works: The prefix instantly tells anyone scanning a board or a report what kind of work they are looking at. - Tip: Keep the prefix short (3‑5 characters) and consistent across all projects. If you manage multiple products, add a short product code after the prefix, e.g., STO‑PAY‑Checkout‑Flow. 2. Use Descriptive, Yet Concise, Summaries - Structure: [Action] – [Feature/Component] – [Outcome] - Example: Implement – Checkout – Save payment method Avoid vague titles such as “Fix bug” or “Add feature”. A clear summary improves searchability and helps the team understand the work at a glance. 3. Leverage Issue Links to Reflect Real‑World Relationships Jira lets you link issues with relationships such as “blocks”, “is blocked by”, “relates to”, “duplicates”, and “clones”. Use them to model: - Epic → Story → Sub‑task hierarchy (automatically created when you select “Epic Link” and “Parent” fields). - Technical dependencies (e.g., a story that “blocks” a bug fix). When you later run a Release Burndown or Epic Report, these links give the system the context it needs to calculate accurate metrics. 4. Keep the Issue Hierarchy Shallow - Rule of thumb: No more than three levels (Epic → Story → Sub‑task). - Deep hierarchies become difficult to visualize on boards and can cause confusion in reports. - If you need additional granularity, consider components (a built‑in field) or custom fields rather than adding another level of issues. 5. Standardize Components and Labels - Components: Represent logical parts of your product (e.g., UI, API, Database). They appear in the Component Report and can be used to filter dashboards. - Labels: Free‑form tags for cross‑cutting concerns (e.g., performance, security, …
Continue learning
- Advanced Jira Administration and Configuration MasteryAdvanced Jira Administration and Configuration Mastery — a free advanced-level guide covering advanced jira administration and configuration. Learn...
- Advanced Jira workflows for project managersAdvanced Jira workflows for project managers — a free advanced-level guide covering advanced jira workflows for project managers. Learn with clear...
- Learn to Use Slack for Business: A Beginner's GuideLearn to Use Slack for Business: A Beginner's Guide — a free beginner-level guide covering learn to use slack for business. Learn with clear...
- Photoshop Basics for Absolute Beginners: Step-by-Step GuidePhotoshop Basics for Absolute Beginners: Step-by-Step Guide — a free beginner-level guide covering learn to use photoshop for absolute beginners. Learn...