Tools And Frameworks

>

Agile

Getting Started

PM Roles and Responsibilities

Communication

1-on-1 Guide Conflict Resolution Developer and Designer Communication

Tools and Frameworks

GitHub - Best Practices for Commits and Branches JIRA, Kanban Boards, and Agile Methodologies Managing User Stories

Wrap Up

Project Wrap Up

JIRA, Kanban Boards, and Agile Methodologies

Estimated Time: ~30 minutes

Overview

What is JIRA?

JIRA is an issue and project tracking software commonly used in industry to help track progress on software development work.

What is a Kanban Board?

Kanban Boards help us track the progress of individual issues as they progress through the software development lifecycle.

What are Agile Methodologies?

Agile encourages frequent meetings and weekly task goals so that project expectations and specifications can shift as it evolves, compared to the more “traditional” methodology of deciding everything before work begins on a project.

Kanban Boards and Agile Methodologies

Key Takeaways:

  • Kanban Boards help us keep a good track of our progress on our overall projects and individual issues as they constantly change and evolve - which they will as we use Agile Methodologies to create our tasks - more on this later.
    • On Jira, we use five columns in our Kanban Boards - backlog, get next, in progress, ready for review, and done.
  • A “user story” (often called many different names) represents a singular issue or subtask that we are currently trying to solve and are actively tracking on our Kanban Board.
  • Agile is a style of development that encourages actively figuring out user stories and tasks as the software evolves - it opts for frequent weekly sprint meetings and weekly task goals so that expectations and specifications can easily be shifted as time and the project itself evolves.

How to Use JIRA

Key Takeaways:

  • JIRA is an industry-standard issue and project tracking software.
  • We use Kanban Boards with different swimlanes to represent the status of different “user stories” within different various subtopics.
  • When you create a story on Jira, it automatically generates a story key that we use to refer to it both on Jira and in our GitHub commits.
    • These stories also have an “issue priority” that represents how fast we need to get to solving it.
  • When a new batch of stories is done on Jira and set into the “Done” column, we can release them to clear the board of clutter.