How do you think about bundling or 'holding' launches for a regular launch cadence vs releasing when ready?

I'm a big fan of bundling, especially for small/medium (Tier 2/3) launches. You could bundle into a one-off launch, but I've seen more success at just setting a regular c...

Every organization thinks about this differently, and I’ve worked across the spectrum from a single, annual release (Android OS) to continuous release (B2C startup). So ...

I worked at a startup who took pride in the fact that we launched new features with every sprint. It sounded like innovation to talk about how we released X new features ...

I’ve seen both approaches, but it depends on your business, selling motion, and product team culture on which approach is best for your company. I'll share some takeaways...

This is a question that comes up at every company I work with or talk to. As product teams have moved towards continuous delivery, there's a desire to just launch new fea...

I don’t agree with the strategy of “holding” back feature launches for a regular launch cadence. Tech moves fast and you should be constantly shipping. Launch the feature...

I think there are two different thing - and both important. I think releases shouldn't be random (like daily) because your CS and Sales teams, and most importantly, your ...

Bundling launches can drive efficiencies of scale and impact of message. If there is a Tier 1 launch, that is the primary and sole message/launch for that quarter. At oth...

Each organization thinks about this differently, and both approaches have pros and cons. Three things to think about here: market impact, efficiency/scalability, and cust...

I wouldn't disrupt product's release cycle. If they want to push new capabilities and product updates during a 2- week sprint, thats great! You can even inform customers ...

From my experience, there are a couple of primary considerations when deciding whether to bundle multiple features into a single major launch or push them out individuall...