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.
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 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.
Eduardo Miranda from Carnegie Mellon University explains planning in agile projects, planning techniques, and the impact of agile on project management offices and the project manager role. 4
Capers Jones compares the effectiveness of Agile and Scrum with a sample of contemporary software development methods using several standard metrics. 18
In this article the author shares his thoughts and experience gathered while working together with DEV teams, trying to make sense of metrics. He introduces the practice of Metrics-Driven-Development. 9
While stories are commonly used to prioritize development, a basic divide has formed over whether it should be done with numbers or without. 1
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. They discussed the novel and the process with InfoQ.
Our panel of leading experts explores some of the challenges and thought processes that go into making their apps as scalable and performant as possible. 1
Developers and the business use numbers differently, leading to poor communication. Here the "Spirit of Agile" tells a developer the trick: translate non-computational issues into number language. 3
Based on traditional Earned Value Management (EVM) metrics, AgileEVM is adapted for an Agile PM context. It allows Agile and traditional projects to be tracked within a single program. 7
Kenji Hiranabe shows how to track project status using Kanban Boards from three viewpoints (Time, Task, and Team) to enhance self-organization and collaboration. 14