comment on

Big Disclaimer: I wrote a book about software development strategies. I like to think I'm correct, but I don't know your team, your company, or your business, so all I can do is ask leading questions.

The problem is that we believe this is not true for software development.

Why is that?

A manager of developers has to answer several questions:

What should we build?
How long will it take to build?
What level of quality does it need?
How much will it cost?
How can the team work effectively?

How do you propose to answer those questions? What parts of the traditional management structure in your company make it difficult to answer those questions correctly?

In reply to Re: Making the Business Case for Developer-Run Development by chromatic
in thread Making the Business Case for Developer-Run Development by etcshadow

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.


Perl: the Markov chain saw
	PerlMonks