The average Scrum team delivered a 35% improvement in velocity at Yahoo where teams properly coached delivered 300-400% improvements. The best Scrum Master at MySpace peaked at 267% of initial velocity after 12 weeks and averaged 168% increase in velocity over 12 Sprints. Most teams were less successful. The problem addressed in this paper is what to do about the 90% of Scrum teams that never deliver this capability.
In 1993, at Easel Corporation in 1993, we we first applied the Scrum process to software development teams when we built the first object-oriented design and analysis (OOAD) tool that incorporated round-trip engineering. In a Smalltalk development environment, code was autogenerated from a graphic design tool, and any changes to the code from the Smalltalk integrated development environment (IDE) were immediately reflected back into design. Since the product was directed toward enterprise software development, we spent a lot of time analyzing best practices in software development methodologies.
This article aims to bring to the table a consolidated Agile Project Dashboard layout that could be easily maintained and updated by the Product Owner with day-to-day and well-known information provided by the team. He will be able to get stakeholder and management attention and support while providing an updated clear picture on the Project’s status.
When a team begins a project using the Scrum approach, one of the first questions that often arises is, "how long should our sprints be?" After the collective team understands what a sprint is and how Scrum works, several discussions on the topic usually ensue. This paper reviews the purpose of the Scrum timebox, the reason why two weeks has become the industry standard and some considerations for when another timebox may be appropriate for your particular situation.
Scrum is an Agile Project Management Framework. This framework specifically focuses on maximizing Return on Investment (ROI). Scrum, however, does not define how to manage and track costs to evaluate actual ROI against the vision. A reasonable cost measurement that integrates with Scrum would help provide an additional feedback loop. We adapted Earned Value Management (EVM), using values defined in Scrum. The result is called AgileEVM (Agile Earned Value Management) and is a simplified set of earned value calculations.