What I do is think of the project as if I was not the only one working on it. Strip down the application down to several individual pieces, each one performing a single function, then make each one of those a module.
Then, create a standard way of communicating between modules (inputs/outputs). Most important: document all this
Now I am ready to start the actual coding. Start with the basics, the very core functionality of the application, and work from there. If you're lucky and you're given other people to help you, you just hand them the documentation you wrote, and have them write some of the little pieces/functionalities you specified. Those pieces will automatically "talk" to yours, since you have created your standard I/Os.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.