I didn't read the full article, but certain points strike me off the bat. One is that more process control is not always better; it's important to find the right balance. More specifically, it's important for all stakeholders (management, developers, QA, support, and the clients, be they internal or external) to understand and be comfortable with the process (and if possible, participate in its design) in order to avoid needless bureaucracy.
Where I work we have production releases every two weeks. Our process is pretty lean, but we follow it rigorously. Others might complain that it's not rigorous enough, but truthfully I think a lot teams I've encountered or read about have erected rigid processes to make up for the fact that they can't work in this "agile", rapid-development environment. Why not? Hard to say; lack of motivation, lack of imagination especially on the part of the team leaders, who knows.
Not, mind you, that I'm claiming rapid development is inherently better for all applications. If I were developing embedded systems, real-time systems, safety-critical stuff or anything under a strict regulatory regime, things might be different.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||