If you look at an Aha! Feature as a container of requirements, e.g. Aha! Feature with 3 requirements, then when you send a in the : Feature—>Issues, Requirements —> Issues; then you end up with 4 issues in GitHub - when you only need 3.
GitHub gets “bloated” because instead of just 3 issues showing up – it will get 4, treating the Aha! as a feature, even though development only needs to work on 3.
We do this because we go from Aha! To GitHub, and then GitHub! To Waffle.io where the Dev’s manage their Kanban board.
The Feature in the above example isn’t really supposed to be worked on as a task – it is just a container.
|Release time frame|