Articles

Software development is often fundamentally different than the analogies used to describe it. Accordingly, estimating what software will be done and by when can be an exercise in frustration. Yet, some teams seem to just "get it", making accurate predictions of cost or effort. Other teams struggle with excruciatingly detailed planning meetings or with the results of not estimating at all. Explore estimation for software development from several angles including: empirical planning, time-based estimation, relative comparison, and others. Several effective and proven estimation techniques will be explored, expanding your team’s capabilities beyond hoping for the best.

Share this Article

Decision Rules for the Teams
I often ask a very simple question: “What are the decision rules of your team? “. It’s not rare for this question to make Scrum Mast...Half-Life of commitments
During private PSF (Profession Scrum Foundation) classes my students create a Change Backlog. The idea of this backlog is to codify the things that ne...Our Fight Against Technical Debt
When implementing a new functionality you have two options: blue or red – quick and dirty or smart and clean. If you chose the first option you ...Estimating relative sizes (e.g. story points)
Many companies face issues when trying to estimate in relative sizes instead of absolute numbers (e.g. Story Points vs. man-hours). In Scrum trainings...The Antibiotics of Software Engineering - Agile Testing
Surgery is not a recent invention, it dates back millennia. Even if the procedure was successful, often the patient suffered and usually died of subse...