There is a simple reason why a feature should be completed within a Program Increment (PI) timebox, even if it seems too fast. It’s a safety net to ensure we deliver in small batches. If you find it challenging to timebox it, then it sounds like the feature is not ready for the team to work on it. To groom the backlog (get it ready), break down the functionality into smaller features. Think through your (too big) feature:
- Is it too broad?
- Are there too many user roles? Can they be broken down?
- Is the feature description concise?
- Can you break it down by data flow, logical system component, or interface?
- Is there a component of it that is blocked by an open issue and can be split off?