Practical project management advice for web-based applications

37 Signals is a small company that built web-apps such as Basecamp and Ta-da List. They also published a book called Getting Real--a no-nonsense project-management guide for building web-based applications or websites. If you're tired of messing with Gantt charts and critical path analysis, check out their book. The free online version is here. Some tips you'll learn:

• Build half a product, not a half-ass product. Beware of the "everything but the kitchen sink" approach to web app development. Throw in every decent idea that comes along and you'll just wind up with a half-assed version of your product.
• Let limitations guide you to creative solutions. There's never enough to go around. Not enough time. Not enough money. Not enough people. That's a good thing. Instead of freaking out about these constraints, embrace them. Let them guide you. Constraints drive innovation and force focus. Instead of trying to remove them, use them to your advantage.
• Work from large to small...How often have you realized that the progress you made today wasn't real progress? This happens when you focus on details too early in the process. There's plenty of time to be a perfectionist. Just do it later.
• People often spend too much time up front trying to solve problems they don't even have yet. Don't....Make decisions just in time, when you have access to the real information you need. In the meanwhile, you'll be able to lavish attention on the things that require immediate care.
• Instead of banking on getting everything right upfront, the iterative process lets you continue to make informed decisions as you go along. Plus, you'll get an active app up and running quicker since you're not striving for perfection right out the gate. The result is real feedback and real guidance on what requires your attention.
• Accept that decisions are temporary...Accept that mistakes will happen and realize it's no big deal as long as you can correct them quickly. Execute, build momentum, and move on.
• Use inline help and FAQs so your product doesn't require a manual or training. You don't need a manual to use Yahoo or Google or Amazon. So why can't you build a product that doesn't require a manual?
• Forums and web-based group chat are a great way to let customers ask questions and help one another out. By eliminating the middleman--that's you--you provide an open stream of communication and save yourself time in the process.