Home > Archive > Extreme Programming > February 2005 > [newbie]: How to convert an existing project into a XP project?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[newbie]: How to convert an existing project into a XP project?
|
|
| Jeremy 2005-01-12, 3:58 pm |
| Is there some documentations about it?
Thanks in advance
Roberto
| |
| Jeremy 2005-01-12, 3:58 pm |
| I must add: when the old one is very huge and prolix?
Roberto
| |
| John Roth 2005-01-12, 8:57 pm |
|
"Jeremy" <rc.nospam@tiscali.it> wrote in message
news:41e5589e$0$130$5fc30a8@news.tiscali.it...
>I must add: when the old one is very huge and prolix?
This is two different issues: How do you transition
a team to using the XP methodology, and how do
you get a legacy application under test so that you
can apply XP techinques to it.
The answer to the second one is "Working Effectively
With Legacy Code" by Michael Feathers. It's the best
work on unscrewing the inscrutible and getting the
untestable under test around.
"Refactoring" is also a good resource, but you need
WELC first. You can't do a thorough job of refactoring
without being able to test the beast.
The best way of transitioning is to get a coach that
has done step by step transitions before. Failing that,
read "Extreme Programming Expained" Second edition,
"Crystal Clear" and "Lean Software Development," and
feel free to ask questions either here or on the
extreme programming mailing list. It's advisable to hold
regular team meetings, get agreement on the top problems,
and tackle them one at a time.
John Roth
> Roberto
| |
| Jeremy 2005-01-13, 8:58 am |
| Thanks a lot for your suggestions.
I will start reading the Michael Feathers's book. It's a lot of work I have
to do, but now it seems I have an how-to way.
| |
| Robert Atkins 2005-01-30, 3:56 am |
| In article <41e5589e$0$130$5fc30a8@news.tiscali.it>, Jeremy wrote:
> I must add: when the old one is very huge and prolix?
IMHO, the technical challenges are straightforward and the books
reccomended downthread will give you a good start.
The real problem is the associated cultural change necessary to turn the
type of disorganised, dysfunctional team which produces a huge, prolix
project into a lean, mean, XP machine. For that, you might take a look
at "Fearless Change" (http://tinyurl.com/5shmy).
Cheers, Robert.
| |
| Ilja Preuß 2005-01-30, 8:56 am |
| Robert Atkins wrote:
> The real problem is the associated cultural change necessary to turn
> the type of disorganised, dysfunctional team which produces a huge,
> prolix project into a lean, mean, XP machine. For that, you might
> take a look at "Fearless Change" (http://tinyurl.com/5shmy).
I agree wholeheartedly.
There are also three good chapters in "Sams Teach Yourself Extreme
Programming in 24 Hours".
Cheers, Ilja
| |
| Robert Atkins 2005-02-06, 8:56 am |
| In article <41fc9948@news.totallyobjects.com>, Ilja Preuß wrote:
> There are also three good chapters in "Sams Teach Yourself Extreme
> Programming in 24 Hours".
Just three? Talk about damning with faint praise :-).
Cheers, Robert.
| |
| Ilja Preuß 2005-02-06, 8:56 am |
| Robert Atkins wrote:
> In article <41fc9948@news.totallyobjects.com>, Ilja Preuß wrote:
>
> Just three? Talk about damning with faint praise :-).
Three *on this topic*, of course!
I actually found the whole book to be surprisingly good.
Cheers, Ilja
| |
| Ilja Preuß 2005-02-06, 8:56 am |
| Ilja Preuß wrote:
> I actually found the whole book to be surprisingly good.
See http://tinyurl.com/5v97y for a more elaborate review.
Cheers, Ilja
|
|
|
|
|