0 views collected around this technical thread.
This article explores how mathematical thinking—through concrete puzzles, probability paradoxes, and the Fermi estimation method—helps us overcome intuitive traps, make rigorous calculations, and apply logical reasoning to everyday problems and complex estimations.
This article explores the nature of agile estimation, details popular techniques such as Planning Poker, T‑Shirt Sizing, Story Points, Affinity and Wideband Delphi, and provides comprehensive risk‑management strategies and best‑practice recommendations to improve forecasting accuracy and project success.
This article provides a detailed overview of user stories, their three essential elements, writing guidelines, role modeling, collection methods, acceptance testing, and practical application within Scrum, including estimation, prioritization, iteration planning, and the advantages and pitfalls of using user stories in software development.
Software engineers rarely build entire systems from scratch; instead they spend most of their time navigating large codebases, documenting, estimating, handling uncertainty, and collaborating with imperfect teammates, emphasizing business value over elegant code, and learning practical skills that university curricula often overlook.
This article reveals the hidden challenges of software engineering, emphasizing that most developers spend little time writing code and more on maintenance, documentation, dealing with incompetent colleagues, uncertainty, estimations, and meetings, urging newcomers to accept these realities and focus on delivering value.
This article explains why agile teams prefer story points over time for effort estimation, how the Fibonacci sequence (and its modified form) aligns with human perception of differences, the role of planning poker and the Delphi method in reducing bias, and practical steps for establishing baseline stories and estimating story points.
The article recounts how a major bank's R&D center used a card‑playing exercise to demonstrate agile story‑point estimation, detailing the step‑by‑step process, its purpose, and answering common questions about the technique’s applicability, units, and relative‑estimation logic.
This article introduces the most commonly used algorithms in engineering—recommendation, optimization, estimation, and classification—describes their typical application scenarios, and explores various testing methods and evaluation metrics such as offline experiments, user surveys, A/B testing, and performance indicators like accuracy, coverage, and robustness.
The article recounts a Nokia mobile‑software project where a newly appointed agile consultant analyses the company’s Scrum adoption, team structure, user‑story splitting, point‑based estimation, and the exclusion of testing and code‑review effort to improve planning and delivery for a ten‑month, 200‑person product development effort.
This article explains how a team transitions from waterfall to an Agile 101 approach by introducing time‑boxed iterations, applying the INVEST principle for user‑story splitting, using a ranking method for relative estimation, and outlining a practical planning process to improve project predictability.