The Pragmatic Craftsman :: Simplicity from complexity : by Stanley Kubasek ::

Improving Your Process

How to adopt XP? Here’s how, from Extreme Programming Explained.

1. Pick your worst problem.2. Solve it the XP way.3. When it’s no longer your worst problem, repeat.

I think the above is not only for adopting XP, but a good way to solve any development process issue. It is a good way to improve your process.

Here’s how I think you can solve any process issue (a modified version of the above):

  1. Start with your worst problem.
  2. Try to continously solve it. Don’t try to solve anything else; keep working on the individual problem until you see improvement.
  3. Once you made it better, repeat.

Where else can this be applicable? I think this is also a good way to work on your individual problems.

You are not going to fix anything right away, start making small, step-by-step changes and you will get there sooner than you think.

RelatedGood XP Practices, my recent entry

Related Posts

Favorite Quote

Topics

Tags

Archive

Currently Reading

Info

© 2001-2012 Stanley Kubasek About me :: Contact me

Me on Twitter

The key to performance is elegance, not battalions of special cases. — Jon Bentley and Doug McIlroy - 4 days agoThe ability to simplify means to eliminate the unnecessary so that the necessary may speak. — Hans Hoffmann - 9 days agoSo much complexity in software comes from trying to make one thing do two things. — Ryan Singer - 15 days agoGood code is short, simple, and symmetrical - the challenge is figuring out how to get there. — Sean Parent - 17 days agoSimplicity carried to the extreme becomes elegance. — Jon Frankli - 21 days ago

»see more

Recent Entries