Please enable JavaScript.

Coggle requires JavaScript to display documents.

CS317 Class: Why Project Fails?, CS3B - MONACILLO GROUP, CS3B - Chavo'…

- - - - Major slowdowns
      - Scope creep
    - - Frequent errors
      - Frequent bugs
      - Higher dependency on others
    - - Rework
      - Integration issues
      - Project delays
  - - - Project delays
      - Rushed work
      - Lower quality deliverables
    - - Workflow bottlenecks
      - Missed milestones
    - - Team confusion
      - Overlooked critical tasks
    - - Vague scope
      - No requirement validation
      - Misinterpretation of problem statement
  - - - Rushed output
      - More defects
      - Missed reviews / testing
    - - Disrupted flow
      - Overlapping tasks
      - Overtime work
    - - Unifnished tasks
      - Bug buildup
  - - - Conflicting inputs
      - Delayed approvals
    - - Overly safe choice
      - Missed oppurtunities
    - - No action taken
      - Momentum loss
  - - - Hidden issues
      - No feedback loop
    - - Stifled innovation
      - Low morale
    - - Reduced participation
      - Higher turnover
- - - - Lack of Version Control
      - Ignoring User Feedback
      - Overengineering
      - Low Scalability & Maintainability
      - Inconsistent Coding Standards
      - outdated Technology Stack
      - Poor Architecture & Design
    - - Inappropriate Theories
      - Unclear Requirements
      - No Clear Success Metrics
      - Misalignment with the Project Goals and Organizational Vision
      - Unrealistic Deadlines
      - Poor Marketing Strategies
    - - Inadequate Testing
      - Poor Quality Assurance
      - Overlooking Edge Cases
      - Neglect of Post-Launch Development
      - No Automated Testing Processes
    - - Financial Constraints
      - Lack of Skilled Personnel
      - Poor Resource Forecasting
      - Insufficient Technical Infrastructure
    - - Security Breach
      - Plagiarism
      - Data Privacy Violations
      - Intellectual Property Theft
      - Misuse of Sensitive Data
      - Lack of Transparency & Accountability
      - Unethical Business Practices
    - - Poor Communication
      - Conflicting Ideas
      - Lack of Feedback Loops
      - Ineffective Leadership
    - - Sudden Regulatory or Policy Changes
      - Infrastructure Disruptions
      - Natural Disasters & Calamities
      - Market Shifts
- - - - Team is confused, work takes too long, and money runs out.
  - - - Misunderstandings, no feedback, and wrong information delay the project.
  - - - Inexperienced and few members with no training cause poor results.
  - - - More features, no limits, and changing ideas keep restarting work.
  - - - No testing, rushed work, and no review leave many bugs.
- - - - Overly optimistic timelines; underestimated setbacks
    - - Poor allocation of people, tools, time, etc.
    - - Cannot adjust when problem arise
    - - Setting goals too high
    - - Choosing unsuitable technologies
  - - - Requirements keep changing mid-project
    - - Product does not meet user needs
    - - Unclear features or acceptance criteria
    - - Product becomes outdated or unnecessary
    - - Confusion about what to build
  - - - Problems not reported early
    - - Team is not equipped for tasks
    - - Loss of interest or commitment
    - - Bugs slip through to production
    - - Misunderstandings and misaligned priorities
- - - - Lack of time
  - - - Unrealistic expectations
- - - - Unrealistic deadlines
  - - - Low motivation
        
        Unwillingness to change or adapt
    - - Timezone problems
        
        Work ethics
- - - - Ideas that only work on paper
      - Misaligned Goals
      - No Market Research
      - Unclear Goals
    - - Poor team fit
      - Weak System Security
      - Underestimating project complexity
      - Misaligned team size
- - - - Weak software architecture
        
        The system’s foundational design is flawed, making it difficult to scale, maintain, or adapt.
      - Ambiguity in requirements
        
        Requirements are vague, open to interpretation, and prone to misunderstanding.
      - Incomplete requirements specification
        
        Key features or constraints are missing, leading to gaps in functionality.
      - Conflict or inconsistent requirements
        
        Different stakeholders request features or rules that contradict one another.
      - Uncontrolled scope creep
        
        New features and changes are added without proper impact assessment, extending timelines and budgets.
      - Insufficient domain analysis
        
        Limited understanding of the business domain results in solutions that don’t fit real-world needs.
      - Poor requirements traceability
        
        The link between requirements, design, implementation, and testing is unclear, making it hard to verify coverage.
      - Lack of requirements validation and verification
        
        Requirements are not checked with stakeholders for correctness or tested for proper implementation.
    - - Unrealistic timelines and budgets
        
        Underestimating time and cost requirements leads to rushed work, quality issues, and missed deadlines.
      - Inadequate risk management
        
        Potential risks are not identified, assessed, or mitigated, allowing preventable problems to escalate.
      - Poor communication among stakeholders
        
        Misunderstandings and misaligned expectations arise due to unclear or infrequent updates.
      - Lack of clear leadership and decision-making
        
        Without strong leadership, the team lacks direction, focus, and accountability.
      - Failure to monitor progress effectively
        
        Progress is not tracked against milestones, delaying the detection of problems.
      - Lack of proper change management process
        
        Requirement changes are implemented without structured evaluation, causing disruption and confusion.
      - Inadequate resource allocation and task prioritization
        
        Key tasks are delayed or under-resourced, reducing efficiency and slowing delivery.