agile project management why do we need it ?
DESCRIPTION
TRANSCRIPT
Agile Project Management
Why do we need it ?
Agile Project Management (APM)
What is APM ?
Why do we need it ?
Who will benefit from this ?
What are the challenges ?
How can we start APM ?
When should we start APM ?
How can we learn APM?
Where do we learn APM ?
What is APM ?
APM is Lean Project Management!
APM is Clear Project Management!
APM is Bold Project Management!
APM is Change Management!
APM is Built around CUSTOMERS!
PM is NOT the most significant role in APM!
APM is CSFC ! Communication, Simplicity, Feedback, Courage
!
The Agile Manifesto
1. People and Interactions OVER Process and Tools
2. Working Software OVER Comprehensive Documentation
3. Responding to Change OVER Following a Plan
4. Customer Collaboration OVER Contract Negotiation
5. Craftsmanship OVER Executable Code
http://agilemanifesto.org/
Initial Agile Manifesto Signatories
Kent Beck, Mike Beedle, Arie van Bennekum
Alistair Cockburn, Ward Cunningham, Martin Fowler
James Grenning, Jim Highsmith, Andrew Hunt
Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin
Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas
http://agilemanifesto.org/history.html
The Twelve Agile Principles – 1 1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
The Twelve Agile Principles1. Our highest priority is to satisfy the customer
through early and continuous deliveryof valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Why do we need it ?
Bcz speakers like us need to talk ;-)!
Bcz “C/TPM”s failed to deliver results ! Approx 70% of IT projects failed! Conventional/Traditional Project Managements
are too heavy to lift ;-)!
Bcz we need CUSTOMERS to stay HAPPY always! Both Internal & external customers !
Bcz Software / IT Systems are THOUGHT Products! Thought of both the Developers & Customers ! Thought evolves over TIME!
Who will benefit from this ?
CUSTOMERS !
Domain Specialists !
System / Business Analysts !
Software Programmers !
Software Testers !
Technical Writers !
Middle Managers !
Senior Managers !
Public ! And who is LEFT, then ;-) ??
What are the challenges ?
Conventions ! Traditions !
Conventional / Traditional Mindsets !
The “Almighty” Project Managers !
The “Almighty” Middle Managers !
The “Almighty” Top Managers !
The “Almighty” Customers !
The “Almighty” Developers Too !
Absence of TEAM-ing in “true sense” !
How can we start APM ?
Let us start in a “Lean” way!
Let us start immediately, but incrementally!
Let not wait for the “Guru” to come!
The “Gurus” are in US (not USA;-)…
Let us CHANGE our Org Culture Blow the CSFC winds heavily!
Start with “INTROSPECTION”!
Start with “REVIEW”! (Let Google SE HELP us!)
When should we start APM ?
Almost anytime ;-)…
Better is to start from the beginning of a small / prototypical project to learn solidly!
Pls do NOT CHANGE everything at once!
Process EVOLUTION is the KEY!
REVOLUTIONARIES is the World are RARE!
Pls do NOT wait for that MAGIC Moment!
Start Immediately ! At least with the XP Planning game or the Poker Game !
How can we learn APM?
Attending seminars / workshops like this ! ..
Sharing experience with practitioners!
Staring SMALL, Starting SIMPLE!
Fixing the Person In The Mirror (PITM)!
Adopting Open Org Culture in True Sense!
Adopting Agile Core Values: CSFC
Starting with CRYSTAL, only Retrospectives!
Starting with SCRUM ?
Let may flowers bloom in Agile
Where do we learn APM ?
Attending seminars / workshops like this ! ..
Agile BD (http://www.agilebd.org) http://groups.google.com/group/agilebd (you need to register here)
http://agilefaqs.com/
http://www.agileacademy.com.au/agile/syllabus/agile-project-management
… And many more .. Do some more Google Search .. You alone will find many ……