Whether you are a professional trainer or trying to bring agility to your organization or team, you no doubt have encountered the difficulty in conveying agile values and principles. Learning practices and techniques is easy in comparison; You learn by doing. But how do you teach a philosophy or mindset? How do you 'do' a value?
Through trial and error, through hundreds of classes, through training thousands of agile practitioners, we have put together a set of best practices (and not-so-best practices) for delivering powerful agile learning experiences. Participants in this session will walk away with a toolkit they can put to use the next day. The toolkit will include scenario simulations, learning games, discussion generators, reenforcement exercises, student patterns, common pitfalls, and other activities to help you get out of the way and let the learning happen.
Links to the activities we did during the presentation:
'What Were They Thinking?' game: http://tastycupcakes.org/2009/06/what-were-they-thinking/
'Pocket-Sized Principles' activity: http://tastycupcakes.org/2010/01/pocket-sized-principles/
'Presto Manifesto' activity: http://tastycupcakes.org/2009/06/presto-manifesto/
11. AGILE LEARNING improvingenterprises.com
QUESTION BACKLOG
What is the
difference between
Scrum and Agile?
How long should a
Sprint be?
How do I keep my
Daily Scrum to
under 15 minutes?
How do I break
down Epics?
How do I get my
manager to buy-in to
agile?
What do I do when I
have a total a$$ on
the team?
CONSULTING
MENTORING
COACHING
25. ValuesValues
Individuals and Interactions
Processes and Tools
Working Software
Comprehensive Documentation
Customer Collaboration
Contract Negotiation
Responding to Change
Following a Plan
What%Were%They%Thinking?
32. AGILE LEARNING improvingenterprises.com
POCKET-SIZED PRINCIPLES
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.
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.
33. AGILE LEARNING improvingenterprises.com
POCKET-SIZED PRINCIPLES
Principles
EarlyValue
Welcome Change
Frequent Delivery
Collaborate Daily
Motivation & Trust
Face to Face
Working Software
Sustainable Pace
Technical Excellence
K.I.S.S.
Self-Organize
Reflect and Adjust