Scrum, for one agile methodology, is not at all about replacing people with cheaper people. It's all about getting a tighter feedback loop on smaller chunks of work. It's meant to deal with specification drift, scope drift, and people talking past one another about the customers' needs.
Having two weeks or four weeks to deliver a minimum viable product, then increments of the same for new features to be added, is not something one should ask of a team of plug-in commodities. It takes a team some time to work together to even be able to estimate properly what they can deliver in that amount of time. Once the team is built, it should be left in place as much as possible.
The practice of specifying every little thing up front can be handy if those specifications are done well and won't change. If the customer's needs or which needs take priority over other start to drift, then getting that feedback every few weeks becomes really valuable.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||