Why is it called a scrum? State verbs and the present simple vs continuous

About this lesson

This lesson plan teaches state verbs and the present simple vs continuous to B1 learners of English for IT, through a Scrum team's week.

Grammar
Routines in the present simple (The sprint lasts two weeks.), work in progress in the continuous (Right now the tests are running.), and state verbs like need that stay simple.
Topic
Sprints and standups on the mobile team of Kestrel Cloud, a fictional payments startup, with words such as backlog, user story, timebox and retrospective.
Activities
The rugby story behind Scrum, the team's sprint page, a welcome call, self-checking drills, a chat and a wheel, then a message to a new teammate and a voice update.

What's inside

  1. Chapter 1Warm-up: How Does Your Team Work?

    • PictureUnlock
    • Open a box and talk about your teamOpen the boxUnlock
    • Study the words: Scrum at workVocabularyTry it
    • Look at the pictures and choose the wordChoose by pictureUnlock
  2. Chapter 2The Story: From Rugby to Software

    • Read the story: a rugby word at workArticleUnlock
    • Choose the correct answer about the storyQuizUnlock
  3. Chapter 3At Work: The Mobile Team's Sprint Page

    • Read the mobile team's sprint pageReal-life documentTry it
    • True or false? Check the sprint pageTrue or falseUnlock
    • Sort the sentences: how we usually work or this sprintSort into columnsUnlock
  4. Chapter 4Listen: Welcome to the Mobile Team

    • Listen to Beatriz and RuiListeningTry it
    • Transcript, for the teacherUnlock
    • Choose the correct answer about the callQuizUnlock
  5. Chapter 5Grammar: Usually or Right Now?

    • Study the scheme: usually or right now?Grammar schemeTry it
    • Choose the correct formChoose the optionTry it
    • Complete the second sentence with the same verbFill in the gapsUnlock
    • Choose the correct sentenceQuizUnlock
    • Fill in the gaps: Iryna's standup updateFill in the gapsUnlock
  6. Chapter 6Speak Up: Routines and This Week

    • Choose Iryna's best repliesChatTry it
    • Spin the wheel and answerSpin the wheelUnlock
  7. Chapter 7Homework: Your Team, Your Week

    • Read your phrase bankReal-life documentUnlock
    • Fill in the table: a typical week and this weekFill in the tableUnlock
    • Unscramble the Scrum wordsAnagramUnlock
    • Write a welcome message for a new teammateWriting, checked by the teacherUnlock
    • Record a voice update: a typical week and this weekSpeaking, checked by the teacherUnlock

Agile and Scrum vocabulary

12 words and phrases from the lesson, each with a picture and audio in edio.

+9 more with pictures and audio in the lessonMore words

  • a sprint goal
  • the backlog
  • a user story
  • a retrospective
  • a timebox
  • prioritize
  • estimate
  • demo
  • pick up a ticket

Grammar: present simple vs continuous and state verbs

A software team uses two presents side by side: one for how it always works, one for what it's doing at the moment. Moving between a sprint page and a standup, learners match each tense to its time words and keep state verbs simple, even right now: I need access, never I'm needing access.

Present simple or present continuous?

The present simple for how your team usually works; the present continuous for what is happening now or this sprint.

Two present tenses, two jobs

The present simple gives routines, facts and timetables: We review pull requests after lunch. The sprint lasts two weeks. The present continuous, am, is or are + -ing, gives actions in progress and temporary work: This week Jordan is testing the payouts screen.

Two present tenses

TenseFormUse it forExample
Present simpleI / you / we / they test; he / she / it tests; don't / doesn't test; Do / Does… test?routines, habits, facts, timetablesWe review pull requests after lunch.
Present continuousam / is / are + verb-ing: I'm testing; isn't / aren't testing; Are you testing…?actions now; temporary work this week or this sprintThis sprint I'm working on the login page.

From the lesson

  • The sprint lasts two weeks.a fact about how the team works
  • Beatriz prioritizes the backlog every week.a routine
  • In a scrum, players from both teams push together.a fact
  • Right now Iryna's building the payouts screen.an action in progress
  • This week Jordan is testing the payouts screen.temporary work

