Blog software
Four methods for software effort estimation
Understanding the size and effort of a software project early on is a difficult problem. Several different methods exist, but no method is perfect. In this article we present an overview of the four methods most mentioned in literature: 1) expert opinion-based, 2) top-down estimation, 3) bottom-up estimation and 4) estimation using a parametric or algorithmic model.
Joost Schalken-Pinkster
Getting non-functional requirements right
Getting non-functional requirements right early on is an important success factor for successful projects. This is why, in the course on software project management, one of the practical assignments focused exactly on this topic. In this article we summarize the most important steps: discovering requirements, making them precise and making them flexible .
Joost Schalken-Pinkster
Why having a vision is key in software project management
From March to May 2016, we are teaching the course Software Project Management at the Free University of Amsterdam. In eight weeks, students learn the fundamentals of project management and are creating their own project plan for a software project of their choice. In the course we devote the first week on the project vision….
Sieuwert van Otterloo
Code inflation – why expanding software is a problem
Code inflation is a major problem in software development: software in use tends to grow until it becomes unmaintainable. Read here how you can recognize and prevent software inflation.
Sieuwert van Otterloo
Pros and Cons of Backfiring function points
For estimating the size of IT systems, Backfiring is a faster, cheaper but less accurate method than traditional function point analysis. Backfiring is a useful method for estimating existing systems but less suitable for new software development.
Sieuwert van Otterloo