Tooling Talk: Jira, GitHub, and Slack

Your tools define your day. In this lesson, we'll look at the specific English used around the "Big Three" of tech productivity.

1. Jira (Project Management)

Jira is where "Tickets" live.

• Ticket/Issue: A single unit of work.
• Epic: A large body of work that can be broken down into smaller tasks.
• Story Points: A measure of effort (not time).
• Status: Where the ticket is (e.g., In Progress, In Review, Done).

Common Phrase: "Can you ticket that?" (Using 'ticket' as a verb means to create a formal record of a request).

2. GitHub (Version Control)

GitHub is where the code lives. Even if you aren't an engineer, you need to know these terms:

• Repo (Repository): The folder where the code is stored.
• Branch: A version of the code where you make changes without affecting the main version.
• Commit: To save your changes to the branch.
• PR (Pull Request): Asking the team to review and "merge" your changes into the main code.

Common Phrase: "I'll open a PR for those copy changes."

3. Slack (Communication)

Slack is the "digital HQ." The language here is fast and informal but professional.

• Thread: A sub-conversation under a message. (Always use threads to keep channels clean!)
• DM (Direct Message): A private message.
• Channel: A room for a specific topic (e.g., #eng-team, #product-launches).
• @mention: Tagging someone to get their attention.

Common Phrase: "Let's take this to a thread." (Used when a conversation is getting too long for the main channel).

Alex's Tip: In Slack, avoid just saying "Hi." State your request or question in the first message. Tech culture values "asynchronous efficiency"-don't wait for a "Hi" back before explaining why you are messaging.

The daily standup is the meeting you will attend most often. Keep your update to under two minutes and follow the three-part structure:

1. Yesterday : what you completed since the last standup.
2. Today : what you plan to work on today.
3. Blockers : anything slowing you down or blocking your progress.

A clean standup update sounds like this:

Yesterday I finished the login bug fix and opened a PR. Today I'll start on the dashboard charts. No blockers.

Notice the verbs: finished, opened, start on, and the short no blockers at the end. This concise pattern is what managers and teammates expect.

Common mistakes

1. Saying the meeting instead of standup. Standup is the name. Scrum also means the daily meeting in some teams, but standup is more common.
2. Using velocity wrong. Velocity is how much work a team completes per sprint. Say our velocity dropped this sprint, not our speed dropped.
3. Calling a ticket a task every time. In agile tools, work items are usually tickets, issues, or stories. Task is fine but less specific.

Practice

Write a 30-second standup update using the three-part structure. Try it out loud:

• Yesterday I _.
• Today I'll _.
• Blockers: _.

You now have the vocabulary of the team's rhythm. In the next lesson, you will learn the product and business vocabulary that surrounds all of this work, from MVP to product-market fit.