Archive of Release Planning
-
Concurrent US-India Release Planning Agenda
Posted on July 18, 2011 by Dean Leffingwell in Release PlanningMany of our larger software enterprises (perhaps MOST) do substantial development within the continental United States and also have a significant offshore development presence, most likely in India (or China or both and more). So it is a very common...
Continue reading this entry → -
Agile Release Train Community of Practice
Posted on May 8, 2011 by Dean Leffingwell in Agile Release Train, Enterprise Rollout, Release PlanningAs those of you familiar with Scaling Software Agility, Agile Software Requirements or this blog know, the Agile Release Train is the mechanism I like to recommend whenever an enterprise needs to harness a significant number of agile teams...
Continue reading this entry → -
Resource Flexibility in The Agile Enterprise
Posted on December 2, 2010 by Dean Leffingwell in Enterprise Rollout, Feature Vs Component Teams, Release Planning, Team PracticesI received this interesting email from a colleague (who allowed me to share it) a few days back. “I currently lead a project on how to increase our resource fluidity so that we can effectively assign sufficient manpower to where it matters...
Continue reading this entry → -
Prioritizing Features
Posted on April 8, 2010 by Dean Leffingwell in Agile Requirements, Lean Thinking, Release Planning, UncategorizedIn the last post, I described a system for estimating features that will be in my upcoming book. This post, prioritizing features, is that post's evil twin. Together, it should be provide a reasonable strategy to estimate cost...
Continue reading this entry → -
The Agile Release Train, Strategic Alignment and Product Development Flow
Posted on January 31, 2010 by Dean Leffingwell in Agile Release Train, Agile Requirements, Lean Thinking, Release Planning, Scaled Agile Framework/Big PictureIn this blog, in Scaling Software Agility, and in my forthcoming book on Agile Requirements, I've been writing fairly extensively on the implementation of the Agile Release Train (also see whitepaper derived from the book) as a...
Continue reading this entry → -
Fun with Release Planning
Posted on November 5, 2009 by Dean Leffingwell in Release PlanningEnterprise release planning is my favorite (business!) activity. Put all the right people in a room for a day or two, fuel them with caffeine and sugar. Present the strategy. Convert the strategy to vision and a set of the...
Continue reading this entry → -
More on the Agile Release Train – Internal vs External Releases
Posted on November 16, 2008 by Dean Leffingwell in Agile Release Train, Release Planning, Scaled Agile Framework/Big PictureIn a number of posts, including Enterprise Agility - The Big Picture(5) The Release Revisited I've commented on the desirability of separating Internal Releases (or Potentially Shippable Increments) from External or General Availability Releases. Although not directly represented...
Continue reading this entry → -
Enterprise Agility-Big Picture (5): The Release Revisited
Posted on September 28, 2008 by Dean Leffingwell in Agile Release Train, Release Planning, Scaled Agile Framework/Big PictureIn the post, Enterprise Agility-The Big Picture (5): The Release, we described that seminal, value delivery construct of the Agile Release. (see Big Picture below). But as with all the other oversimplifications in the Big Picture, (which at...
Continue reading this entry → -
Successes in Release Planning: An Agile Enterprise Tipping Point
Posted on July 24, 2008 by Dean Leffingwell in Agile Release Train, Release PlanningIn the "Release Planning" category and series on this blog, I described an enterprise best practice designed to coordinate the efforts of some number of agile teams in order to deliver a larger scale system in a somewhat predictive...
Continue reading this entry → -
Meeting Deadlines: What’s wrong with this Release Plan #2? (AERP8)
Posted on March 25, 2008 by Dean Leffingwell in Agile Release Train, Release PlanningIn my last post, Meeting Deadlines: What's wrong with this Release Plan #1, I noted that the ability to commit to and deliver on near term deadlines is a reasonable and necessary accomplishment of a professional agile team and...
Continue reading this entry →
Add to Google



