UNIT 1 — Software Project Management Labs in Jira (Step-by-Step with

Examples)
BCA Seventh Semester • Tool: Jira Cloud (free plan or trial)

Sample Case Used Throughout: “Online Appointment Booking System” (Web + Mobile)
What You Will Produce in UNIT 1
 A Scrum project in Jira with initiation artifacts modeled as issues.
 Custom issue types and fields for Charter, Stakeholder, Risk, and Change Request.
 A Stakeholder Register filter + an initiation dashboard (with a 2D matrix).
 A lightweight WBS using Epics → Stories → Tasks with a Release (v1.0).
 A Roadmap for epics, prioritized backlog, and Sprint-0 for initiation tasks.
 A Unit-1 dashboard with JQL-driven gadgets.
Lab U1-1: Create Jira Account & Scrum Project
Objective: Set up Jira Cloud and a Scrum software project.

Prerequisites
 Stable internet; any email address (student email preferred).

Steps
1. 1. Open https://www.atlassian.com/software/jira and click “Try it free”. Choose Jira
Software.
2. 2. Create/Sign-in to your Atlassian account. Follow prompts to create a site (e.g., oabs-
team.atlassian.net).
3. 3. When asked for a template, choose “Scrum”. Select “Team-managed” (simpler) or
“Company-managed” (more control).
4. 4. Project name: Online Appointment Booking System. Project key: OABS.
5. 5. Go to Project settings → Features and toggle ON: Backlog, Board, Roadmap, and
Releases.
6. 6. Optional: Invite 1–2 classmates via Project settings → People → Invite. Assign role
“Member”.

Example Values
Field Example

Site oabs-team.atlassian.net

Project name Online Appointment Booking System

Key OABS

Template Scrum (Team-managed)

What to Submit
 Screenshot: Project settings → Features page (showing
Backlog/Board/Roadmap/Releases enabled).
 Project URL and Project key.
Lab U1-2: Configure Issue Types & Custom Fields (Initiation Artifacts)
Objective: Model Charter, Stakeholder, Risk, and Change Request as first-class issue types in
Jira.

Where to Configure
 Team-managed: Project settings → Issue types (configure inside the project).
 Company-managed: ⚙️Jira settings (top-right) → Issues → Issue types & Custom fields →
Add fields → Add to appropriate screen scheme.

Create Issue Types

7. 1. Add issue types: Charter, Stakeholder, Risk, Change Request.
8. 2. For each issue type, add fields as below. (Team-managed: “Add field” inside the issue
type.)

Fields to Add (with Examples)

Charter

Field Type Example

Business Objective Paragraph Reduce clinic wait times by

enabling online
appointment booking

Scope Paragraph Web portal + Android app;

booking, reminders,
payments

Assumptions Paragraph Doctors share availability;

SMS gateway available

Constraints Paragraph Budget NPR 15L; Go-live in

12 weeks

Success Criteria Paragraph ≥70% online bookings in 3

months; NPS ≥ 50

Stakeholder

Field Type Example

Role Short text Sponsor / PM / Tech Lead /

QA Lead / Legal / Ops

Influence Number (1–5) 5

Interest Number (1–5) 4

Contact Email sponsor@client.org

Risk

Field Type Example

Probability Select (1–5) 4

Impact Select (1–5) 5

Exposure Number (calc) 20

Response Select Mitigate / Avoid /

Transfer / Accept

Owner User picker PM

Change Request

Field Type Example

Reason Paragraph Add telemedicine video

calls

Impacted Areas Checkboxes Scope, Schedule, Cost,

Quality

Impact Summary Paragraph Add 120 Dev hrs, 20 QA hrs;

+2 weeks; NPR 180,000

Decision Select Proposed / Approved /

Rejected / Deferred

Automation (Optional, for Exposure)

9. 1. Project settings → Automation → Create rule → “Issue updated”.
10. 2. Condition: Issue Type = Risk.
11. 3. Action: Edit issue fields → Exposure = {{issue.Probability}} * {{issue.Impact}}.

What to Submit
 Screenshot of Issue type scheme with the 4 new types.
 Screenshot of a Risk issue showing Probability, Impact, Exposure, and Response fields
filled.
 List (or CSV) of custom fields created.
Lab U1-3: Project Charter & Stakeholder Register in Jira
Objective: Capture the charter and build a stakeholder matrix using filters and dashboards.

Steps
12. 1. Create a “Charter” issue (Issues → Create). Fill all fields; attach a one-page DOC/PDF if
you have a charter template.
13. 2. Create 6–10 “Stakeholder” issues (Client Sponsor, PM, Tech Lead, QA Lead, UI/UX,
Legal, Ops). Fill Influence and Interest (1–5).
14. 3. Save a filter for stakeholders: Search → View all issues → Type = Stakeholder AND
project = OABS → Save as “Stakeholder Register”. Share with your class team.
15. 4. Create a dashboard: Dashboards → Create dashboard “UNIT 1 — Initiation
Dashboard”.
16. 5. Add gadget “Two-Dimensional Filter Statistics”: Filter = Stakeholder Register; X-axis =
Influence; Y-axis = Interest.
17. 6. Add a Text gadget explaining: High-High = manage closely; High-Low = keep satisfied;
Low-High = keep informed; Low-Low = monitor.

