we are gonna fail a second sprint in a row on the same stuff on our uni project, I'm trying scramble something together but there's just so much that isn't properly handled :/
Multiple reasons IMO: too much work put into the sprint (I was pretty vocal about this in the last planning but no one seemed to mind), too much dead weight on the team, bad git branch habbits on the feature developers, some smallish unexpected hickups, and partly just unrealistic expectations from our PO that we mistakenly agreed to (the old "9 women can't deliver a baby in a month" saying fits pretty well into the Scrum fallacy I feel)
yeah, ok, so a lot of it that you can't do anything about it :/
user92578
Yeah, it's frustrating when I can identify the issues pretty well but can't do a whole lot about them, and it really sucks to have to say pretty much the same stuff to our PO on Thursday and I know he doesn't care about testing or software quality in general at all
user92578
Dead weight is a super bad word to use actually, they're just inexperienced, not intentionally bad or anything
Yeah, I guess just repeating what has already been said could help. The sad thing is, the workplace is no different. You can see this as a way to exercise leadership skills.
user92578
That's what everyone is saying to me, but I really don't see these issues at work