Project Division of Release
Another important part of the release plan is how the releases will be divided across the life of the project. Any requirement can be decomposed into a stand-alone user story that can function independently by itself. It often makes sense to have user stories grouped together by feature where related user stories can be batched and addressed more efficiently.
Full features will often complement each other and give more value when completed simultaneously. Developers are the most knowledgeable roles on how features will interact with the rest of the product.
They intuitively know which features are likely to share common functionality enabling them to group requirement together for the most efficient delivery of value to the stakeholders.
By grouping the requests together, stakeholders also receive valuable features earlier in the project.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: