BT

InfoQ Homepage Agile Estimation Content on InfoQ

  • On Uncertainty, Prediction, and Planning

    This article describes the software industry’s dismal history with predictions and planning in the face of uncertainty. It details some of the reasons why we fail to learn from our repeated mistakes. It suggests alternative approaches that are based on learning and include the strategy of hypothesis testing (Hypothesis-Driven Development) for deciding which features to deliver.

  • Agile and Late! End-to-End Delivery Metrics to Improve Your Predictability

    Agile teams may need to deliver milestones expected at a certain time, so will need to forecast or risk being accused of being “Agile and late”. There are metrics that relate to the “Logical Six” potential sources of delay which are key to improve forecasting accuracy. The metrics can used to create a Root Cause RAG Progress Report – to share a more accurate forecast and clear mitigations.

  • Author Q&A on the Book Software Estimation Without Guessing

    George Dinwiddie has written a book titled Software Estimation without Guessing: Effective Planning in an Imperfect World. The book discusses different approaches to estimation for software products, the ways they can go wrong and be misused, and when to use them

  • Agile in the Context of a Holistic Approach

    In this article Jon Kern, co-author of the Agile Manifesto, describes a set of critical practices that serve to build up a holistic view of the project, from which all else proceeds. Fail to do a good job at taking the systems view, and your project will likely not go as well as it could. It might even fail.

  • Why Software Estimation Is More Important Now Than Ever

    In a world trending away from traditional waterfall and toward agile development methodologies, it would be understandable to assume that there is no longer a need for software project estimation. However, that assumption would be wrong - estimation is still a very valuable practice, even in organizations that are dependent upon agile development methodologies.

  • Monte Carlo Planning Improves Decision Making

    De la Maza helped a startup IPO by applying Monte Carlo to a planning problem. Learn how Monte Carlo planning provides a rigorous, quantitative account of what the future may bring. It has advantages over standard average case approaches and you can start with a simple Excel spreadsheet.

  • Size Estimation Approaches for Use with Agile Methods

    Reifer’s software sizing survey identifies five commonly used methods for sizing agile projects along with their strengths and weaknesses. Size is used as the basis for measurement and estimation. Stories/story points is the most popular, while function points are used at the project level. Sizing by analogy, proxies, Halstead vocabulary and hybrids are used by others as the situation warrants.

  • Q&A with Vasco Duarte on the #NoEstimates Book

    In the book NoEstimates: How to Measure Project Progress Without Estimating Vasco Duarte explores how NoEstimates can help to manage projects with a focus on value and predictability, report progress quickly and often, and adapt plans constantly based on existing data.

  • Scrum Fundamentals and Advanced Live Lessons : Video Review and Interview

    Tommy Norman’s Scrum Fundamentals and Advanced Live Lessons training videos help beginners to understand the basic agile and Scrum concepts. The videos run more than nine hours, broadly divided between “Scrum Fundamentals” and “Advanced Scrum”. The video sessions use animations to explain the concepts.

  • A Fast Story Point Estimation Process

    Estimating story points can be a tedious process. So tedious in fact that some teams abandon doing story points to help predict their velocity. Instead of letting go of this valid way to predict upcoming work, how about finding a way to make the process of estimating points much faster? Not only faster, but FUN! Yes, story point estimation and fun in the same paragraph!

  • Probabilistic Project Sizing Using Randomized Branch Sampling (RBS)

    Analyzing all the stories in a project requires significant time. How can we estimate the size of a project without prior identification and analysis of every single user story? If you don't want to analyze all user stories in your project in order to estimate its size then Randomized Branch Sampling is an approach you can use for portfolio related decisions and quotations on prospect projects.

  • Quantifying the Impact of Agile Software Development Practices

    Rally Software and Carnegie Mellon's Software Engineering Institute (SEI) are researching the impact of agile software development practices using data from Rally’s Agile Application Lifecycle Management (ALM) platform. InfoQ interviewed Larry Maccherone and Jim McCurley about their collaboration, measurements from the study, conclusions from the analysis and plans for further research.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.