Time words point to the tense

Usually, always, every sprint and on Mondays go with the present simple; right now, at the moment, this week and currently go with the continuous. And a task under way today takes -ing: Today I'm working on the login bug.

With the present simpleWith the present continuous
usually, always, often, neverright now, now, at the moment
every day, every sprint, on Mondaysthis week, this sprint, currently
every other Monday, once a weektoday (work in progress), Look!

State verbs stay simple

Verbs for states rather than actions rarely take -ing, even when the state is true at this moment: need, want, know, understand, mean, depend, belong, like. So a blocker sounds like I need access to the repo, and a reply like Sorry, I don't know who owns this ticket.

  • need, want, know, understand, mean, depend, belong, like
  • I need access to the repo. (not I'm needing)
  • Sorry, I don't know who owns this ticket.
  • The release date depends on the test results.

Both tenses at the standup

A standup update mixes the two: the continuous for your own work in progress (I'm fixing…, We're testing…), the simple for the team's fixed habits (We plan every other Monday.), and often a state verb for the blocker: The screen needs real payout data.

At the standup

Talk about your work in progress with the present continuous: I'm fixing…, We're testing… Talk about how your team works with the present simple: We plan every other Monday. The standup lasts 15 minutes.

Spelling

  • -s: test → tests, fix → fixes, reply → replies
  • -ing: test → testing, write → writing, take → taking
  • -ing: run → running, set → setting, plan → planning

Typical mistakes

  • I'm needing access to the repo.

    I need access to the repo.

    need is a state verb

  • Today I work on the login bug.

    Today I'm working on the login bug.

    work in progress today

  • Usually I'm doing the reviews.

    I usually do the reviews.

    a routine

  • This week she works from home.

    This week she's working from home.

    a temporary change

More lessons on this grammar: Present simple vs present continuous lessons and exercises · Present simple lessons and exercises · Present continuous lessons and exercises

Try the state verbs exercises

Try them yourself: these are the same exercises your students do in edio.

What's in the lesson

  • 11 auto-checked exercises
  • 3 games
  • 2 teacher-checked tasks
  • 2 real-life documents
  • 1 article
  • 1 grammar scheme
  • 1 set of word cards
  • 1 audio clip
  • 1 picture
  • 1 transcript

The main objectives of this lesson are to:

  • describe your team's routines with the present simple: We plan every other Monday. The standup lasts fifteen minutes.
  • say what's happening now or this sprint with the present continuous: This sprint I'm working on the login page.
  • use state verbs in the simple form, even about this moment: I need access to the repo, not I'm needing access
  • welcome a new teammate with how the team works and what everyone is doing this week: Need a task? Pick up the top ticket in the backlog.

Lesson 4 opens The daily standup, unit 2 of English for IT B1 · Inside the Team, which trains learners to give a clear update, flag a blocker and ask for help. It sets lesson 1's present simple beside the present continuous, a pair first contrasted in English A1.2 lesson 25, and adds state verbs, the usual trap in a blocker. Lessons 5 and 6 bring just, already and yet, then have to. A sprint mixes fixed routines with changing work, so both tenses come up daily.

Open boxes about the learners' teams come first, then twelve words with pictures and audio, from a scrum to pick up a ticket, and a picture quiz. The story shows how a 1986 article compared product teams to rugby players, and how Scrum got its name. Students check the mobile team's sprint page as true or false and sort its sentences into usual work and this sprint. In an AI-voiced call, the product owner welcomes a developer joining for one sprint. Four self-checking drills follow the scheme, the last a standup update with gaps; a chat with a friend about the new job and a wheel of questions come next.

Homework starts with a phrase bank; a table of a typical week beside this week and an anagram of Scrum words then check themselves. Students write a welcome message for a new teammate and record a voice update on a typical week and this week, both for the teacher to review.

Grammar:
present simple vs present continuous · state verbs
Topic:
Scrum · sprints · how a team works

Teaching tips

  • Draw two columns before the sprint page, every sprint and this sprint, and let learners fill them with facts about their own team; the column sort after the reading checks the same split.
  • Run a short standup in class: each learner gives one routine, one task in progress and one need, and the group catches any I'm needing. In-company groups can use their real tickets.
  • Ask about rugby before the story: has anyone seen a scrum, and why would a software team borrow the word? The answers prepare the article's contrast between a relay race and a rugby team.
  • One-to-one, trade weekly voice updates: the learner records a typical week and this week, you answer in kind, and together you mark each verb as a routine or work in progress.

Liked it?

Teach the whole lesson in edio

24 exercises in 7 chapters, ready to teach. edio is an online platform for language schools and teachers: ready-made interactive lessons, live classes, homework and student progress in one place.

  1. Start a free trial

    7 days, no credit card.

  2. Open the lesson

    Find it in the library of 621 ready lessons. Teach it as it is, or copy any chapter into your own lessons.

  3. Teach it live or as homework

    Students work in their own accounts, in sync with you during the lesson, and the practice exercises check themselves.

The whole course: English for IT B1 · Inside the Team

24 lessons at B1 for people who build, test or run software, in American English. Learners follow Iryna, a junior developer, through her first year at Kestrel Cloud, a fictional payments startup: standups, tickets, code review, chats across time zones and job interviews. Each lesson is built around a true story from software history.See the course

  1. Unit 1 Hello, team

    roles, stacks and first days: the present simple, the present perfect with for and since, question forms

    1. Lesson 1How big is a two-pizza team?Present simple for jobs and responsibilities
    2. Lesson 2Your first "Hello, World"Present perfect with for and since
    3. Lesson 3Write your personal READMEQuestion forms for getting to know colleagues
  2. Unit 2 The daily standup

    updates and blockers: the present simple and continuous, just, already and yet, have to and need to

    1. Lesson 4 · you're hereWhy is it called a scrum?Present simple vs continuous and state verbs
    2. Lesson 5Done, not done yetPast simple, present perfect and going to for updates
    3. Lesson 6Help, I'm blocked!Have to, need to, don't have to and can't
  3. Unit 3 Bugs and tickets

    clear bug reports: the past continuous, imperatives and the zero conditional, quantifiers

    1. Lesson 7The first actual bugPast simple and past continuous for bug stories
    2. Lesson 8Steps to reproduceImperatives and the zero conditional for bug reports
    3. Lesson 9The email that couldn't go 500 milesQuantifiers in bug tickets
  4. Unit 4 Code review

    kind, useful comments: -ed and -ing adjectives, modals for suggestions, the first conditional

    1. Lesson 10What's a nit?-ed and -ing adjectives in review comments
    2. Lesson 11Could we maybe…?Modals for suggestions in code review
    3. Lesson 12Your first pull requestThe first conditional and unless in code review
  5. Unit 5 How it works

    explaining systems step by step: time clauses, the passive, relative clauses

    1. Lesson 13What happens when you type a URL?Time clauses with as soon as, until and once
    2. Lesson 14How is a barcode read?The present and past simple passive
    3. Lesson 15Draw it, then say itDefining relative clauses
  6. Unit 6 Remote and async

    chat, email and time zones: polite requests, future forms, the present perfect continuous

    1. Lesson 16Just say what you needPolite requests and indirect questions
    2. Lesson 17Your 9 a.m. is my noonFuture forms for plans across time zones
    3. Lesson 18Write it downPresent perfect continuous for status updates
  7. Unit 7 Users and clients

    user stories and plain explanations: verb + to or -ing, reported speech, comparisons

    1. Lesson 19As a user, I want…Verb + to or verb + -ing
    2. Lesson 20"The client said it was broken"Reported speech for client calls
    3. Lesson 21Explain it in ten hundred wordsComparisons for plain explanations
  8. Unit 8 Your next job

    resumes and interviews: used to, the past perfect, the second conditional

    1. Lesson 22A resume that shows resultsUsed to for your career path
    2. Lesson 23Tell me about a time when…The past perfect for STAR stories
    3. Lesson 24What would you do if…?The second conditional for interviews

Questions about this lesson

What are stative verbs?
Stative verbs, also called state verbs, describe states, not actions: what you need, know, want, like or understand. Because a state isn't an activity in progress, these verbs usually stay in the simple form, even right now: I need access to the repo. Sorry, I don't know who owns this ticket. The release date depends on the test results.
What are some common stative verbs?
Common stative verbs include need, want, know, understand, mean, depend, belong and like. Others include love, hate and prefer for feelings, believe and remember for thoughts, own for possession, and seem. At work they turn up in blockers and questions: I need the test data. Who does this repo belong to? What does this error mean?
Can state verbs be used in the continuous?
Usually not: state verbs stay simple even right now, so it's I need access to the repo, not I'm needing access. A few also have an action meaning and take -ing in it: I'm thinking about it beside I think it's fine. The chat in Why is it called a scrum?, a B1 English for IT lesson on edio.ai, hides I'm not needing any help among the wrong replies.
What's the difference between state verbs and dynamic verbs?
Dynamic verbs name actions; state verbs name states. Dynamic verbs such as fix, test, build and run work in both tenses: I fix bugs on Fridays. Right now I'm fixing one. State verbs such as need, know and belong keep the simple form: This ticket belongs to the iOS team. A quick test: can it be in progress? Fixing can; knowing can't.
When do you use the present simple and when the present continuous at work?
Use the present simple for how your team always works and the present continuous for what's happening now or this sprint: We plan every other Monday. This sprint I'm building the payouts screen. A temporary change takes -ing too: This week she's working from home. In Why is it called a scrum?, a B1 English for IT lesson on edio.ai, students sort a sprint page's lines into these two groups.
Is it "Today I work on the bug" or "Today I'm working on the bug"?
For a task under way, it's Today I'm working on the bug, because today here means work in progress. Keep the present simple for habits: I usually do the reviews, not Usually I'm doing the reviews. The same logic splits I work in the office (normally) from This week I'm working from home (for now). At a standup, most lines about your own work take -ing: I'm fixing the login bug.
Why is it called Scrum?
Scrum is named after the rugby scrum, where both teams push together to restart the game. In 1986, two professors writing in the Harvard Business Review compared fast product teams to rugby players moving up the field together, and in the early 1990s Jeff Sutherland and Ken Schwaber used the name for their way of building software in small teams. At work the word names the method: We use Scrum, and we work in two-week sprints.
What are the key agile and Scrum words in English?
The core words are sprint, backlog, user story and retrospective. A sprint is a short, fixed period of planned work; the backlog is the ordered list of work still waiting; a user story says what a customer wants to do and why; a retrospective asks what went well and what to change. The verbs matter too: teams estimate tickets, prioritize the backlog, demo new screens and pick up the top ticket.
How do you say what you're working on at a standup?
Use the present continuous for your work in progress: Right now I'm building the payouts screen. For a blocker, a state verb in the simple form: The screen needs real payout data. I don't understand the new payout states yet. Keep habits simple: He usually replies within an hour. A standup update with gaps closes the grammar drills of Why is it called a scrum? on edio.ai, a B1 English for IT lesson.
How do I teach state verbs to B1 adults?
Teach them through real blockers and replies, where learners need them: I need access, I don't know who owns this, It depends on the tests. Contrast each with an action verb in -ing (I'm fixing it), then let learners catch I'm needing or I'm knowing in a chat or a standup. A short list on the board, eight verbs or so, works better at B1 than a long one.
What's good homework for practicing state verbs and the present tenses?
Good homework puts a typical week next to this week: a table with the same verb in both tenses, then a message or a voice update that uses both, with at least one I need…. In the B1 English for IT lesson Why is it called a scrum? on edio.ai, a fill-in table and a Scrum-word anagram check themselves; a welcome message for a new teammate and a recorded voice update go to the teacher.
Are there interactive exercises for state verbs?
Yes: choose-the-form drills and chats catch I'm needing as soon as a learner picks it. This page plays four parts of Why is it called a scrum?, a B1 English for IT lesson on edio.ai, without an account: the mobile team's sprint page, the product owner's welcome call, a drill where students choose the correct form, and a chat with a friend about the new job. The other exercises are locked.

Teach this lesson with your students

No credit card required