Some people want to take the stance that no work should be done in advance of the sprint. That is clearly untenable. To see why, let’s take that view to its extreme: If we did nothing in advance to understand what we’re building, we’d show up at the planning meeting and say, “Hey, what should we build this sprint? We were working on an eCommerce site yesterday, but I think maybe we should switch to writing a word processor…” The team would literally have nothing written down—no product backlog / user stories / prioritized feature list at all.
Articles on Scrum and Agile Project Management
Scrum teams just look different. From their faded whiteboards to their discarded post-it notes, Scrum teams make their mark just by doing their job. Read one CSPs story of how his team’s space tells the story of their struggles and their triumphs.
Written by Jeff Sutherland, Anton Victorov, and Jack Blount, “Distributed Scrum: Agile Project Management with Outsourced Development Teams” analyzes and recommends new best practices for globally distributed agile teams. Toyota routinely achieves four times the productivity and twelve times the quality of competitors. Can Scrum do the same for globally distributed teams? Two agile companies, SirsiDynix using Scrum, and StarSoft Development Labs using Scrum with some XP engineering practices, achieved comparable performance developing a Java application with over 1,000,000 lines of code. SirsiDynix best practices are similar to those observed on distributed Scrum teams at IDX Systems, radically different than those promoted by PMBOK, and counterintuitive to some practices advocated by the Scrum Alliance.
The article “Bridging Agile and Traditional Development Methods: A Project Management Perspective” by Paul E. McMahon discuss agile project management adoption. This article identifies specific project management conflicts that companies face based on actual project experience, along with strategies employed to resolve these conflicts and reduce related risks. This article will help you understand the risks, issues, and strategies that can help your project and organization succeed.
The article “Agile, Multidisciplinary Teamwork” by Gautam Ghosh presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.
“Estimating With Use Case Points” describes the process to measure the size of an application modeled with UML, using use case points.
An article on Big Visible Charts by Ron Jeffries. You should display important project information not in some formal way, not on the web, not in PowerPoint, but in charts on the wall that no one can miss.