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: November 4, 20222022-11-04T13:24:57-05:00 2022-11-04T13:24:57-05:00In: Kanban

What are some great ways to convince a team to swarm on stories instead of working on single tickets per member?

  • 0

Hi,

What are some great ways to convince a team to swarm on stories instead of working on single tickets per member?

Thanks

membersstoriesswarmteam
  • 1 1 Answer
  • 45 Views
  • 0 Followers
  • 0
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

    1 Answer

    • Voted
    • Oldest
    • Recent
    1. GuyM
      Best Answer
      GuyM
      2022-11-05T15:20:12-05:00Added an answer on November 5, 2022 at 3:20 pm

      Maybe take two steps back.

      – why do you need to “convince” your team of anything?
      – what is the problem that you, as a team, are trying to solve?

      At a point, you are part of a team; you might have some specialist knowledge and specific accountabilities, but you are not the boss. Servant leadership doesn’t mean trying to force your team in a given direction.

      Scrum, Kanban and Lean ways of working are empirical. We are data-driven, not opinion based. In fact we want to shift the whole organisation away from the “highest-paid-person’s opinion” (HIPPO) model and towards an environment where people are curious, open, and want to experiment.

      And that starts with us. Exhibit the behaviors we want to see in others, is my counsel.

      You have a solution “the team should swarm on tickets”, and yet what we are trying to move towards is the business bringing the team problems to solve, not solutions to be implemented.

      Rather than convince the team of any given agile practice or process, I would suggest

      – surface issue ideally in a data-driven way with your team in the retrospective
      – work with the team to evolve a problem statement
      – take that problem statement into an Ishikawa fishbone analysis with the team
      – get to a revised problem statement from what they think is the biggest root cause
      – brain-storm solutions together, which is where you can add your opinion
      – determine what solution you want to try, as a team
      – develop a hypothesis – what you will measure to determine success or failure
      – do the experiment
      – if the original problem still exists or resurfaces, redo the Ishikawa analysis

      In doing this you give the team agency and autonomy, teach them problem solving techniques and have an opportunity to bring your knowledge to bare as part of the solution, without acting to control or steer them too much.

      Giving a team solutions all the time, or forcing them in a direction you believe to be correct creates a dependency on you. That’s robbing them of an opportunity to grow..

      • 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 or what is the best way for metrics utilization ...

      • 1 Answer
    • Is Kanban Agile?

      • 5 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.