Skip to content
Go Projects
  • Planning
  • Estimates & budget
  • Running it

DE EN

  1. Home
  2. Running it

Running it

Scrum or waterfall, acceptance, change requests, crises.

  • Task cards on a wall with In Progress and Complete sticky notes
    Agile vs Waterfall: How to Choose for Your ProjectAgile vs waterfall for software projects: what Royce wrote in 1970, what Scrum requires, a seven-criteria decision matrix and when hybrid is the honest answer.
  • Deep construction pit with two excavators and a conveyor on a stalled building site
    Why Software Projects Fail: Causes and Early Warning SignsWhy software projects fail, according to McKinsey, Oxford and Standish data, how far to trust the CHAOS numbers, and seven warning signs to check each week.
  • Printed document covered in handwritten corrections, crossings-out and margin notes
    Change Request Process: Steps, Template and Impact AnalysisA change request process for software projects: six steps, a form template, an impact analysis in numbers, a sample contract clause and a small-change rule.
  • Printed document covered in handwritten corrections, crossed-out words and margin notes
    User Acceptance Testing Checklist: Plan, Run, Sign OffA user acceptance testing checklist covering entry and exit criteria, test case template, defect severity levels and a sign-off record that protects both sides.

Go Projects is a guide published by OnlineBuilders LLC, a technology studio for SaaS, AI and data platforms. Related: How we work. How software projects succeed: requirements, estimates, budget, agile or classic planning, risks and the most common reasons projects fail.

Topics: Planning · Estimates & budget · Running it

© 2026 OnlineBuilders LLC · About · Image credits · Legal notice · Privacy