Sometimes customer’s feedback doesn’t come so quickliy, and another deploy has gone without a couple features.
How to handle it right?
Is it the customer ? Does have he to answer quickly? or can he answers during another sprint?
I mean feature is tested and ok, but cannot be deployed because of customer validation missing.
First of all, why customer doesn’t have check to that feature ?
That’s the moment to have a talk with customer to clearify priorities … maybe that features was not so important, or maybe there is something very urgent that he cares of.
Customers or not, your are paying extra time&money handling that “feature not to be” off every deploy until customer will answer.
This is a technical issue customer won’t care at all, and a couple of solutions might be:
-branch per feature 😦
-feature flag (Feature Flags made easy e FeatureToggle)
Honestly, I woukld not add new IF-THEN-ELSE statements (what about anti-if campaign ?) jsut to keep out that code,
branch per feature seems a good idea … but you’ll pay the whole bill when you re-align branch to trunk,
or you add that “feature-sth” pattern … it may solve when it’s a well delimited piece of code or method/function/…
but if that features touched lots lines of code, or web pages? 😦
No best solution so far, except asking customer evaluate those “pending features” quickly. 🙂
Thanks to XP-IT mailing list.
a developer's breadcrumb 