I'm not much into the Agile & XP type of things - pair programming has a lot of value, but I don't do it much. The Stories (sort of like a Use Case?) seems pretty good - especially the testable part - very nice. Leads you into TDD development. Again, I don't really do TDD but I probably should - except when porting complex Cobol code with a small amount of time to do it.
I've been chatting with RC about the RT team and their approach to porting their application. They seem to be treating this port as 'new development' and are looking for an 'owner' who can help them develop stories that eventually become code.
The main problem I see is the legacy code is the 'owner'. So we need people to 'mine' the legacy code in order to develop the 'stories'. I'm wondering if the RT team is doing this? I doubt it. They appear to want to talk to people and develop stories this way. The problem is, no one person knows the app well enough. There are way too many one-off's.
From what I've heard and seen, the rest of the process doesn't seem bad - pair programming, testable stories, war room, etc. I wish they were using Fitness for real - I'd like to see that - seems like it would be difficult.
So what do the 2 people who read this think - I'm way off, dead on, somewhere in between?