Lecture on Jira and Agile Methodology

Introduction

• Jira: A project management and issue-tracking tool.
  • Origin: Name derived from 'Gojira' (Japanese for Godzilla).
  • Main Use: Agile project management.
  • Other Methodologies Supported: Can be customized via plugins and apps.
• Focus: Understanding core Agile concepts since Jira operates based on Agile principles.
• Note: If familiar with Agile, skip introductory videos on Agile concepts.

Agile Overview

Agile Methodology

• Core Concepts:
  • Adaptive planning
  • Evolutionary development
  • Early delivery
  • Continuous improvement
  • Rapid and flexible response to change
• Agile Tools: Digital and physical (Jira, whiteboards, etc).
• Key Element: Agile board with columns (lanes) representing workflow states (e.g., To Do, In Progress, Done).

Agile Boards

• Columns (Lanes): Represent different steps in a project.
  • Basic board: To Do, In Progress, Done.
  • Customization: Additional columns can be added.

Agile Workflows

• Scrum:
  • Based on sprints (fixed time periods for completing tasks).
  • Sprint Planning: Meetings to discuss last and next sprints.
  • Day-to-Day: Moving tasks across the board.
  • Completion: Reviewing the sprint, solving roadblocks, discussing improvements.
• Kanban:
  • Continuous workflow; tasks are moved across the board ongoingly.
  • No fixed sprints; tasks added dynamically.

Summary

• Scrum vs. Kanban: Main difference is the use of sprints in Scrum.
• Agile Board Setup: Columns and customization to fit workflow needs.

Jira Agile Terms

Stories and Epics

• User Stories: Terminology inside Agile for tasks.
  • Example: "As a web developer, I want to add users to Jira so that my co-workers can report bugs."
  • Structure: As a [type of user], I want [goal] so that [reason].
• Epics: Large user stories broken into smaller tasks (stories).
  • Used for long-term projects spanning multiple sprints.
  • Hierarchy: Epics contain multiple user stories.

Issues and Projects

• Issues: Central to Jira; represent tasks, bugs, or user stories.
  • Containers for data fields like description, summary, assignee, due date, etc.
• Projects: Collections of issues.
  • Projects define where issues reside and include various settings and types.
  • Customizable by access and permissions.

Jira Interface Overview

• User Interface: Familiarize yourself with sections like the dashboard, projects, filters, dashboards, people, apps, and user settings.
• Navigation: Utilize shortcuts and quick filters for efficient management.
• Contextual Features: Utilize features like search, notifications, and help.

Detailed Exploration

• Team-Managed Projects vs. Company-Managed Projects:
  • Team-managed: Simplified, project-contained entities, no admin permissions required.
  • Company-managed: Complex, shared entities across projects, requires admin permissions.
• Project and Issue Customization: Add custom fields, issue types, and more.

Practical Applications

• Creating Projects and Issues:
  • Different methods and detailed steps to creating both team-managed and company-managed projects.
  • Screens for creating issues directly in Jira and from the board.
• Sprints and Boards:
  • Managing sprints, adding issues, and using various board views.
  • Customizing boards for specific needs.
• Sample Data: Enable sample data to better understand and practice Jira functionality.

Conclusion

• Key Takeaways: Understanding core Agile concepts and Jira’s interface crucial for efficient project management.
• Continuous Learning: Customize Jira per project needs and utilize resources (help section, support) extensively.
• Future Sections: Diving deeper into company-managed projects, advanced customizations, and automation.