Functionality Driven
A functionality driven release strategy focuses on getting certain features into each release. If stakeholders need certain key components quickly, they may prefer this method. Smaller and less important features may be pushed back, and take longer, but the Scrum team will get the most important features into the product and release it to the stakeholders as quickly as possible.
Date Driven
If stakeholders have a preference for having new features delivered regularly in a certain time frame, a date driven release strategy may be a better fit. Customers who have certain schedules in their own environment may need releases to fall into certain time windows. Perhaps this coincides with training periods or some other static time frame. In any case, these stakeholders are willing to have functionality reduced or split up, in order to meet the strict date requirements. Developers are valuable in this strategy as well, since they know how to maximize value in short release periods. If the scrum team keeps to the development pace, features should be finished just before the product is released to stakeholders.
Release planning covers a lot of factors, and developers are important in every part of the process. From creating the release plan to deciding on release strategies, the knowledge of a developer is extremely valuable. Developers know how long tasks should take, how they fit together, and how to maximize value to the stakeholders on a time frame.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: