I agree with your general sentiment, but I don't agree that they should necessarily be able to produce a "project plan". In fact, I'd be worried if they had a highly detailed project plan, because in software development, those are rarely kept to (your comparison to the building industry doesn't hold a lot of water in my opinion. It's possible to do deterministic planning in building - what you plan is pretty damn close to what you build. It's very rarely the case that that's true with software).
Still, I'd hope they had some documentation about their project. A well shaped product backlog would be a good start in my books.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||