Quote:
Originally Posted by jmakin
separate project called "backlog" and i'm going to try to get either my boss or some of the other devs prioritize them all in the next 2 weeks.
I think full backlog grooming/prioritization is a big waste of time. I'd say always focus on the short/medium term stuff and don't worry about the rest. About every 18 months I use to delete 2/3 of my team's backlog w/o thinking about it at all.
Quote:
Originally Posted by OmgGlutten!
Daily meetings are overboard. Think weekly is ideal. You should be communicating over slack anyways during the week.
Quote:
Originally Posted by RustyBrooks
I think daily meetings are fine but they should literally be 2 minutes/person and if they're more than 10 minutes your team is probably too big.
Quote:
Originally Posted by Grue
^^ I'd say 20 but yeah
Daily meetings are great and super useful. But, obviously have to be run well. My average time for a 8 person team was still under 10 minutes. Just a few rules:
1. You start on-time with (almost) no exceptions. It's a daily meeting, if someone misses or is late occasionally its not a big deal.
2. You don't talk about a single issue for more than 15-30 seconds. You can save these things for the end (when people are free to leave) or just write down the topic + the people and let people figure out when to talk. Or whatever. It doesn't matter except getting through scrum quickly.
3. Someone runs it. There are lots of formats for scrum, but one person needs to drive it and move through **** quickly. Cutting off discussion. Etc.
You don't need to be an ******* about any of these either. Tell people up front what the deal is and that its just so the meeting stays useful and not a waste of everyones time.
Quote:
Originally Posted by jmakin
I told them each sprint the goal should be 100% to try to merge to the master branch and they agreed and i’m gonna add the merge mess stuff to the backlog after i speak to my boss about it, but there’s so many other things that seem like they need to be dealt with.
Merging to master probably shouldn't be a sprint goal as much as a task/story goal. The task/story isn't done until the code is merged. This obviously depends on your build/release process.