BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Estimation Content on InfoQ

  • 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.

  • Estimating on agile projects: what’s the story, what’s the point?

    Ever wondered about how and why we estimate on agile projects? In his first article on InfoQ, David Morris draws on his own experience with since the 90s, and that of several leading agile writers, to explore the topic of agile estimating: what it is, how we typically do it, why we should bother, a brief appraisal of the #NoEstimates debate, and closes with some advice for people new to it all.

  • Your story cards are limiting your agility

    Story cards are a long-established tool for keep track of requests and populating a backlog, but the current common format for storycards can lead to improper focus, improper conclusions, wasted time and wasted opportunity. With a subtle but important change to the way storycards are formatted these issues can be overcome, increasing delivery of real customer value

  • Planning and Controlling Complex Projects

    Planning and budgeting large projects is often based on trying to predict how development will turn out. Stories are estimated by the development team, but the budget for the whole project is independent from those estimates. Especially for complex projects this leads most often to (unwanted) surprises. Insights from beyond budgeting can help to increase flexibility, and focus on business value.

  • Interview with Eduardo Miranda about Estimating and Planning Agile Projects

    Eduardo Miranda, associate professor at the Master of Software Engineering program at Carnegie Mellon University explains the need for planning in agile projects, and describes various planning techniques that can be used with agile. He also looks on the impact of agile on project management offices and on the role of project managers in agile projects.

  • The Prioritization Divide: With Numbers or Without?

    While there are many methods that use stories as a means for prioritizing development, there's a basic divide that asks whether it should be done with numbers or without. There are arguments on both sides, but instead of examining these, people tend to fall into one side naturally. Once there, they can become quickly entrenched in the belief that the other camp is foolishly mistaken.

  • Commitment – Writing a Graphic Novel explaining Real Options

    Building on their work on Real Options, Chris Matts and Olav Maassen are writing a graphic novel to explain the concepts and share their knowledge in the area. They discussed the novel, the process of producing it and the crowdsourcing model of funding with Shane Hastie from InfoQ. A sample chapter is available for InfoQ readers to download.

BT