16.08.2013 Views

Sky X Technology.pdf - DSpace at CUSAT - Cochin University of ...

Sky X Technology.pdf - DSpace at CUSAT - Cochin University of ...

Sky X Technology.pdf - DSpace at CUSAT - Cochin University of ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

EXTREME PROGRAMMING<br />

ownership, so th<strong>at</strong> everyone can (and does) work on all parts <strong>of</strong> the<br />

system from time to time. This is communic<strong>at</strong>ion <strong>of</strong> design.<br />

Refactoring Communic<strong>at</strong>es Design: An essential aspect <strong>of</strong> XP is<br />

refactoring. Martin Fowler's book Refactoring is subtitled Improving the<br />

design <strong>of</strong> existing code. Refactoring is a process whereby the<br />

programmers (in pairs, <strong>of</strong> course) examine and consider whether the code<br />

is reflecting the design in their heads, and consider wh<strong>at</strong> the code is<br />

saying about wh<strong>at</strong> the design should be. Then they improve the code to<br />

improve the design. This is design, and communic<strong>at</strong>ion <strong>of</strong> design.<br />

N<strong>at</strong>ural Communic<strong>at</strong>ion <strong>of</strong> Design: Within the XP team, the practices<br />

bring about a high level <strong>of</strong> common understanding <strong>of</strong> the design. Using<br />

the n<strong>at</strong>ural willingness <strong>of</strong> programmers to talk about wh<strong>at</strong> they are doing<br />

and how cool it is, and using pair programming, XP teams spread wh<strong>at</strong><br />

needs to be known without the need for much formality.<br />

Communic<strong>at</strong>ing St<strong>at</strong>us: Some aspects <strong>of</strong> your st<strong>at</strong>us certainly need to be<br />

communic<strong>at</strong>ed externally to the project team. These communic<strong>at</strong>ions will<br />

<strong>of</strong>ten -- but not always -- lead to documents.<br />

Standup Meeting: XP recommends a daily "standup" meeting, where the<br />

team stands in a circle and quickly raises issues th<strong>at</strong> people need to<br />

understand. This will include design issues and the like, but the main<br />

thing is a quick review <strong>of</strong> st<strong>at</strong>us, requests for help, problems encountered,<br />

and discoveries made. The standup meeting makes sure th<strong>at</strong> all the<br />

<strong>at</strong>tendees know about everything th<strong>at</strong>'s going on. N<strong>at</strong>urally, customers<br />

and managers are invited, and should <strong>at</strong>tend.<br />

Big Visible Chart: The important st<strong>at</strong>us inform<strong>at</strong>ion th<strong>at</strong> needs to be<br />

fresh in people's minds all the time should be represented in Big Visible<br />

Chart. Here are some examples <strong>of</strong> useful charts:<br />

DIVISION OF COMPUTER SCIENCE ENGINEERING,SOE <strong>CUSAT</strong> 25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!