Agile Project Management Methods

Project Flexibility and Being Agile
Beulah Dianne Suddith
One way to be flexible and agile with projects is to do research mulitple vendors, this provides choice. For example, when procuring vendors for a project, research as many as possible that have the qualities that are being sought after. Doing this provides a choice of vendors that can be used. If something happens that causes one vendor not to be able to fulfill the requirements, we then have other vendors available to choose.
Another way to be flexible is in assignment of tasks. Tasks can be assigned using rotation of tasks. For example, assign tasks to be performed by each team member for a specific amount of time. After that time period is finished, reassign the tasks to different team members. This will allow each team member to contribute to the project and experience different aspects of the project.

Issues with Rotating Tasks
Iskandar Hussein Mohamed Hussein
The ability to rotate tasks has it own pre-requisite: team members that are involved in rotational work should have the same skill sets.
In a working environment where high numbers of resources and similar skill sets are available, it could feasible to implement.
However, in working environment where similar skill sets are limited, rotational task may pose a challenge. That's where vendors can play a big role in closing this gap.

PROs and CONs of Being Agile
T. Stahl
I agree that flexibility and agility are key to project success, but also believe that "traditional" project management methodologies have their place.
In my view, having multiple vendor or rotating tasks is not an "agile" practise, but rather being able to quickly change team focus or direction based on current environmental risks and issues.
The flip-side of being so flexible and agile is that you are changing all the time, and never actually get anything accomplished.
A good agile practise is having clear short-term goals and usable deliverables that provide clear value, then re-assessing goals with your clients and users for the next phase of work.

Agile Project Management Methods
Derek Dorzie
I think that I agree with Stahl. To continuously change with the environment does not represent agility.
Rather, agile projects are those that draw from a strong foresight in the planing process and are thus strategically enabled to withstand changes while meeting the goals of the project and needs of the same changing environment.
An agile project, benefiting from sound plans and forecasts, is able to deliver its value at all stages, while mitigating any contingencies via responsible emergency preparedness plans.

Agile? Where?
Shankar Lakkaraju
I think to implement any agile methodology we as a person (team members also) should be agile first. Agile is more of quick adoptability than a process.

Agile is Much More Than Change Adoption
Vaibhav Behere
@Shankar: I would disagree that agile is more of change adoption than a process. Agile actually enables a team to assess its project deliverables vis-a-vis overall project objectives. Agile enables a quick turnaround as the deliveries are small and more often. It also enables the end user to understand what to expect and participate continually.

Agile versus Traditional Project Management Methodologies
Luis, Manager, China, Member
Both agile project management methodology and traditional project management methodology have their advantages and disadvantages.
If the PM faces a logical user and stable requirements, a traditional project management method may be the best approach.
If the PM faces unstable requirements but the project team has to start anyway, an agile project methodology may be the best choice.
A full criteria list is needed to help PMs to select the right methodology for a new project.

Adapt Project Tools to Facilitate Agile People Change
Lesley Beal
As in any change project, the effected resources need to be prepared, so they can adopt the change. This is more difficult in agile projects as the solution is defined very close to the time it is deployed.
There is a need to adapt the approaches and tools built around traditional project management methodology to reflect the above. But how? Ideas? Suggestions?

How Agile Works in Software Development Projects
John Rogers
In the software domain, the "agile manifesto" provides ground rules for a rapid application design approach.
It is characterized by small teams of 6-8 people, with a team leader. They meet daily to establish the short-term (today) and near-term (this week) development goals for each person.
These teams, sometimes referred to as 'scrums' work in 4 week sprints to develop applications. The project manager coordinates one or more scrum teams to accomplish the major milestones in the project.
Rather than instructing work all the way to the task, 'agile' permits software development with use-cases as guidance and prototyping as a means to an end, all with velocity to completion with minimal documentation as key outcomes.