This is my impression of Agile Project Management:
Agile Project Management . . . What is it?
Agile programming breaks down an application development project into smaller modularized pieces.
» Each piece is addressed one at a time in a very short time frame (called a sprint). This adds to the application and represents a complete part of the functionality.
» You can deploy the application and expect people to accomplish some amount of work with it, even if the application does not do everything that is intended upon full completion.
For example, if you were creating a word processor, one iteration might be its spellchecker. The spellchecker adds functionality to the word processor, but it affects only one aspect of the application.
Before the developers create the iteration that handles spelling, users can work with the word processor without that feature in place. They simply cannot perform a spell-check on what they write.
Reasons to use Agile Project Management
Businesses need a way to reduce development costs, improve software reliability, decrease time to development and ensure applications actually work with the users, rather than against them. Reducing the number of errors developers make when designing and building applications.
In addition, Agile programming techniques can eliminate that most expensive development cost of all: the failed application. Source: www.CIO.com : ABC: An Introduction to Agile Programming
Agile Project Management : A Scrum Iteration Example
Scrum (the word “Scrum” comes from a terminology in Rugby) is a management-focused agile methodology that is straightforward and can be used in a wide variety of project environments. The Scrum methodology provides the guidance necessary to direct a project in an environment of high variability and where some departments within the customer may have conflicting or competing interests. Of all of the Agile methods, SCRUM appears to be the most popular. The daily communication engages the stakeholders. Scrum requires that the customer not meddle with the team while in sprint and accept that the team may alter sprint goals as required by the difficulty or ease of its tasks. Scrum out-of-the-box is formulated for smaller teams. However, it comes packaged with a scaling strategy, based on a Scrum of Scrums, that is claimed to have been applied to an 800-person project
Product Backlog: team converts the features requested by the customer into a list called the sprint backlog of specific and estimated tasks
Sprint Planning Meeting: The sprint planning meeting is actually two meetings that are timeboxed to four hours each and meant to be completed within the same day. In the first meeting the team assists the customer (called the product owner in Scrum) in selecting the functionality for the upcoming sprint. In the second meeting, the team converts the features requested by the customer into a list called the sprint backlog of specific and estimated tasks
Sprint: Timeboxing is an important feature of the 30-day sprint. This forces tough decisions about functionality and design. The more things different customers request at once, the longer it will take for the project to produce anything of value; meanwhile, there is always a more elegant design solution if the programmers would keep looking. The timeboxed sprint keeps the team from entering into such low-productivity quagmires by forcing the customers to agree on the features the team will produce in the next 30 days and by giving the team a hard deadline to deliver as much of those features as possible.
Daily Scrum: Scrum uses the daily Scrum meeting (short in duration), which facilitates daily communication from the programmers on the project to the otherwise unengaged stakeholders. This meeting ensures that the team communicates frequently, that no one ever wanders far off course, and that customers are made aware of roadblocks in a timely manner.
I hope this was informative in giving you a look at Agile Programming.