Related Posts
Hi fishes,
Anyone joined coforge recently? Any reviews for the same? Is it worth to join this organisation? They told me they are hiring for Santander bank account but still be having client interview before onboarding to project. Any idea on this account? Is it tough to crack client interview over there? Don't want to face long bench hours like it used to be in Publicis sapient which led to brutal lay off. Kinda sceptical to join as it is giving me Publicis sapient vibes.Coforge Coforge ltd
More Posts
Additional Posts in Consulting
Can you pay for Invisalign with your HSA?
New to Fishbowl?
unlock all discussions on Fishbowl.
If you haven’t groomed enough you’ll have long sprint planning. Schedule backlog grooming 2x per week for an hour minimum until you have a couple of sprints worth of stories to work on. Good user stories take a long time to get perfect.
You could look to SCRUM for guidance: According to SCRUM, sprint planning should be max 8h for a four week sprint. Less for shorter sprints. So if you have 2 week sprints, 5hrs are almost within the recommendation.
In my experience, 2-4hrs should be more than enough for a 2 week sprint.
In my experience, the more mature agile is in your org and team, the quicker the meetings.
Definitely schedule more backlog grooming sessions, as the clarity of the backlog directly impacts the length of the sprint planning meeting.
I currently lead two product dev groups. One is one team that's been doing agile dev for about a year, the other is 3 teams that's been doing agile dev for 5-6 years. For the newer org, we do an hour of backlog grooming per week and our sprint planning meetings take about 90 minutes. For the older, more mature org, we do 30 minutes of grooming per week and out sprint planning takes 60 minutes, despite the planning being for 3 teams worth of work. Both orgs run on 3 week sprints.
I mean it really depends on the scale of what you’re developing, how many devs/teams are involved, the quality of tickets, ability to prioritize etc. I’ve been in week long sprint planning sessions before but it was for an entire company’s product/dev org for all the sprints in a quarter
Many everyday people run a marathon in 5 hours...not a sprint