The methodology delivers business functionality in discrete releases prioritized by a steering group. Each release has a detailed 3-4 page plan approved by the steering group. Within each release, data is integrated into the data warehouse and reports are created iteratively with business users. Releases provide value to the business roughly every three months while reporting releases can have a monthly tempo. The steering group can modify the release strategy and provide in-flight guidance without locking the enterprise into large commitments.

1. © Redwing Business Intelligence Ltd 2002-2015 v1.2 Page 1 of 1
Evolutionary Development Methodology®
The Release Spiral . . . in a nutshell.
The overall goal of the methodologyis todeliverdiscrete unitsof business functionalityinorder of
value to the business. These discrete unitsare called Releases.
Releasesare prioritizedbythe SteeringGroup,andare listedinprioritysequence inaplanning
documentcalledthe ReleaseStrategy. Itisownedbythe SteeringGroupandhas an 18-24 month
planninghorizon.
The Release nextinsequence will have amore detailed3or4 page Release Planpresentedtothe
SteeringGroupforapproval. Approval will initiate Releasedelivery.
The progressionof Release deliveryisthe outerspiral of the methodology,andthe rhythmisa
deliveryof achunkof value to the businessroughlyeverythree months. WithineachRelease,two
majoractivities typicallytake place. The firstisbringingonanew data feedintothe data
warehouse,andexpandingthe warehouse toaccommodate the new raw data. The secondis
reportingdevelopmentforinformationdelivery,andthisisdone iterativelyinclose collaboration
withinformationconsumersfromthe business. The rhythmof thisinnerspiral isfaster,withreports
beingcreatedperhapsweekly.
There are alsosuch thingsassub-Releases,orReportingReleases,where anew setof reportingor
analyticsiscreatedbasedonmetricsalreadywithinthe datawarehouse.1
Oftenthistakesplace by
combiningtwoormore existingsetsof data. Shouldthere be staff dedicatedtothispurpose,then
the deliverytempowouldtypicallybe monthly.
It issometimesfeasible toaccelerate progressbyrunningReleasesinparallel. Thisrequiresmore
resources,of course,butvalue can be deliveredfaster. A technical assessmentof feasibilityis
usually required,but ingeneral majorReleasescanalwaysruninparallel withReportingReleases.
Upon completionof aRelease,the SteeringGroupwill re-examine the Release Strategy,andmay
modifythe listasappropriate. Thispermitsexecutive managementthe abilitytoprovide‘in-flight’
steeringtothe overall programme.
The enterprise isneverlocked-intoalarge future commitment,withnooptiontomanage change.
The go/no-godecisionisalwaysavailabletothe SteeringGroup.
1 For a full explanation of business intelligenceterminology, pleasesee the Business IntelligenceJargon Buster