This has been a question that has been hitting me home. Some companies think that because they are small, they don't need to spend any time or energy being organized/structured.
By structured/organized technically I mean:
1. Bug Tracking System - That helps developers kill all bugs, which incites them to create less bugs.
2. Project Management System - can be excel, notepad, anything that helps developers manage their time, and managers set priorities, due dates and manage that.
3. Documentation of Code Logic/Business Rules - So that if lead developer dies, and he/she had it all in their head, how in the world would the next lead developer figure out the code/logic and business rules?
4. Common Coding Styles - Including page naming, commenting, indenting. And have this written to train new members, and remind old.
5. Set, Record and aim for Technical Goals not related to specific projects but affect overall success of developers. IT Architecture, Scalability, Updating ColdFusion, Updating databases, Security, etc. Do you just create more code, or do you also work on improving the environmment, universe the code resides?
Maybe the size of the company can dictate the complexity or depth you go to provide solutions to your main needs, but to not provide them sounds like something that should be on the DailyWTF.com
How do you explain the importance of organization/structure to those who think small companies don't need them?