Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
If you work on the sale task more then 2 days so you should split it into sub tasks more specified.
-
2erXre525047y@projektaquarius I think the your team is doing something wrong in terms of task breakdown (as @ProTooCool also have mentioned). If your tasks have a maximum planned duration of one work day, then it should either be obvious that you have a blocker in your task when it takes you longer to work on that, or all goes good and you are in plan. In your position I would suggest a better task breakdown in the beginning of a sprint then.
Alternatives like Kanban will fail on the same parts of the process if not done well (that's what is happening in my team right now). So it is crucial to have a better view on the current work load. -
C0D4681387ySounds like my teams but we try to follow Kanban.
Let’s go around the circle..
Ok so everyone is doing the same thing as yesterday.
20 minutes of my life missing. -
One team I was on would go through the in-progress tickets on the board, rather than through the team members.
It helped clear up any tickets that had been stuck in limbo, and kept the updates brief. Only problem is that it doesn't work so well if there's loads of tickets in your sprint.
Scrum is terrible. Is there another agile technique that isn't as bad? Like maybe one that will let us do our "scrum" once a week for like an hour? My current project really doesn't lend itself to once a day scrums. Literally my scrum input is "I worked on what I have been working on, and I'm gonna work on it more today. Impediments are literally the same as they always are because my life is no longer my own."
rant