If you find yourself implementing a next-generation network inventory application/solution...and someone attempts to convince you to use an agile development approach (e.g. RAD), don't be fooled...it won't work!
Agile development approaches are proven methodologies; however, when it comes to OSS and network inventory...I would strongly encourage a more traditional approach be used.
I have experience with three different carriers who tried to use RAD methodology for their inventory program and they all failed because there is simply too much technical information (e.g. requirement specs, design specs, process specs, etc.) that requires significant time and energy to document, update, share and review with other teams, etc.
In the end, an agile approach caused too much confusion between teams and resulted in 'shortcuts' being made to meet ridiculous agile/RAD timeframes. These shortcuts helped contribute to incomplete system requirements / teams unable to complete design specifications....and in the end ...extended delivery timelines...which not surprisingly resulted in the need for more money from business/funding sponsors (think very BIG change requests).
Stick with the old school development approach when implementing network inventory ...it will increase your chances of being successful.