Now, if deliverables were to start slipping, and I saw a general lack of responsiveness and a downgrade in quality, I would react
with a more stringent set of requirements, however, until that time comes (which I hope is never, we have worked hard to put
together a strong team, and a good atmosphere,) I refuse to bend on this.
This being the case, stand firm and make them give you good
reasons why you need to change anything. It sounds as
though everything in your department is working perfectly well
so your critics are the ones who need to prove their case,
not you. Keep pointing out that you are meeting all your
milestones and that all your numbers add up. Wild guess:
Are any of the execs who are trying to manage your
group for you having problems in their own departments?
-
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.
|