4. Shu-Ha-Ri
leerling kopieert voorbeeld
Shu Follow the rules van leraar
er is maar 1 goede methode
leerling neemt afstand van
Ha Bend the rules leraar, reflecteert, er zijn
meerdere goede methoden
leerling wordt practitioner,
volgt de methode niet meer,
Ri Be the rules
maar weet intuïtief wat het
juiste is
3
5. Use the Scrum Guide
• http://www.improvementfocus.com/media/
pdf/Scrum%20Guide%20NL.pdf
4
16. Delegation Poker
Je bent manager van de afdeling, en moet de volgende beslissingen nemen.
In welke mate kan je dit werk delegeren?
• Je wilt je huidige teamleden betrekken bij de werving en selectie van
nieuwe medewerkers.
• Er moet een nieuwe tool aangeschaft worden voor automated testing.
• Bepalen van het nieuwe salaris van een medewerker na de jaarlijkse
beoordeling.
• Organiseren van een team uitje.
• We starten een nieuw project en moeten bepalen welke aanpak we
gaan volgen. De traditionele aanpak, of Scrum?
• verzin zelf nog een paar situaties ....
10
20. User Story
As a trainee
I want to brainstorm about opportunities and risks
of Agile
Because there’s a trainer around
Because that helps to sink in the ‘slideware’
Because I will also run into these issues when
implementing in my company
12
21. Application
• Workshop
• 2 groups, 2x15 minutes
• “What has made me really thrilled, what
will I start using tomorrow”
• “This is never going to work, because ...”
13
27. The Perfection Game
• This course deserves a rating of [1 .. 10]
because
• this is already good
• It would get a 10
• if you would improve these things
16
28. Agile Manifesto
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 items on
the right, we value the items on the left more.
17
29. 12 principes
Our highest priority is to satisfy the customer
Working software is the primary
1 measure of progress. 7 through early and continuous delivery of
valuable software.
Agile processes promote sustainable
Welcome changing requirements, even late in
development. The sponsors, developers,
2 and users should be able to maintain a 8 development. Agile processes harness change
for the customer's competitive advantage.
constant pace indefinitely.
Continuous attention to technical Deliver working software frequently, from a
3 excellence and good design enhances 9 couple of weeks to a couple of months, with a
agility. preference to the shorter timescale.
Simplicity--the art of maximizing the Business people and developers must work
4 amount of work not done--is essential. 10 together daily throughout the project.
The best architectures, requirements, Build projects around motivated individuals.
5 and designs emerge from self-organizing
teams.
11 Give them the environment and support they
need, and trust them to get the job done.
At regular intervals, the team reflects
The most efficient and effective method of
on how to become more effective, then
6 tunes and adjusts its behavior 12 conveying information to and within a
development team is face-to-face conversation.
accordingly.
18
Editor's Notes
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Toepassing op planning:\n1\n- ga bij elkaar zitten tijdens release/sprint planning\n- leg uit wat je bedoelt met een requirement\n2\n- voor een sprint van 3 weken kan je veel details wel onthouden, documenteer alleen het noodzakelijke\n- snelle oplevering zorgt ook voor snelle leercurve voor schatten en plannen\n3\n- ga bij elkaar zitten ...\n4\n- elke nieuwe sprint kan iets volledig anders zijn dan vooraf gedacht\n