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

Charles P.

0 Visits
0 Followers
0 Questions
  • About
  • Questions
  • Polls
  • Answers
  • Best Answers
  • Groups
  • Questions
  • Polls
  • Answers
  • Best Answers
  • Groups
  1. Asked: May 27, 2022In: Scrum

    Testing generate a lot of bugs and the sprint never ends, what can I do?

    Charles P.
    Charles P.
    Added an answer on June 2, 2022 at 1:57 pm

    There is many points in your question. A couple of ideas on how I would proceed. I would invite team to get focus (if not already in place) so you could at least complete 1 story. Ensure that bugs are handle following the Story priority so fix whatever is broken in your oldest story or higher rank bRead more

    There is many points in your question. A couple of ideas on how I would proceed. I would invite team to get focus (if not already in place) so you could at least complete 1 story. Ensure that bugs are handle following the Story priority so fix whatever is broken in your oldest story or higher rank before moving to other bugs. I would have team inspect the type of bugs if they were avoidable; Are they requirements understanding issue, is there use case not covered tought of before developping, etc. I found that using the “3 Amigos” or Story Kickoff so the BA, Dev, QA sits together to ensure they understand the story before starting it. It help see many angle and think of edge cases that can help during design etc.

    See less
    • 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

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.