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.
Articles on Scrum and Agile Project Management
“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.
The article “Managing the Pipeline” by Mary Poppendieck discuss the project planning and usage of resources. Exhorting workers to estimate more carefully and project mangers to be more diligent in meeting deadlines is not going to remove variation from projects. We need to change the rules of the game!
The article “<a href=”http://www.mountaingoatsoftware.com/system/article/file/12/UpsideOfDownsizing.pdf”>The Upside of Downsizing</a>” describes how a project was successfully downsized from 100 to 12 developers. To make such a dramatic adjustment the development process was switched to Scrum and user stories.
People who have experienced good stand-ups will generally know what can be done when things aren’t working well. This capability is obviously less likely for people with limited experience to reflect on. “It’s Not Just Standing Up: Patterns of Daily Stand-up Meetings” is an attempt to partly compensate for inexperience by describing the benefits and consequences of common practices for daily stand-ups. These patterns of stand-ups are intended to help direct the experimentation and adjustment of new practitioners as well as provide points of reflection to experienced practitioners.
The article “Adaptive Project Management Using Scrum” by Craig Murphy provides a basic overview of Scrum.