Sign Up

Captcha Click on image to update the captcha.

Have an account? Sign In Now

Sign In

Captcha Click on image to update the captcha.

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Captcha Click on image to update the captcha.

Have an account? Sign In Now

Sorry, you do not have permission to ask a question, You must login to ask a question.

Captcha Click on image to update the captcha.

Forgot Password?

Need An Account, Sign Up Here

Sorry, you do not have permission to add post.

Captcha Click on image to update the captcha.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

Ask Agile

Ask Agile Logo Ask Agile Logo

Ask Agile Navigation

  • Home
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Community Help
    • Kanban
    • Scrum
    • Scaled Scrum
    • Liberating Structures
    • Culture
    • Small Talk
    • Team Dynamics
    • Job Opportunities
    • Self-Promotions, Selling Services, Tool Promotions
  • Home
  • Blog
  • Contact Us

Ask Agile Latest Questions

Anonymous
  • 0
Anonymous
Asked: September 7, 20222022-09-07T11:47:00-05:00 2022-09-07T11:47:00-05:00In: Scrum

Is there an industry standard velocity for a certain team size?

  • 0

Hello Scrum Masters

I came across a new information about team velocity recently during an interview which I never knew.

The interviewer asked me my team size and its velocity. When I answered, I was told that, it was too low. She said, “There is an industry standard velocity for a certain team size. For example, for a team of seven members, the velocity should be minimum 55”.

Is this correct?

industry standardteam sizevelocity
  • 2 2 Answers
  • 111 Views
  • 0 Followers
  • 1
Share
  • Facebook

    You must login to add an answer.

    Captcha Click on image to update the captcha.

    Forgot Password?

    Need An Account, Sign Up Here

    2 Answers

    • Voted
    • Oldest
    • Recent
    1. AhmedRida
      AhmedRida
      2022-09-07T13:01:05-05:00Added an answer on September 7, 2022 at 1:01 pm

      Velocity is an indication of the average amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Development Team for use within the Scrum Team.

      There is no such thing as a Good Velocity or a Bad Velocity.

      Remember, it is based on relative estimations.

      • 1
      • Share
        Share
        • Share on Facebook
        • Share on Twitter
        • Share on LinkedIn
        • Share on WhatsApp
    2. GuyM
      GuyM
      2022-09-08T01:55:33-05:00Added an answer on September 8, 2022 at 1:55 am

      Industry standard? Nope.

      SAFe has an idea that you can start with roughly “a point equals a day” as an initial guess when you have no data, and you have about 8 days for work in a 10 day sprint. That would give you 56 points for a team of 7.

      But that’s just for an initial guess.

      The “no estimates” crowd do it a bit the same’ split the work down to stories that take a person about a day, so you’d get to a similar number maybe?

      Sounds like they have half-understood some stuff and have no real idea about how and why a team uses planning poker or estimation.

      A good counter interview question is “how much autonomy do teams have?” …

      • 1
      • Share
        Share
        • Share on Facebook
        • Share on Twitter
        • Share on LinkedIn
        • Share on WhatsApp

    Sidebar

    Ask A Question

    Stats

    • Questions 145
    • Answers 77
    • Best Answers 3
    • Users 0

    Top Members

    • Popular
    • Answers
    • Danny Vallee

      Is Kanban Agile?

      • 5 Answers
    • Anonymous

      What is one thing you wish you could know when ...

      • 2 Answers
    • Anonymous

      Testing generate a lot of bugs and the sprint never ...

      • 2 Answers
    • GuyM
      GuyM added an answer "The product backlog items are too big for one sprint"… March 5, 2023 at 12:45 am
    • GuyM
      GuyM added an answer I'd suggest two things. - the surface issue is seldom… March 5, 2023 at 12:36 am
    • Danny Vallee
      Danny Vallee added an answer Thanks GuyM! January 31, 2023 at 9:38 am

    Related Questions

    • How can we use agile practices to improve the diversity ...

      • 0 Answers
    • What are the most common mistakes that teams make when ...

      • 0 Answers
    • How to foster collaboration and trust in agile teams?

      • 0 Answers
    • How to deal with changing requirements in agile projects?

      • 0 Answers
    • How to Manage Scope Creep in an Agile Project

      • 0 Answers

    Trending Tags

    agile (6) book (4) metrics (4) po (5) scrum (10) scrum master (14) sprint (4) story (5) story points (4) team (9)

    Explore

    • Community Help
      • Kanban
      • Scrum
      • Scaled Scrum
      • Liberating Structures
      • Culture
      • Small Talk
      • Team Dynamics
      • Job Opportunities
      • Self-Promotions, Selling Services, Tool Promotions

    Footer

    About Us

    • Blog
    • Contact Us

    Help

    • Knowledge Base - FAQs

    Legal Stuff

    • Privacy Policy
    • Terms of Service

    © 2023 GaliléSolutions.com. All Rights Reserved
    Crafted with Love by Agile Lovers at GaliléSolutions.com.