Rangers Build Customization Guide … what do you think of the Epics?
In Requirements Management for Ranger Projects … Epics, Team and Personas we mentioned the Rangers requirements management and the concept of Epics, also referred to as Experience. Here is the list of Epics from the Rangers Build Customization Guide project: For those that are squinting at the above image, here is a more readable list: Epic – Practical guidance and tooling to simplify the Team Build 2010 "Build" customizations Epic – Practical guidance to utilize Team Build process templates to automate build and non-build scenarios in Microsoft environments Epic – Practical guidance that allows utilization of Team Build process templates to automate build and non-build scenarios in non-Microsoft environments Epic – Practical guidance to enable simple and flexible flexible deployment of applications and their data stores Epic – Practical guidance for Activities to empower developers and build engineers Epic – Quality hands-on-labs that complement the guidance and effectively guide the user through the features Epic – Visualisation of the guidance using quick reference posters Do these Epics make sense? Do these Epics summarise the killer features of the project?
Go here to read the rest:
Rangers Build Customization Guide … what do you think of the Epics?
