The document provides an overview of Agile software development. It defines Agile as a collection of principles and practices aimed at improving collaboration, reducing documentation overhead, and making development teams more responsive to changes. The document discusses Agile methods like Scrum and Extreme Programming. It also covers Agile concepts such as user stories, velocity, and retrospectives. The document aims to help attendees understand what Agile is, its benefits, and how it differs from traditional waterfall methods. Training and certification options in Agile are also listed.
2. Goals/Objectives
Gain an understanding of:
Agile Software Development
Definition
Benefits
Practices
Objective:
As an attendee I can walk away with an understanding of
what Agile is and what it isn’t
PMIWB Agile Introduction (Nov 2011)
3. What is Agile Development?
A collection of principles and practices aimed at:
Improving collaboration between the Business and
Technology
Reducing the documentation and management overhead on
projects
Making development teams more responsive to changes in
business requirements
Giving the Business early visibility of what will be delivered
MYTH: No documentation
MYTH: Undisciplined
MYTH: Agile is a process
MYTH: Agile is the Silver Bullet
PMIWB Agile Introduction (Nov 2011)
4. Agile Manifesto (2001)
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.[1]
[1]http://agilemanifesto.org/
PMIWB Agile Introduction (Nov 2011)
8. Agile is gaining popularity:
Current Challenges
Nowadays the predictable & repetitive work is done much
faster (often automated)
Things (requirement/need) change much quickly
To stay competitive we need to continuously inspect & adapt
We need to deal with more uncertainty
How do we address:
Time boxed delivery & continuous feedback loop helps to
reduce uncertainty
We need to learn as we progress
Early & sustainable rate of valuable feature delivery
PMIWB Agile Introduction (Nov 2011)
9. How does it benefit _?
_client
Early ROI
More control on budget
Transparency
Incorporate changes as market dynamics change
Frequent deployable software
PMIWB Agile Introduction (Nov 2011)
10. How does it benefit _?
_developer
Transparency (constant feedback)
Protection from client requests
Insight into client requests
Empowerment
Clear expectations
Sense of accomplishment and recognition
More development
Less documentation
Fewer requirements
PMIWB Agile Introduction (Nov 2011)
12. Agile Methodologies
SCRUM (most popular):
It is an iterative process of development used with agile software development. The roles in Scrum are
the ScrumMaster, the Product Owner and the Team. During each sprint the team creates an increment
of potential shippable software.
Extreme Programming (XP):
It is a traditional software engineering practices (daily interactions, working software, testing, etc.) taken
to so-called "extreme" levels, leads to a process that is more responsive to customer needs ("agile“),
while creating software of better quality.
Feature-driven Development (FDD):
It an iterative development process. This practice is driven from a client-valued functionality (feature)
perspective.
Test-driven Development (TDD):
It is a software development technique that uses short development iterations based on pre-written test
cases that define desired improvements or new functions. Each iteration produces code necessary to
pass that iteration's tests.
Lean:
It is a process designed to eliminate waste, amplify learning, make decisions late, fast delivery,
empowered teams, product integrity and an fully understood system.
… (& many others)
PMIWB Agile Introduction (Nov 2011)
13. The People Involved
The Agile Team
Architects
Developers, Analysts, Designers
Quality Assurance, Testers
Tech Writers
Product Owners / Customer Representatives
Project Managers / ScrumMasters
Note: Teams are small (~7), preferably co-located, cross
functional. Scale by adding teams, not more people
PMIWB Agile Introduction (Nov 2011)
14. The “Other” People Involved
Management
Note: Can attend dailies but cannot speak. Can
participate in planning. Interact with team through
Project Manager / ScrumMaster
PMIWB Agile Introduction (Nov 2011)
16. Who uses Agile?
Microsoft AOL
Yahoo Intuit
Google Nielsen Media
Siemens First American Real Estate
Nokia BMC Software
Capital One John Deere
Lockheed Martin PwC
Philips Lexis Nexis
BBC Sabre
Intuit Salesforce.com
Time Warner
…
PMIWB Agile Introduction (Nov 2011)
17.
18. Moving Forward…
It is simple – but difficult
An understanding and appreciation of Agile values and
principles is essential
Agile Methodology alone will not create better products.
Engineering, design and testing practices need to become more
Agile
Interactions and communication need to become clearer, more
personal and more transparent
Honesty, trust and a sense of commitment need to be developed
When the going gets tough it is easy to slip back into the old way
of doing things. Courage is essential.
PMIWB Agile Introduction (Nov 2011)
22. References:
Web Sites:
PMI Agile Community of Practice (Agile CoP)
http://agile.vc.pmi.org/
Scrum Alliance
http://www.scrumalliance.com/
BOOKS:
Agile Project Management with Scrum
Ken Schwaber
Agile Estimating and Planning
Mike Cohn
WEBINARS:
All presentations on InfoQ about Agile
PMIWB Agile Introduction (Nov 2011)