Excellent comments, Eyes.
Now, I happen to work as a software consultant, so I usually wind up walking into either “active fires” or, more likely, “smoking ruins.”
The project has usually reached and passed its turning burning-point.
Heads have rolled, and the best people have quit.
So, one of the first things that I try to do is to look at the team’s work-flow organization, or lack thereof.
I usually recommend that organizations do retrospectives, although w-i-t-h-o-u-t swallowing the kool-aid of “five-whys.”
Technicians need to see their work as the business does.
But the business(!) also needs to better understand how the teams actually work.
I read a little e-book called Managing the Mechanism ... never seen it on a shelf ... that had a lot of influence on my thinking.
The premise behind this book is that software is a self-directing, autonomous software automaton.
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
