This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Agile and Other Processes and the fly likes Releases in Programs running multiple Agile Projects Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Releases in Programs running multiple Agile Projects" Watch "Releases in Programs running multiple Agile Projects" New topic

Releases in Programs running multiple Agile Projects

Anadi Misra
Ranch Hand

Joined: Jun 03, 2008
Posts: 69

This topic has got me worked up for some weeks now. Basically, when you are in charge of releases in a distributed program setup (Product Owner for a scrum and Release Manager); which runs multiple projects on AGILE. Whats a good way of managing releases? Specially when some projects are in a more rigorous developmment cycle (where releases to production might not be that often) while others are more in a maintenance phase with minor development (more frequent deliveries).

Looking from an overaall organization perspective; how to synch deliveries from this multiple scrum setup and be able to do what I like to call releases on demand which does not involve the big event cycle that there is today?

Should there be a specialized scrum for releases only( this doesn't sound very aligned with the whole concept of Scrum Team - but has been tempting me off late)? Or should capabilities like System Integrators (SCM etc.) be added to each scrum and keep the Release Manager as a person who plans releases and manages there roll outs to production?

Anadi Mishra.
Ravindra Rawat
Ranch Hand

Joined: Dec 09, 2004
Posts: 34
A possible solution can be to plan a release in term of features from multiple projects in each iteration. Do not allow any project to say that they cannot have a delivery till next 2-3 iterations of the product.

* A scrum of scrums ( i am not a fan of this), i see it as an anti pattern taking you back to days of good ol thick middle management layer. Sooner or later you will have people during pure 'management' and you start the war all over again.
I agree. Here's the link:
subject: Releases in Programs running multiple Agile Projects
Similar Threads
defect tracking column for SW Test & Perf Mag
Agile working remote
Advice for an assignment I am transitioning to Agile.
Refactoring, extreamProgramming, Agile Modelling, SCRUM
Certified Scrum Master Training