Don't "Do" Agile, Be Agile
-
Upload
adam-zolyak -
Category
Business
-
view
381 -
download
1
description
Transcript of Don't "Do" Agile, Be Agile
Don’t “Do” Agile.
Be Agile.
Presented by Adam ZolyakJuly 2014
CC 2.0 https://www.flickr.com/photos/vfsdigitaldesign/5396691102/
To understand the commonly
accepted set of agile principals
to evaluate if you are agile.
takeaways
And to start thinking about our own principles.
Come to my next Lunch and Learn “Why Iterate?” about the business and customer benefits of iteration
Tools and practices for building
better software and better
satisfying customers.
what is agile?
But which tool is right for the job?
Doing AgileLearning the practices and applying
them without knowing the principles
behind them and without knowing
when to tailor and select practices.
doing vs. being agile
Being AgileAdopting and understanding the principles and applying the right practices and tailoring them to different clients and situations.
which tool?
Using the right tool can make
the job easier and achieve the
desired outcome. And it’s important to read the owner’s manual for your tools as well :)
doing vs. being agile
Scrum Pairing AutoTesting
Kanban XP Backlog
Burn Down Demos Standup
Story Mapping
Cycle Time
WIP Limits
Agile Principles
Client Goals
+ =The right tools for the job!
Agile Principles
The 12 Principals of Agile – a
set of first principals to choose
the right tools and practices.
agile principles
And an extra 13th bonus principle…
http://agilemanifesto.org/principles.html
Our highest priority is to satisfy
the customer through early and
continuous delivery of valuable
software.
satisfy the customer1
Welcome changing
requirements, even late in
development. Agile processes
harness change for the
customer's competitive
advantage.
welcome change2
Deliver working software
frequently, from a couple of
weeks to a couple of months,
with a preference to the shorter
timescale.
deliver frequently3
Business people and the
development team must work
together daily throughout the
project.
be a team4
Build projects around
motivated individuals. Give
them the environment and
support they need, and trust
them to get the job done.
trust and motivate5
The most efficient and effective
method of conveying
information to and within a
development team is face-to-
face conversation.
talk, face to face6
Working software is the primary
measure of progress.
working software7
Agile processes promote
sustainable development. The
sponsors, development team,
and users should be able to
maintain a constant pace
indefinitely.
sustainable, forever8
Continuous attention to
technical excellence and good
design enhances agility.
quality and polish9
Simplicity—the art of
maximizing the amount of work
not done--is essential.
simplicity10
The best architectures,
requirements, and designs
emerge from self-organizing
teams.
iterate and evolve11
At regular intervals, the team
reflects on how to become
more effective, then tunes and
adjusts its behavior accordingly.
always be improving12
Be Lean. If a practice, process,
or tool doesn’t add value,
eliminate it or simplify it.
eliminate waste13
Spotify
what are our principles?
http://labs.spotify.com/2013/03/20/agile-a-la-spotify/
352 Inc
what are our principles?
http://www.352inc.com/blog/a-manifesto-for-agile-web-development/
what are our principles?
???I look forward to the
conversation!Questions / Comments?
Be Agile!
Build Great Products!
CC 2.0 https://www.flickr.com/photos/vfsdigitaldesign/5396691102/
Inspiration and SourcesBeing Agilehttp://www.slideshare.net/MikePearce/being-agile-7819456
Ingredients to Sustainable Agilehttp://www.slideshare.net/AhmedSidky/introduction-to-icagile-through-sustainable-agility-kiev-2013