There are various levels that have to be communicated:
- coding standards
- source code organization (in which file do I put $x?)
- build system
- testing policies
- documentation policies
- design
- APIs
- schedule
- infrastructure like bug tracker, source control etc.
In the end what's important is that you know what to do, and how to do it. If you don't know it, it can has two reasons: it's a hard problem and needs research, or you're not clear about some conditions, design questions or APIs. In the first case you likely just need to sit down and work on the problem, in the latter you need to ask your boss or cow-orker.
So what needs be communicated is "all you need to know".
There are various books out there that cover software project management. If my meager answer is not enough for you, you might read one of those books (though I can't recommend one in particular; but I'm sure some other monks can).
Perl 6 - links to (nearly) everything that is Perl 6.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.