Project Management Central

Please login or join to subscribe to this thread

Topics: Agile
What exactly is Agile?
Excuse the naivety in advance, a new PMP here...
I recently received my PMP certification (December 2017). In my study for the certification, in which I used Rita's 8th edition book, there wasn't much mention of Agile methodologies. Now, the PMBOK 6th edition comes out with Agile and I have been too afraid to ask what it is all about. Can anyone dumb it down for me?
Sort By:

Agile is an adaptive approach to a project.

As I am studying for the CAPM - this is starting to be considered and described as a keep in mind sort of thing.

Each knowledge area I can assume will have an agile approach consideration to think about which can affect how the project is coordinated.

As I study scope, it describes an agile iron triangle to be reversed. So here, the cost and time will be fixated and your scope constraints will be flexible. Agile methods focus on sprints and defining/adjusting the scope as the work gets done vs. defining the scope and setting it in stone from the beginning.

Experts correct me if any of my info is wrong.

Agile is a set of principles that embrace the fact that in many cases (including most software development) it is more effective to get continuous feedback from the customer during the development of the product than to try to exhaustively document the requirements up front. (Similar to rolling wave planning, but taken to the next level.) You still have to start with a rough idea of where you are going, but you seek feedback and make course corrections all along the way. Agile embraces, welcomes, and encourages change.

The Agile Manifesto and 12 Principles are the foundation of many Agile methodologies, such as Scrum.

The Agile Manifesto for Software Development is:

"We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more."

The 12 Principles of the Manifesto are:

"Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Business people and developers must work
together daily throughout the project.

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

Continuous attention to technical excellence
and good design enhances agility.

Simplicity--the art of maximizing the amount
of work not done--is essential.

The best architectures, requirements, and designs
emerge from self-organizing teams.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly."

I recommend you start by reading "Scrum: The Art of Doing Twice the Work in Half the Time", by Jeff Sutherland. It is an approachable book for both technical and non-technical readers.

Please login or join to reply

Content ID:

A low voter turnout is an indication of fewer people going to the polls.

- Dan Quayle



Vendor Events

See all Vendor Events