Agile Project Management Methods

Comments by date▼

Comments by rating

Rating

Beulah Dianne Suddith, United States

Project Flexibility and Being Agile

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.

Iskandar Hussein Mohamed Hussein, Malaysia

Issues with Rotating Tasks

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.

T. Stahl, Canada

PROs and CONs of Being Agile

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.

Derek Dorzie, Ghana

Agile Project Management Methods

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.

Luis, China

Agile versus Traditional Project Management Methodologies

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.

John Rogers, USA

How Agile Works in Software Development Projects

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.

Rudranath Singh
Project Manager, Trinidad and Tobago

Agile versus Traditional PM Methodologies

@Luis: Definitely agree that both agile and traditional project management methodologies are relevant for projects, depending on the characteristics of a project.
Agile may be most applicable to software development and other design projects.
Traditional is suited to different fields such as construction (Design - Bid - Build).
In general, as the fast changing environment and flexibility need to be catered to, more agile PM methodologies are needed.
Perhaps some examples of the use of agile in other disciples (other than software development) may be instructive.

8Manage
Editor, China

WBS in Agile Projects

There is a misconception out there that if you use an Agile Kanban method to manage your projects, you can’t use Work Breakdown Structure (WBS) and vice versa. In other words, the misconception is that Agile Kanban and WBS can’t work hand-in-hand together.
The argument against WBS by those who practice Agile Kanban is that at the beginning of a project, the scope of the work is not known. They also note that during the project’s lifecycle the requirements often change, the market changes, and the competition will not sit idle but surprises you. So according to Agile practitioners, spending time on WBS at the beginning of the project is useless and a waste of time for any Agile project.

This assumption is totally wrong. Same as Kanban and any other Agile methods, WBS allows you to establish what you need to do currently as a separate project apart from your ultimate goals. If it is important that you begin with end in your mind, meaning you don’t want to totally lose sight of your ultimate goals while you are doing your current project, then WBS allows you to relate your current project with your ultimate goal. There is actually no conflict between Kanban Agile and WBS.

Agile Kanban and WBS each have their weaknesses and using them together benefits projects.
- The biggest complaint about the Agile method is the lack of certainty as to when the project will finish. It is very important that project teams begin with end in their minds.
- The biggest objection to WBS is that only trained project management professionals can use it effectively but projects often involve non-PMP-certified personnel.

Modern project management software such as 8Manage Agile Large Project allow to switch between Kanban view and WBS view dynamically and in real-time.
Kanban Agile is simple, visual and easy-to-use. But when you have a large project of important ultimate goals, using Kanban purely would be hard to begin with end in people’s minds since what they are currently doing in their current activities can be related to their ultimate goals visually in any way.
Many trained project managers use WBS to get a handle on the complex and large projects. People can switch from the Kanban view to the WBS view in real-time if they want to see the big picture. On the other hand, if people want to focus on a number of activities at hands, they can simply use the Kanban view.
Being able to dynamic switching between Kanban Agile and WBS views creates the best project management method to plan, track, and manage complex projects.