From: Robby Russell <ro...@planetargon.com>
Date: Sun, 17 Jun 2007 23:26:25 -0700
Local: Mon, Jun 18 2007 2:26 am
Subject: Re: [rails-business] Change requests
On Jun 14, 2007, at 10:12 PM, Nick Coyne wrote: > So one of the requirements in our Fortune 500 proposal, is a detailed > Working with Agile and Rails, change management isn't something we series of discussions about why something needs to be changed. How does it affect the rest of the existing application and where does it fit into the road map. We often say no to some change requests because they aren't supported with rationale for them, which our process requires for any features to exist. This is our way of working with our client to avoid the, "wouldn't it be cool if...?" requests and keep the system focused on it's primary objectives. When changes are necessary, they become new deliverables in an upcoming iteration. If the change impacts other areas of the application, there should be Anyhow, that's how we currently handle it at PA. Cheers, Robby -- PLANET ARGON, LLC www.planetargon.com +1 503 445 2457 You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||