The document discusses Agile software development and provides a personal perspective on adopting Agile practices. It defines Agile as valuing individuals, interactions, working software, and responding to change over processes, tools, documentation, contracts, and plans. The Agile Manifesto emerged from various Agile methodologies and seeks continuous improvement through self-organizing teams delivering working software frequently using principles like customer collaboration and adaptability. Ultimately, the document emphasizes that Agile is a journey of learning and improvement unique to each team's goals and circumstances.

1. An Agile Journey
A Personal Perspective

2. What is Agile Software Development?
“Agile Software Development is a group of software
development methods in which requirements and
solutions evolve through collaboration between self-
organizing, cross-functional teams. It promotes adaptive
planning, continuous improvement and encourages rapid
and flexible response to change” (Wikipedia)

3. Agile Manifesto (agilemanifesto.org)
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 terms on the right, we value the items on
the left far more.

4. Where did the Agile Manifesto come from?
Extreme Programming (XP)
SCRUM
Dynamic Systems Development Method (DSDM)
Adaptive Software Development
Crystral
Feature-Driven Development
Pragmatic Programming
Kanban

5. Sounds great, now what? What does all that
mean?
● How do I implement?
● Which agile methodology do I choose?
● Who is affected?
● What processes are needed to ensure we are meeting our
goals/objectives/ideas
● What are the best practices?
● What is the ultimate end goal?
● Do we focus our time on functioning software and worry about
documenting it later?
● Do we go with the flow and spend less time formally planning since we
all know the one constant is change?
● How do we go about delivering on all those key terms used to describe
Agile?

6. A Personal Perspective
It is a conceptual framework created with values to help guide
you
My key takeaways from the Agile Manifesto:
● The usage of the word “We” in the statement
● It does not state that Agile Software Development defines
how you go about achieving all of these great things
● It does not define a list of things you need to do in order to
be an agile team

7. A Personal Perspective
“We” makes this journey personal
● Individually, yes, but more importantly within the Team
● Individual values may be different but the Team must
collectively agree upon its focused values
The values will likely be very popular and common
● But this doesn’t mean your team is limited to them
● Nor must your team be in 100% absolute compliance
with those specific values

8. Successful Principles (http://agilemanifesto.org/principles.
html)
Concepts/thoughts/guidelines of what successful teams have proven to have and/or attain:
● Customer satisfaction through early and continuous delivery
● Acceptance of and flexibility to handle change in support of competitive advantage
(business agility)
● Delivering functioning software frequently (the frequency is your own)
● Collaboration throughout (visibility)
● Supporting, trusting and providing project teams what is needed
● The most valuable means of communication is face-to-face
● Working software as a primary measure of progress
● Promote sustainable development (predictability)
● Quality designs and solutions
● Simplicity
● Team members that care most about something will be the most effective at gathering
themselves to create, promote and help determine what is best for the product (from
requirements to solutions)
● Self and Team reflection (learning how to make tiny improvements)

9. What is the ultimate end goal?
Its a journey, not a destination. A journey of
continuous improvement
But its YOUR journey
● Not mine
● Not your neighbor or friend who may also work
in an agile shop

10. An Appreciation for the Journey
● Define a goal/destination but don’t be afraid to change it
● Each team’s journey, destination and choices will be different
● Team comparisons are not apples-to-apples
● Respect where one another is in the journey and the choices made along
the way
● Agile Manifesto states that a part of the journey is helping others
● Most important to understand/explain the circumstances that led to a
decision/choice
● Realize that your decisions may or may not lead you in the same
direction
● There WILL be conflict and frustration
● It is not for everyone
● Enjoy the ride for what it is...a road filled with tiny adjustments that the
team cares about in order to get better

12. How do we work today?
Focus areas:
1. Business Value
2. Predictability
3. Business Agility
4. Visibility
5 Rules:
1. Respect for people
2. Continuous improvement
3. Make all work visible
4. Work in priority order
5. Work as a team