Best practices on sprint process

Hi guys, Since every companies has a different agile sprint process I wanted to get your opinions on what are the best practices on the process of sprint. In the past, I was in a team where requirements and tasks are constantly changing during the sprints which made me and other developers hard to complete before the deadlines. What works well and what did not work for your team. Can you share what are your sprint process that works well for your team? Thanks in advance!

LinkedIn I-have-tp Aug 11, 2020

Stick to the original commitments at the beginning of the sprint. If somebody asks you to do something outside your initial commitments say “sure I would love to help you but I already have commitments made to Stakeholder X. If you think I should prioritize (new task) let’s meet with stakeholder X and see if it can be depeioritized”

Apple EjBs11 Aug 11, 2020

Sprint and agile process is shit! It generally takes a new team about 2-3 months to get used to the product flow and return deliverables in timely manner. I am not saying that we should have a process and not hire a agile leader, but dont overdo it.

Cisco hjch71 Aug 11, 2020

Much to the Agile Industrial Complex's chagrin, there isn't a set answer to this question. Keep it to the basics and the empower the team through usage of retrospectives to improve it for their needs. Basics being: definition of "done", start doing estimates and velocity, firm spring forecasts etc. If you find some work can't be planned for, then start setting aside capacity in the sprint for that work. On one team we rotated around the support role. In that spring the support person would be responsible for triaging escaltions or any other work and could be interrupt able while the rest of the team can stay focused on sprint work.