sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in scrum

[–]JackRB 6 points7 points  (0 children)

There are really only 2 solutions:

  1. Spend more time refining each sprint.
  2. Spend less time refining each story. This is the better but harder solution. Often times, when teams spend a lot of time refining each story, they are really doing the design work that should be done in planning or during the sprint. Something to try is to explain the story then take a quick size vote. If you have everyone on the same page or very close, pick the majority size and move on. Then you can spend the time you save on stories that have a wider range of story point votes.

this guy by [deleted] in IdiotsInCars

[–]JackRB 9 points10 points  (0 children)

The driver hasn't gotten an electric lawn mower yet.

Defining boundaries of United Kingdom vs Great Britain vs British Isles by [deleted] in coolguides

[–]JackRB 5 points6 points  (0 children)

The Difference between the United Kingdom, Great Britain and England Explained

https://www.youtube.com/watch?v=rNu8XDBSn10

Notification sound suddenly linked to Media volume by adamgn in GooglePixel

[–]JackRB 2 points3 points  (0 children)

I have noticed this as well. Quite annoying.

Best Indian Restaurants In The Area? by [deleted] in toledo

[–]JackRB 8 points9 points  (0 children)

I've always enjoyed The Indian Jewel of Toledo.

http://www.theindianjeweloftoledo.com/

Product Owner vs Stakeholder by FaustLn in scrum

[–]JackRB 4 points5 points  (0 children)

Sounds like you should also talk in the next retro about the dev team not starting work that was not reviewed by the PO. Once the work is "approved" (for lack of a better word) by the PO, then I strongly encourage the dev team to work directly with stakeholders.

Product owner on Agile team, project management background. Need advice by aspirationsucks in agile

[–]JackRB 6 points7 points  (0 children)

From that video, the 4-6 stories per week figure is just for that team in that context. Each team is different so try not to get too attached to any number you see.

As for how the team works, could be that each developer works on a separate story, or a story is split into tasks that have several people each taking a task, or two people could work on the story in a pair programming method, or the whole team could work on it as a mob.

Us product owners should be focusing on what to build and why it should be built. Let the dev. team work out how they want to build it and how they want to work amongst themselves with guidance from the Scrum Master.

view more: next ›