Related Posts
Desi people, what is your go to soul food dish ?
Who’s excited for Austria this weekend?
Thanks for creating the bowl
Additional Posts in Tech
Looking for a TikTok referral please!
What is the best e-reader, truly? And why.
New to Fishbowl?
unlock all discussions on Fishbowl.
Is the question on the length of sprint (2w v 3w)? We do 2w sprints and it requires discipline and planning. Processes are required to ensure work is planned and risks are taken into account so work rarely bleeds into next sprint (which has a cascade effect on future sprints depending on how far ahead we plan). PMs are actively involved to make sure team is on track, focused, and actively addressing risk. I do think 2w is short; because development is even more comprehensive now from unit, functional tests, DevSecOps. 2w isn’t enough time to see it all.
Tried it for a while, didnt work for us. Switched to Kanban and it much better.
The thing is, you risk burning out your team if you have them commit to too many sprints. Sprints are great, but in moderation.
It depends on the situation. Done correctly it is brilliant. It is rarely done correctly.
Jamming agile sprints into a crappy waterfall enterprise process just adds overhead of overly frequent delivery and demo and slows down the work.
The other common mistake is planning in time units instead of story points and observing velocity as a feedback not assigning a point to hour ratio.
Yes, this is how our engineering teams operate. It works for us. Each team consists of software engineers, QA and a Product Owner (PO). The PO works closely with Product Management and leadership regarding the work the team will embark on. We batch the work and t-shirt size each story using a Kanban and then groom each story- adding details, a more precise point value and what QA is needed. Our work is pulled into 2 week sprints. We made the transition to an Agile philosophy a couple of years ago.
Sprinterfall = bad
Sprints in a true agile system = good
We switched from sprint (fully committed for a specified time window) to a hybrid of sprints and kanban. We demo, prioritize and plan every week, draw a line to set expectations for next week but there’s less emphasis on ‘committed’ - release happens whenever the work is ready to go to production instead of fixed cycle - demos are a combination of working code in production and progress on other items in test environment.