Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Agile Project Management

No description
by

Teri Rebo

on 6 August 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Project Management

The Agile Project Management Professional
On time + In scope + Within budget Happy Partner
When will the project be
done
?
How much money can we spend to get it
done
?
What do we have to deliver to be
done
?
Do we have what we need to get everything
done
?
What are the risks that might keep us from getting the project
done
?
What does it mean to even be
done
?
What do Project Managers manage?
An Unhappy Partner
NEVER EQUALS
A Successful Project
Successfully developing a project is more than simply creating a plan and attempting to follow it.
What is project reality?
37%
of all projects succeeded in that they were delivered on time, within budget, and with all required features and functions.

42%
delivered late, went over budget, and/or were delivered with less than the requested features and functions.

21%
were considered complete failure due to cancellation prior to delivery or were never used post completion.
Five key areas that influence whether a project is successful or deemed a failure
Project Management (54%)
Business (21%)
People (14%)
Method (8%)
Technical (3%)

Source: IBM
Source: Standish Group Chaos Report - 2011
Complicated Vs. Complex
Developing IT projects is a COMPLEX endeavor
Cone of Uncertainty
Agile PM Rule #1
Deliver Your Product
As Soon As It's Ready
Work with the customer throughout the project lifecycle
Expose the customer to the product early
Review and evaluate functionality and product maturity on a regular basis
The Key: The customer determines when the product is ready
Agile PM Rule #2
Meet Your Customer's Needs,
Even if they
CHANGE
during the project
Practice continuous planning
New requirements can be added at any time
Avoid "you built what I asked for, but it's not what I need"
Pay close consideration for the best product outcome, rather than adherence to the original plan
Agile PM Rule #3
Focus on
maximizing ROI
rather than simply adhering to the budget
Prioritize work with the customer
Deliver incrementally
Validate business impact of each feature
The customer is always in the driver's seat
Agile PM Rule #4
True product quality is more than a measure of defects.
The
customer
defines quality
Product spec and product quality are not always at the same destination
Remember, the customer is always driving the product direction
Demonstrate the product at the end of each release
Increased collaboration
Agile PM Rule #5
Provide your team with mechanisms to improve.
When your team is
happy
they produce better products.
Build projects around motivated individuals
Trust them to get the job done
Empower them to make decisions that support short-term iteration goals
The PM supports and manages results and outcomes, not tasks and activities
Regular retrospective, then tune and adjust
Top three improvements teams notice after adopting agile
PRODUCTIVITY
QUALITY
CUSTOMER SATISFACTION
Servant Leadership
Predicting outcomes in the distant future is error prone
Manage the manageable
Agile is not a silver bullet
You get out of it what you put into it
As with anything, it takes time to get good at it
Agile Manifesto
Benefits
Higher productivity
Lower costs
Less likely to build functionality not or no longer required
Improved employee satisfaction
Faster to market
Higher quality
Improved stakeholder satisfaction
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Full transcript