4 ms·
Two thoughts: > "Way of work should be defined at a team level by its people, not by the company." OP delivers that like a surprise, but isn't that the single
by ineptech 3y ago
Two thoughts:
> "Way of work should be defined at a team level by its people, not by the company."
OP delivers that like a surprise, but isn't that the single core defining tenet of Agile? I thought it was.
> Sprint Planning — as simple as it seems, a long session (up to 4 hours)..
My big insight is, painful sprint planning is a result of painful deploys. Once you accomplish real CICD, you can just dispense with sprints and sprint planning entirely.
I'm not sure if that's something most people would agree with or not so I won't belabor it unless someone argues, but I can go on at length about that...
- Scubabear68 3y agoI think one of the biggest mistakes of Scrum is the Sprint concept. Artificially carving work into an X-week, immutable window makes no sense. Plan releases for when feature sets reach the level of maturity users and product folks want them. The Sprint approach leads to half-assed features hiding behind a small army of feature flags. At a minimum, if you can’t get rid of sprints, at least change the default 2 weeks into 3 or 4 weeks. Your meeting burden will go down add you’ll actually have time to deliver working features.
- ineptech 3y agoSprints make/made sense in the world of slow deploy cycles, especially for lengthy manual regression testing. If it takes you three weeks to get from a story being done to a story being in production, deciding which sprint a thing goes in is the difference between customers getting it on day n or day n+21. Once that's not a problem you can kind of forget sprints exist.