Timeline for What is the best way to manage features decomposition in scrum?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2019 at 9:53 | vote | accept | nourdine | ||
| Apr 28, 2019 at 8:26 | comment | added | Barnaby Golden | One technique that teams used is called 'feature toggles'. The team releases features but does not necessarily make them visible in the application. Only when they have the set of features they want in a release ready do they change the feature toggle to make them all visible to the end users. | |
| Apr 26, 2019 at 13:37 | comment | added | Bart van Ingen Schenau | @nourdine: It is perfectly possible that an organization decides to deploy the system before the "lost credentials" story is implemented. They just have to accept a higher load on the helpdesk to support the users that lost their password. | |
| Apr 26, 2019 at 12:55 | comment | added | nourdine | Or at the very least use the superset information as a reminder of the fact that those stories MUST be deployed together. | |
| Apr 26, 2019 at 12:52 | comment | added | nourdine | I agree, although I am a novice ;) I still have a doubt though. In the example I provided, it is clear that the single user stories cannot be deliverable independently, although they are somehow independent stories. Somehow I would feel obliged to make them belong to the same set of requirements in order to be in the position to understand when they become deployable. What do you think about that? | |
| Apr 26, 2019 at 11:05 | history | answered | Barnaby Golden | CC BY-SA 4.0 |