An effective software measurement program is a long-term investment, not a quick fix. Here are 10 steps to ensure your organization’s metrics deliver a positive return on that investment, from more accurate cost and schedule estimation, to streamlined processes and better insights into current and future commitments.
Bad project estimates cause costly delays, scope creep and inefficient resource allocation across programs and portfolios. Here are 10 ways to generate more accurate estimates throughout your organization, starting with a multi-phased approach and including top-down and bottom-up methods.
In the quest of software excellence, IT organizations try various approaches across different phases of an application's lifecycle. However, two areas that are often neglected are requirements management and testing.
Securing buy-in from a lone stakeholder group can be difficult enough, but when Pacific Northwest National Laboratory (PNNL) (Richland, Washington, USA), launched a project, which was a 2012 PMI Project of the Year finalist, to move its facilities, it had to engage three high-profile government stakeholders and its own staff of scientists. This article discusses how the company moved a laboratory without disrupting its cutting-edge work for some high-profile government agencies.
Does your team spend significant time estimating stories with story points? Or, does your team try to manage its estimates with support or other interruptions? Velocity via story point estimation works in very few teams. Instead of story points, consider these other alternatives for your agile estimates.