Ultimately, someone at the company wants to have software that makes them more money or keeps them from worrying about losing money or going to jail (compliance.
Someone at the company thinks they can improve the state of software maintenance/delivery by changing the process. Maybe this is a VP accommodating a micromanaging CEO and doing something so that they can be seen doing something, but it could also be a well-intentioned change, in which case they want either more productivity -- with the theory that more software sooner results in more value -- or more predictability, with the theory that managing teams more closely results in less surprises and delays.
Identifying the root motivation may help propose alternatives, so it may be worth talking 1-1 with someone in leadership to try to understand the motivation. "On team X we're going to move to 1 week sprints. For my contextual awareness to better help implement this change, are we primarily hoping to increase predictability, even if velocity ends up decreasing, or should we focus more on increasing velocity even if work ends up carrying over?"
And they may be willing to go along with smaller secret team-level experiments. Maybe Kanban will result in even better visibility and performance! (And satisfaction)
That said.. just break the tasks down to as small and granular as possible and take on fewer.
You’ve got leadership that doesn’t understand how to deliver software, but you also almost certainly have a transparency problem. You probably can’t do much about the former but you can the latter.
“Once the avalanche has started, the pebbles no longer have a vote”
Remove unnecessary demos or retros. You need the feedback cycle but often 1-3 months is fine, and 2 weeks is only useful for a beginner team.
You do need planning, context, and meetings to discuss the context. We moved these to two days a week where anyone is free to interrupt anyone else and call for a call right now. Nobody expects to be in flow on these days. But as we got better at teamwork, we only needed 0 or 1 days.
We do have 1 week sprints but it's about 90 minutes of sprint related meetings/week on average and that includes stand ups, retros and demos.
Work estimation into the schedule. They're called spikes. Time box them. No commitment is made without the confidence of the spikes. If you don't have confidence by the end of the spike, then something is wrong - the requirements is unclear, code is too opaque, you don't have the data, someone isn't cooperating, etc. These are all very valid outcomes of a spike. Maybe you need to call someone. Maybe you need to refactor.
How much time per week do you have dedicated to sprint meetings? Another issue we have is requirements are always lacking because it’s always fires (and everything is P1).
But if you have frequent P1 fires, then you definitely need the retros quite often. In our case, we always do post mortems for a P1. We dig deep into root causes and this alone is a significant meeting. If it's P1, then, well, it should take everyone's attention. If it's not that major, then it should be some other level. But they shouldn't be happening more than one a quarter or something. It's okay to not be adding features – sometimes reducing fires is significant progress, lol.
Sprint planning meetings for us is just 30 min. We update a doc, it doubles as the retro. Most of the tickets and stuff is already managed by Jira; PM just ticks what we plan to do that sprint. Requirements have already been reviewed before the meeting starts, the meeting is where we work out a plan for it.
Sounds like normal career in development to me.
Remove the 2 most important meetings in a functioning team?
The symptoms of too many meetings is people don't attend them, work during them, complain about not getting things done, etc. If the retros are working, you shouldn't need many of them. If they're not (which sounds like OP's case), then they should be less frequent.
Demos tend to be redundant. Most of the teams I worked with know exactly what the team just built; sometimes the CEO is QA. In the bigger teams, the stakeholders might be juggling too many things to attend anyway.
Or quit, I guess, if the difference between 1 and 2 week sprints is a deal breaker for you.
Usually I find I want improved traceability of the work, and so that means clearly calling out:
planning, defining, scoping and building.
If those on the left are poorly completed that in the right will suffer.
Are there agreed plans or do they change? Are they feasible.
Are sprints hap hazard with story changes, poor quality (and measured against what criteria) or team changes? Are resources sufficient and skilled?
There are many more questions but hopefully you get the idea
Anyone still sticking to Scrum is already behind the times on creating an enjoyable work environment. If they are pushing for shorter sprints, they are doubling down on what makes it bad, not what makes it good.
I'm all for trying to make a place better before giving up, but this is one of the few leadership decisions that are an exception to my ideals. I would just walk out the door, no hesitation.
Ideally KANBAN should be used only for reactive work (bug fixing, ops, support, etc.), but I guess with incompetent management every work is reactive work :(
Give it a try and if it fails, it not on you.
If you're burnt out from meetings and leaving is worth it then leave.
developers and biz folks are basically living in two different time zones, work-wise. Developers need big blocks of uninterrupted time to think hard and get stuff done efficiently. When they’re yanked into meetings or forced to hop between tasks all the time, it kills their groove, and honestly, they end up getting less done. Meanwhile, the biz people—like your management or OWSP types who love to chat—want to see progress in the ticket system. And I get it—developer time ain’t cheap, so they’re stressing about whether the money’s being well spent or if people are just slacking off. But here’s the kicker: sprints themselves aren’t the bad guy. It’s really about the feedback loop—or lack of it—and how it makes everyone feel like they’re not on the same page.
End-of-Day Sync System Instead of those morning standups that mess with developers’ focus right when they’re getting started, we flip it and do a quick check-in at the end of the day. Developers get to work all day without interruptions, and biz folks still get their updates to keep the ticket system humming. Win-win, right? Here’s how it shakes out:
How It Works
Quick End-of-Day Huddle (15-20 mins, max): Everyone jumps in at the end of the workday. Developers say what they got done—did they finish their task, are they still grinding on it, or did they hit a wall? Then they grab a small task for the next day off the Kanban board—something they can knock out in 2-4 hours. Keeps it doable, no stress.
Biz Folks Do Their Thing All Day: While developers are heads-down coding, the management crew has the whole day to mess with the ticket system, shuffle priorities, and prep for the huddle. No more last-minute panic in the morning—they’ve got time to think it over and bring solid updates.
Tasks That Fit the Day: Developers pick their next task at the end of the day, so they can sleep on it and hit the ground running tomorrow. Since the tasks are small, there’s no pressure to pull all-nighters or play hero. Everyone clocks out on time—no burnout, no unpaid OT.
Keeping Biz in the Loop: This setup gives biz people daily visibility— they see what’s done, what’s next, and if anything’s stuck. It’s not about hovering over developers’ shoulders; it’s just enough to keep them in the know without breaking anyone’s focus. Plus, they can tweak priorities for the next day if stuff shifts.
Why It Beats the Sprint Chaos
Look, sprints aren’t evil—they’re just a way to chunk up work. But when you squash all the planning, reviews, and standups into a tight one-week sprint, it’s like you’re spending half your time talking instead of doing. This system keeps the structure but cuts the fat. That end-of-day sync replaces a bunch of those meetings, so developers can actually breathe and work, while biz folks still get their progress fix.
And let’s talk about that “slacking” vibe for a sec. When there’s no clear daily update, it’s easy for management to wonder what’s going on—especially since developer time is so pricey. But with this, everyone sees small wins every day. If someone’s not pulling their weight, it shows up fast—no blame game, just facts. Plus, developers get better at guessing how long stuff takes, since they’re sizing tasks daily and getting instant feedback. Oh, and the biz people? They love to talk—OWSP types especially, right? This gives them their stage at the end of the day without dragging developers into endless chats during prime coding hours. They get their ticket system updates, they feel in control, and developers don’t have to fake-smile through it all morning.
The Bottom Line Developers get their space to think and work efficiently, biz folks get their daily dose of progress without freaking out about costs, and nobody’s burning out. It’s all about respecting those two timelines—letting developers dig in deep and keeping management happy with a steady flow of info.
