{"id":484,"date":"2024-06-21T10:40:25","date_gmt":"2024-06-21T09:40:25","guid":{"rendered":"http:\/\/localhost:8082\/?page_id=484"},"modified":"2024-07-05T13:56:49","modified_gmt":"2024-07-05T12:56:49","slug":"planning-meeting-chaos","status":"publish","type":"page","link":"http:\/\/localhost:8082\/scrum-helpline\/planning-meeting-chaos\/","title":{"rendered":"Planning meeting chaos"},"content":{"rendered":"\n
Dear Scrum Helpline,
We are now into the third hour of our planning meeting and we’re still trying to figure what’s going to be in the next release, having had only a couple of small breaks.
Some are frustrated, some are quiet and seems from investigation that’s partly because they’re used to the mess hence lost interest I think.
The problem is we’ve got a bunch of bugs that one guy is working on as it’s all part of his code changes. But it’s difficult for others to help out because it’s in one specific area, and now they’re trying to decide if others need to work on them as they’re concerned about whether they’ll get done.
They miss the fact that if I’m working on specific code and know the issues, I can fix better than bringing others in (for example).
QA are getting frustrated (and I understand why) because they’re saying this is a bug but – well I don’t know, it’s just turning into a low key argument (well maybe “argument” is too strong).
We had a discussion previously in the retro. We do NOT and will NOT have BA’s but how do we define what the requirements\/acceptance criteria etc
Wait a minute\u2026 oh no, the Agile coach has just given up on this call so will have to continue this discussion another time lol.
At my last job we had minimal of this stuff and we worked on things without major issues – here, not so simple. It really is all over the place.
Is this really agile and does it have to be like this?<\/em><\/p>\n\n\n\n
\n\n\n\n