Example Charter (filled)

Field Value

Business Objective Cut average wait time by 30% within 6

months via online bookings

Scope Doctor directory, slot booking, SMS/email

reminders, Stripe payments

Assumptions Clinic provides availability; OTP SMS

supported

Constraints Budget NPR 15L; Compliance with privacy

laws

Success Criteria ≥5,000 bookings in first 3 months; p95

booking API < 3s

What to Submit
 Link or screenshot of “Stakeholder Register” filter.
 Dashboard screenshot (2D matrix gadget visible).
 Charter issue screenshot.
Lab U1-4: Lightweight WBS via Epics → Stories → Tasks
Objective: Represent scope hierarchically and prepare a release.

Steps
18. 1. Add Epics: EP1 Registration & Auth; EP2 Doctor Directory; EP3 Booking Flow; EP4
Payments; EP5 Notifications.
19. 2. For each Epic, create 3–5 Stories. Example (EP3 Booking Flow): Search slots; Book
slot; Cancel/Reschedule; Confirmation email.
20. 3. Break one story into Tasks/Sub-tasks (Design, API, UI, Test).
21. 4. Add Definition of Done (checklist) to one story: peer review done; unit tests pass;
acceptance tests pass; docs updated.
22. 5. Releases → Create version “v1.0” (target date within 10–12 weeks).
23. 6. Set “Fix Version/s = v1.0” on 6–10 relevant issues.

Example Backlog Items

Type Key Summary

Epic EP3 Booking Flow

Story OABS-21 Book available slot

Task OABS-22 Build POST /appointments

API

Sub-task OABS-23 Add unit tests for booking

API

What to Submit
 Backlog screenshot showing Epics and child Stories.
 One Story screenshot with sub-tasks and DoD checklist.
 Releases page screenshot with v1.0 and assigned issues.
Lab U1-5: Roadmap, Backlog Prioritization & Sprint-0
Objective: Timeline epics, prioritize stories, and run a short initiation sprint.

Steps
24. 1. Enable Roadmap (Project settings → Features → Roadmap).
25. 2. Open Roadmap and set dates for each Epic to visualize sequencing (e.g., EP1 Aug 18–
Aug 29; EP3 Sep 1–Sep 26).
26. 3. Prioritize the backlog: drag stories; optionally add a custom “Business Value (1–5)”
field to help ranking.
27. 4. Create “Sprint-0 — Initiation” (1–2 weeks). Add Charter, Stakeholders, discovery
spikes (spike = research story).
28. 5. Start Sprint. Move issues across To Do → In Progress → Done as you simulate
progress.
29. 6. Reports → Burndown chart. Capture a mid-sprint screenshot.

Example MoSCoW Labels

Label Meaning Example Story

Must Mandatory for v1.0 Book available slot

Should High value, not critical Reschedule appointment

Could Nice to have Doctor ratings & reviews

Won’t Out of scope now Telemedicine video calls

(tracked as CR)

What to Submit
 Roadmap screenshot with epic bars and dates.
 Backlog screenshot showing prioritization (or Business Value field).
 Burndown chart screenshot for Sprint-0.
Lab U1-6: JQL, Reports & Unit-1 Dashboard
Objective: Use JQL filters and gadgets to report initiation status.

Steps
30. 1. Issues → Search → Switch to JQL. Example JQL:
project = OABS AND type in (Charter, Stakeholder, Risk, "Change Request") ORDER BY
updated DESC
31. 2. Save as filter “UNIT1 — Initiation Items”. Share with project members.
32. 3. Dashboards → Open “UNIT 1 — Initiation Dashboard”. Add gadgets:
• Filter Results (source: UNIT1 — Initiation Items)
• Pie Chart (Statistic Type: Issue Type)
• Created vs Resolved (over last 14 days)
• Text gadget with your narrative summary.
33. 4. Export the dashboard to PDF (if enabled) or take clear screenshots.

Useful JQL Snippets

Purpose JQL

Open initiation items project = OABS AND type in (Charter,

Stakeholder, Risk, "Change Request") AND
statusCategory != Done

Recent updates (last 7 days) project = OABS AND updated >= -7d

Risks with high exposure project = OABS AND type = Risk AND
"Exposure" >= 15

What to Submit
 Saved filter link + screenshot.
 Dashboard screenshots showing all gadgets.
 One paragraph status summary (Green/Amber/Red) in the Text gadget.
Appendix: Templates You Can Reuse

Change Request (CR) Minimal Template

Field Description / Example

Title Add Telemedicine Video Calls

Reason Market demand; competitor parity

Impacted Areas Scope, Schedule (+2 wks), Cost (+NPR

180,000), Quality (perf tests)

Risk Integration complexity; call quality issues

Decision Approved / Rejected / Deferred

Stakeholder Register CSV Columns

Column Example

Name Anita Sharma

Role Sponsor

Influence (1–5) 5

Interest (1–5) 4

Contact anita.sharma@client.org

Risk Register Fields

Field Example

Risk API latency exceeds 3s at p95

Probability (1–5) 3

Impact (1–5) 5

Exposure (P×I) 15

Response Mitigate: early perf tests; caching

Owner Tech Lead