View
1.077
Download
0
Category
Preview:
DESCRIPTION
Citation preview
www.pm-podcast.com
Episode 186The Agile Manifesto
For Project Managers
Presented by:
Cornelius Fichtner, PMP
www.pm-podcast.com
This presentation is available as a PM Podcast video episode at
www.pm-podcast.com
Overview
• www.agilemanifesto.org • Short history (really short!)• The Manifesto• Twelve Principles
Strong Focus on Project Management
History of The Agile Manifesto
• 17 proponents of various SW development methods met to discuss better ways to develop software
• Known as the “Agile Alliance”• The Agile Manifesto was released on
February 13, 2001.• Contains core values & principles
• More history:• http://agilemanifesto.org/history.html
The Agile Manifesto
We are uncovering better ways of developingsoftware 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 onthe right, we value the items on the left more.
Interpretation for Project Managers
• Let team & users cooperate• Become a facilitator
Individuals and interactions over processes and tools
• Focus on delivery• Don’t abandon documentation
Working software over comprehensive documentation
Interpretation for Project Managers
• Customer vision is at center• Manage relationships not contracts
Customer collaboration over contract negotiation
• Let customers change their mind• Use change-friendly methodologies
Responding to change over following a plan
“This would NEVER work in our company!”
• Prescribed methodologyIndividuals and
interactions over processes and tools
• PMP Exam SimulatorWorking software
over comprehensive documentation
• Legal requirementsCustomer
collaboration over contract negotiation
• Construction ProjectsResponding to change over
following a plan
“Solution”
Do what you can
•Remember: There is value in the things on the right
12 Manifesto Principles
Software
Changes
Delivery
Coop
Motivation
Communication
Progress
Sustainability
Excellence
Simplicity
Self-organization
Reflect
Principle 1 – Results orientated
Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
Satisfied customers = #1
Deliver, deliver, deliver
Focus on your customer
Principle 2 – Change Management
Welcome changing requirements, even late in development. Agile processes harness change
for the customer's competitive advantage.
Changes are good!
We welcome changes to help you
Focus on features, not budget
Principle 3 – Frequent Milestones
Deliver working software frequently, from a couple of weeks to a couple of months,
with a preference to the shorter timescale.
Faster time to market
Short sprints, iterations, cycles…
Release on time
Principle 4 – Teamwork
Business people and developers must work together daily throughout the project.
Single point of contact?
Developers & customers
Team Developoment
Principle 5 – Yes they can!
Build projects around motivated individuals. Give them the environment and support they
need, and trust them to get the job done.
PM’s job in Agile
Embrace Theory Y
Step back
Principle 6 – Communications Management
The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
Co-location
Meet / call / Skype
Any team
Principle 7 – Progress Measurement
Working software is the primary measure of progress.
“We are on target”
Documents don’t count
Internal reporting?
Principle 8 – Maintenance
Agile processes promote sustainable development. The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Post project
Backlog, burn-down, etc.
Prioritization & collaboration
Principle 8 – Quality
Continuous attention to technical excellence and good design enhances
agility.
Supports #1 and #3
Good design needed
PM becomes conscience
Principle 10 – Just DON’T do it!
Simplicity--the art of maximizing the amount of work not done--is essential.
Agile ≠ Less
Simplify = Central
Tradeoff
Principle 11 – Team organization
The best architectures, requirements, and designs emerge from self-organizing
teams.
Intelligent people!
Let them organize
Facilitate
Principle 12 – Lessons Learned
At regular intervals, the team reflects on how to become more effective, then tunes
and adjusts its behavior accordingly.
Throughout project
Not only at endAgility =
changeability
Agile Manifesto - Review
There is room for PMs
Our role changes
PM’s responsibility is distributed
FACILITATOR
Different title
Thank you for watching!
www.pm-podcast.cominfo@pm-podcast.com
And finally, we have this…
The difference between project success and failure is a good PR
company
Recommended