Pinned topic Some say Agile only works for new or greenfield projects and doesn't work for maintenance, what do you think?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Some say Agile only works for new or greenfield projects and doesn't work for maintenance, what do you think?
Updated on 2012-10-31T21:36:15Z at 2012-10-31T21:36:15Z by JimDensmore
ScottWill 2000001RT94 Posts
Re: Some say Agile only works for new or greenfield projects and doesn't work for maintenance, what do you think?2012-02-17T03:20:16ZThis is the accepted answer. This is the accepted answer.My take is that maintenance was actually "Agile before Agile was cool." Customer-reported defects are more or less equivalent to User Stories (your maintenance team knows the "role," the "goal," and the "business value" of a defect -- for example, "Acme Widgets just discovered a Sev1 defect and their system is down -- they need it fixed ASAP because they're losing thousands of dollars an hour in lost sales!"). A maintenance team that's been around for a while already knows its "velocity" (for example, "On average, each of our maintenance engineers can fix 10 customer-reported defects a month"), and the prioritized backlog of work items is pretty much taken care of by the severity of the defects reported. Finally, work tends to accomplished be in small chunks -- fixing a defect rarely rises to the level of implementing some new feature in a product -- instead defects get coded, tested, and doc'd in short order...
Cherifa 270001GAPC30 Posts
Re: Some say Agile only works for new or greenfield projects and doesn't work for maintenance, what do you think?2012-04-02T17:03:27ZThis is the accepted answer. This is the accepted answer.
Scott , all what you said makes sense in terms of some agile practices ( user stories, prioritized product backlog, release planning, releasing frequently, teams know their velocity...) but it is more to that. When you fix defects, you tend to create code which is going to be injected into an existing component/build. The other challenge is when you have more than one team ( usually more than two), each working on a set of defects and all need to release at the same time. I am working recently with a customer who is using RTC for their maintenance project. The challenges this team faces is in terms of adopting continuous integration properly and to avoid production bottleneck , the deployment needs to be orchestrated...So if we have any best practices that we can share with our clients in terms of adopting continuous integration, TDD,refactoring and continuous deployment..this is where I see good value of agile for maintenance projects. BTW, this is Cherifa.. dev works posted my reply under the nickname I had ages ago!!!Updated on 2012-04-02T17:03:27Z at 2012-04-02T17:03:27Z by Cherifa
- ScottWill 2000001RT9
dmgreggs 120000BN7A1 Post
Re: Some say Agile only works for new or greenfield projects and doesn't work for maintenance, what do you think?2012-04-02T18:57:42ZThis is the accepted answer. This is the accepted answer.I believe Agile concepts and Disciplined Agile Delivery (DAD) can be used for both maintenance and "systems" projects. My last customer was using Agile for all IT projects, which included projects to configure SAP, WebEx and data migration. The Agile Value of "Working Software" would be better described as "Working Solution" to cover the various types of projects. The project teams used the Agile Management practices and tailored the Engineering practices by type of project.
ScottWill 2000001RT94 Posts2012-04-10T22:44:16ZThis is the accepted answer. This is the accepted answer.
Hey Cherifa!I would imagine Reedy and some of the other Services folks would be great contacts for how to effectively use RTC in that particular environment -- and I agree that the coordination amongst teams is critical in such a situation. Also, I'll maintain that an Agile approach in that environment will be far more disciplined and effective than a more waterfall-oriented approach.Thanks,Scott
- Cherifa 270001GAPC
Alok Singh 270002T6FF1 Post2012-09-19T14:00:34ZThis is the accepted answer. This is the accepted answer.Agile works for both new and maintenance projects. I my experience, it works best when teams are maintaining as well are pushing out new versions of a product. Some members form different scrum teams will form a maintenance scrum team which will focus on the service packs and patches. Members will rotate between maintenance and new feature development teams, since no one wants to get stuck up in the maintenance work.
Dan Pollitt 270005CRVY4 Posts2012-10-26T13:50:07ZThis is the accepted answer. This is the accepted answer.
A lot of questions around Agile really seem to hinge on what it means to be an Agile team. I think it really boils down to greggsd's last sentence:
- dmgreggs 120000BN7A
The project teams used the Agile Management practices and tailored the Engineering practices by type of project.I thing in general being Agile is an empowerment of the delivery team to own and customise (when identifying a need) their practices and process to create an environment that allows them to deliver high-quality and relevant (at the point of delivery) value to the customer. I don't think this precludes any type of project at all. An Agile team is often qualified as such by the collection of practices they employ (iterative planning/delivery, pair programming, test-driven development) - and these are very often great choices from which to select from the "Practice Toolbox" but (to give an extreme example to make the point) I believe that a conscious decision by the responsible team to employ a waterfall methodology to deliver a given product could be viewed as an Agile decision in certain circumstances...Updated on 2012-10-26T13:50:07Z at 2012-10-26T13:50:07Z by Dan Pollitt
DougStewart 270004ES7410 Posts2012-10-30T21:30:55ZThis is the accepted answer. This is the accepted answer.For your amusement, I'd like to share 2 points of view I've heard in the last two weeks from customers:
- Agile is really only for big/new applications, said the person working on a small team and application
- Agile is really only for small applications, said the person from a large application project
JimDensmore 1200006V9924 Posts2012-10-31T21:31:06ZThis is the accepted answer. This is the accepted answer.
- DougStewart 270004ES74
JimDensmore 1200006V9924 Posts2012-10-31T21:36:15ZThis is the accepted answer. This is the accepted answer.
- ScottWill 2000001RT9