Common project problems
This document outlines key problems encountered in software development projects, discussed during the Twin Cities CFUG meeting on July 10, 2002. Major issues include ineffective communication between clients and teams, scope creep due to flexible structures, and challenges related to bad code and undocumented processes. Additionally, it highlights the pitfalls of poor database design, lack of reusability, and inadequate standards that hinder maintenance and cause confusion between bugs and enhancements. Strategies for improving project outcomes are suggested.
Common project problems
E N D
Presentation Transcript
Common project problems From Twin Cities CFUG meeting7/10/02
Problems 1 • Communication – client and team • Scope creep • flexible structure to add features • Someone else’s code (or my old code!) • Bad code – logic flow, database issue, hard to read, bad variable and file name
Problems 2 • Undocumented code • Bad database design • Lack of separation of design and code • Lack of structures and common objects • Change things in one place • Lack reusability • Lack of standards – every one else can’t maintain
Problems 3 • Bugs found by client, hard to find • Is it a bug or an enhancement • Relying on memory or poor spec
