StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>My advice is not to be extreme. From my experience, pure agile or pure traditional will not work. Before you use any process, know what it mean to solve.</p> <p>I personally use a variation of <code>Agile RUP</code>. I do some upfront effort such as investigate the actual needs, do high-level design with possible extension. And ask customer to sign-off some major high-level requirements.</p> <p>If you work in small group, detail design or specification may not worth. Of course, if there is some libraries that are shared by many, it will be worth the trouble.</p> <p>Deciding what to invest in up-front depending on its risk (likelihood and effect).</p> <p>Moreover, many SW best practice is really 'best' like version control, automatic testing (to me I only used it way to early detect regression as I do not believe in TDD as driven force of the development). I suggest you read '<a href="http://en.wikipedia.org/wiki/The_Pragmatic_Programmer" rel="noreferrer">Pragmatic Programmer</a>' it presents many of those techines.</p> <p>As to answer you questions:</p> <p>(1). Is it possible to have a development process in a place like this?</p> <p>Yes, but as I say, trailer it to fit your organization.</p> <p>(2). Would it help to have some sort of management? What kind of?</p> <p>Management helps but no control freak. Plan what to do when: integrate, resolve conflict, dead line of some mile stone. And roughly keep them on schedule (I particularly like Scrum's sprint).</p> <p>(3). Is it possible to make quality products with small resources?</p> <p>Definitely as soon as the size of the work, the time to develop and the size of the team is balance. If you definition of Quality is the same with me. To me, Quality means: solve the problem it set out to in an efficient and reliable fashion.</p> <p>(4). How do I convince myself and others that the company which has worked successfully for decades needs to change? What would be essential?</p> <p>Point out the problems. If there are none, why change? If you want to change, you should be able to identify the problem OR potential problems. Point out the problem.</p> <p>Some big one are:</p> <ul> <li><p>Without any process, it is harder for new recruited to blend in as they must learn from observing other how to deal with things.</p></li> <li><p>Without process, it is harder to work in stress.</p></li> <li><p>Without schedule, it is hard to determine the progress.</p></li> <li><p>Without automatic testing, it will takes more time to identify problems and regression.</p></li> <li><p>Without version control, it will be harder to roll-back mistake and separation of work to each team members will be mess.</p></li> </ul> <p>Just my though.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload