Slackers need not apply

[vetran]

When you put it like that it sounds great

honestly its the skill of the Master just like a great PM unfortunately they are very rare!

[dsc]

On the comment about going round the room so can't miss anyone, that might be the case but some people's updates are the bare minimum to the point of almost being misleading. Sorry to say but our offshore friends tend to be the worst offenders with updates being 'It's OK' day after day or requiring a grilling to get the real detail out.

That's why you need a proper scrum master / team lead, that person should be aware of what's pressing in that particular sprint and what issues are to be fixed. If it's just a regular PM doing it, whatever they get told effectively sticks. That's why I said that company who put out the ad probably has no idea how to run things like this properly.

[northernladuk]

honestly its the skill of the Master just like a great PM unfortunately they are very rare!

Indeed. Most people think they are good PM or BA's until they meet proper one. They are on a different planet. So yeah, a good scrum master is on top and knows what is going on before the update. One just following process is going to accept poor updates.

[d000hg]

You don't need to be great to respond to "It's OK" with "can you tell us which ticket(s) you are working on?" It's fine to have no update but if you are active, I prefer the "what I did yesterday, what I plan to do today, what problems I face" as a minimum - what bit of #123 you did yesterday and if you expect to finish it today, etc.

SM is a simpler role than PM. I quite like the idea some teams use of rotating the SM around the team because SM isn't in charge, just a facilitator.

[vetran]

You don't need to be great to respond to "It's OK" with "can you tell us which ticket(s) you are working on?" It's fine to have no update but if you are active, I prefer the "what I did yesterday, what I plan to do today, what problems I face" as a minimum - what bit of #123 you did yesterday and if you expect to finish it today, etc.

Precisely at a minimum that is what the SM should insist on. if he also uses the reports to see what is on critical path and or is over hours then he/she can offer help for those struggling or swinging the lead.

SM is a simpler role than PM. I quite like the idea some teams use of rotating the SM around the team because SM isn't in charge, just a facilitator.

Interesting idea, though some of life's introverts standing at the front may be uncomfortable for them. My experience is that good PMs make good SMs.

[d000hg]

Interesting idea, though some of life's introverts standing at the front may be uncomfortable for them. My experience is that good PMs make good SMs.

I used to find just doing a stand-up quite stressful when I was much younger, and I'm sure many other devs are similar but it's important everyone is heard. Though I wouldn't say any team should force anyone to take the SM role who isn't happy doing so, I would encourage anyone to try it as long as their team is encouraging. It's good to be able to do stuff like that and it will make you better at your job if you're able to. The moment you move beyond being "just a coder implementing a task" you need to be able to talk to humans to discuss ideas, etc as a developer. A good employer would mentor people who find this hard and would benefit a lot from seeing those people grow because often they have great ideas they are too nervous to share

[JustKeepSwimming]

I think some people don't like stand ups because they aren't natural boasters. When you in a SU with people who constantly claim they are curing cancer it can cause anxiety in those who are doing a good job but paranoid they could be doing more.

We all know people who claim to be absolutely swamped no matter how little work they actually have.

[Fraidycat]

I think some people don't like stand ups because they aren't natural boasters.

What i don't like about standups, is if you didn't do much yesterday, say you were distracted at home. It is hard to be honest and admit that when everyone else says how much work they did. Although there was a contractor i worked with who once admitted in morning scrum that 'I have the builders in so didn't get much done yesterday" and he still billed the client for a full day.

[vetran]

I used to find just doing a stand-up quite stressful when I was much younger, and I'm sure many other devs are similar but it's important everyone is heard. Though I wouldn't say any team should force anyone to take the SM role who isn't happy doing so, I would encourage anyone to try it as long as their team is encouraging. It's good to be able to do stuff like that and it will make you better at your job if you're able to. The moment you move beyond being "just a coder implementing a task" you need to be able to talk to humans to discuss ideas, etc as a developer. A good employer would mentor people who find this hard and would benefit a lot from seeing those people grow because often they have great ideas they are too nervous to share

Yep it requires support to do that, good employers will do that, most won't.

Before agile was a thing we had weekly team meetings and I encouraged everyone to stand up and discuss their accomplishments etc. Even the shy young developer managed it, when he left (when they broke up my team to flatten the worldwide structure) he was one of the best dev's and communicators we had ever had.

[Eirikur]

Here is the ad on Jobserve
https://www.jobserve.com/gb/en/searc...6BB871CC6157E/