The scrum meeting should be specific to you and/or your team. It's also a good thing to know what your company is up to. If you silo yourself, you're in for a big surprise when moving to a job that expects you to know how several systems work together. Each to his own I guess
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: How do you normally pay for purchases in stores?
Daily Scrum Meeting
- Thread starter Solarion
- Start date
The scrum meeting should be specific to you and/or your team. It's also a good thing to know what your company is up to. If you silo yourself, you're in for a big surprise when moving to a job that expects you to know how several systems work together. Each to his own I guess
Then you're doing it wrong
(I joke)We do full analysis and project outline beforehand. We don't just jump into a project. In our scrum meetings, when a change and/or obstacle is encountered, something that's not in the scope or a change that is required to push through, the project manager re-looks the outline/analysis, adjusts where necessary (providing the team didn't come up with a solution to the issue), and everyone is issued with the new instructions and kept on the same page. The analysis/project scope changes as and when required.
You never just jump into a scrum meeting with a project that hasn't been defined or planned out properly and just go balls to the wall.
Now this is the thing behind any scrum meeting that blows my fuse. So I received a very urgent item. gOT ONTO IT. Didn't update the #$%^&*() board. In meeting , oh, the urgent item came in, "can only discuss whats on the board" . wHAT A load of bulls***. Simply, if people are in meetings they're not working.
But isn't that why there is a development manager. One who should know who is busy with what? Or can't they do it or what the hells going on with them? And now this scrum crap is putting their work into my hands, not like I"m sitting here doing nothing and have the time to do management and admin as well. $%^&*()_
DukeofHouse
Senior Member
I used to think that the software developers that frequented mybb were mature, lateral thinking, open minded and invested individuals...
This thread correct my naivety.
Forget about scrum, the negativity towards meetings and collaboration in general is astonishing.
This thread correct my naivety.
Forget about scrum, the negativity towards meetings and collaboration in general is astonishing.
crackersa
Honorary Master
well said....
DA-LION-619
Honorary Master
Most of the awesome devs I know don't frequent here often or not even registered.
Then your scrum master/project manager should be fired
+1
If your development manager never interacted with you, and you were someone who couldn't keep a deadline to save his life, or ran into a problem that might affect the deadline (and possibly delay your entire team working on the project) and you don't fully communicate that to everyone in a timely manner, or expect your dev manager to lick your a-hole for constant updates on your work during the day/week, then you shouldn't really work in a team or in dev tbh.
Your dev manager's job is to manage the team to get them focussed on the project that needs to be completed. You also immediately dismiss anyone's involvement as a team by not wanting a quick 10 minute meeting about what needs to be done, what has been done and what is delaying due to issues. I've had many insights in the 10 minutes start of the day into issues I'm struggling with because another developer, not necessarily busy with what I'm busy with, can give insight on how to overcome an issue.
Deal with it.
We call them "stand ups". They are actually very useful. They are project specific. Once a code drop is given to UAT then the UAT team leader also attends. Works well. Yes it can be annoying when you want to get on with something, but you suck it up because you know it's a useful and necessary tool and helps to keep the project on track which is also in your own best interest and YOU ARE PART OF A TEAM. 
Team leaders have more regular meetings between themselves where they discuss projects in general and how projects may impact on each other.
Team leaders have more regular meetings between themselves where they discuss projects in general and how projects may impact on each other.
Mike Hoxbig
Honorary Master
Easier said than done. Your complaints fall on deaf ears, they end up trying to make one of the team members perform the dual role of scrum master, and the whole thing collapses...
crackersa
Honorary Master
well, technically, only certain personalities really work well as a scrum master. just because I am a PM, doesn't mean i will excel as a scrum master, if anything most PM's fail as scrum masters.
and sometimes, you don't need a dedicated scrum master if the team is small enough, or it's a high flying team.
DominionZA
Executive Member
Someone's not coping very well. Wrong career choice?
If your dev manager can't interact with you then he shouldn't be a dev manager. But what is a scrum meeting other than getting updates in a really annoying way...
Team member or not, you get to work at 7:15, start to get going... 9 when you're at speed you get interrrupted with this crap. Really? So why weren't those issues that may affect different dev working on one system picked up earlier, NOT PLANNED?
I like scrum/standup meetings.
If you can't plan your work around a 10 minutes meeting at a set time every day then maybe you need to work on your flexibility.
Maybe get it moved to 10am or whenever you stop for your morning poo or something.. Now that's efficiency, combining 2 tasks into one. Give yourself a gold star!
If you can't plan your work around a 10 minutes meeting at a set time every day then maybe you need to work on your flexibility.
Maybe get it moved to 10am or whenever you stop for your morning poo or something.. Now that's efficiency, combining 2 tasks into one. Give yourself a gold star!