Agile for porting projects
Most often when we, agile enthusiasts, talk about Agile and its applicability, we talk about embracing change. Change in business needs/requirements, change in the team/team members, change in technology, etc.
Definition of porting project: In computer science, porting is the adaptation of a piece of software so that it will function in a different computing environment to that for which it was originally written. http://en.wikipedia.org/wiki/Porting
Googling on “Agile + Porting projects” returns some results out of which only one talks about using Agile practices. The focus though is using Agile testing techniques to guide the port.
What other practices of Agile have been found useful on porting projects? Any thoughts?