2. The team
Julien Biezemans
julien@agilecampustour.org
@jbpros
Simon Schoeters
simon@agilecampustour.org
@cimm
Marc Lainez
marc@agilecampustour.org
@mlainez
If you want to tweet use the hashtag #actbe
21. A few leads...
Customer is not satisfied
Team didn’t have anything to say
Requirements stayed rigid throughout the project
Changes had to be hardly negotiated
Bill dispatched the work amongst his team members
Team started to work on every aspect of the application
Delays could only be identified at the end of the project
Team had to do extra hours
Team had to take shortcuts to finish on time
25. Bob suggests that they work in iterations,
but before that, what is the vision of the
project?
26. Bob and the guys from namco then write
®
user stories, all these user stories are part of
the product backlog
~~~~~~~~~~~~
~~~~~~~
~~~~~~~~~~~
~~~~~~~~
~~~~~~~~
~~~~~~~~~~
In order to apply my
~~~~~
~~~~~~~~ strategy
As a player
~~~~~~~~~
~~~~~~~
~~~~~
~~~~~~
I want to move pacman in
~~~~~~~~~~~~
four directions
~~~~~~~~~~
~~~~~~~~~~~~
27. He asks the guys from namco to prioritize
®
the user stories
~~~~~~~~~~~~
~~~~~~~~
~~~~~~
~~~~~~~~~~~~
~~~~~~~
~~~~~~~~~~~
~~~~~~~~
~~~~~~~~
~~~~~~~~~~
~~~~~
~~~~~~~~
~~~~~~~~~
~~~~~~~
~~~~~
~~~~~~
28. Together, they review a few of the top user
stories, and add details, to make sure the
team can start working on them
29. They all agree, with the team on what being
“done” actually means...
30. The team itself then estimates the user
stories, Bob and the guys from namco are
®
there only to answer to the team’s
questions
31. The team tries to figure out how much work
they can accomplish in one iteration
32. From the estimated user stories, we take
the top prioritized ones that fit the team’s
maximum work constrain
}
~~~~~~~~~~~~ 3
~~~~~~~~~~~~ 3 ~~~~~~~~
~~~~~~~~ ~~~~~~
~~~~~~
~~~~~~~~~~~~ 5
~~~~~~~~~~~~ 5 ~~~~~~~
~~~~~~~ ~~~~~~~~~~~
~~~~~~~~~~~
~~~~~~~~ 2
~~~~~~~~ 2 ~~~~~~~~
~~~~~~~~ ~~~~~~~~~~
~~~~~~~~~~
~~~~~ 3
~~~~~ 3 ~~~~~~~~
~~~~~~~~ ~~~~~~~~~
~~~~~~~~~
~~~~~~~ 5
~~~~~~~ 5 ~~~~~
~~~~~ ~~~~~~
~~~~~~
~~~~~~~~~~~~ 2
~~~~~~~~~~
~~~~~~~~~~~~
~~~~~~~~~~~~ 8
~~~~~~~~
~~~~~~
~~~~~ 13
~~~~~~~~
~~~~~~~~~
34. Meanwhile, Bob and the guys from namco ®
are adding more details to the next user
stories
35. When the team thinks a user story is
“done”, the customer can test it and give
feedback
36. Not satisfied? Team changes the feature
right away, included the customer’s
feedback
37. Customer has another great idea, pacman
can teleport when he eats a special fruit!
38. No worries, Bob adds it in the product
backlog, it’ll be done during the next
iteration
~~~~~~~ 5
~~~~~
~~~~~~
In order to escape the
~~~~~~~~~~~~
~~~~~~~~~~
2 ghosts
~~~~~~~~~~~~
As a player
~~~~~~~~~~~~
~~~~~~~~
8
I want pacman to teleport
~~~~~~
~~~~~ 13
~~~~~~~~
~~~~~~~~~
39. At the end of the iteration, the team makes
a demo of what was “done” during the
iteration
40. And they gather for a retrospective, to see
how they can improve
41. When they reach the deadline, there are still
some stories left in the backlog but the
customer is fully satisfied
~~~~~~~~~~~~ 8
~~~~~~~~
~~~~~~
~~~~~ 13
~~~~~~~~
~~~~~~~~~
45. Values and principles
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
http://agilemanifesto.org
53. In order to <business value>
As a <role>
I want <functionality>
54. With these user stories, they have built the
product backlog
~~~~~~~~~~~~
~~~~~~~
~~~~~~~~~~~
~~~~~~~~
~~~~~~~~
~~~~~~~~~~
In order to apply my
~~~~~
~~~~~~~~ strategy
As a player
~~~~~~~~~
~~~~~~~
~~~~~
~~~~~~
I want to move pacman in
~~~~~~~~~~~~
four directions
~~~~~~~~~~
~~~~~~~~~~~~
55. They then prioritized these stories by
business value
~~~~~~~~~~~~
~~~~~~~~
~~~~~~
~~~~~~~~~~~~
~~~~~~~
~~~~~~~~~~~
~~~~~~~~
~~~~~~~~
~~~~~~~~~~
~~~~~
~~~~~~~~
~~~~~~~~~
~~~~~~~
~~~~~
~~~~~~
57. What do we tackle by doing that?
Customer is not satisfied
Team didn’t have anything to say
Requirements stayed rigid throughout the project
Changes had to be hardly negotiated
Bill dispatched the work amongst his team members
Team started to work on every aspect of the application
Delays could only be identified at the end of the project
Team had to do extra hours
Team had to take shortcuts to finish on time
59. What next?
Blu
Week Day
Sto TO WI D
~ Na
rie D P O
~
s O (4) NE Mi
~
~
~
60. What next?
Blu
Week Day
Sto TO WI D
~ Na
rie D P O
~
s O (4) NE Mi
~
~
~
61. Bob asked his team to estimate the
complexity of the user stories in
story points
62. Bob asked his team to estimate the
complexity of the user stories in
story points
63. Bob asked his team to estimate the
complexity of the user stories in
story points
64. Bob asked his team to estimate the
complexity of the user stories in
story points
1/200
65. Bob asked his team to estimate the
complexity of the user stories in
story points
~~~~~~~~~~~~
~~~~~~~~
3
In order to apply my
3
~~~~~~
~~~~~~~~~~~~ 5
strategy
~~~~~~~
~~~~~~~~~~~ As a player
~~~~~~~~ 2
I want to move pacman in
~~~~~~~~
~~~~~~~~~~ four directions
~~~~~ 3
~~~~~~~~
~~~~~~~~~
~~~~~~~ 5
~~~~~
~~~~~~
Handle 4
Build grid directions, north,
south, east, west
Implement controls
84. What do we tackle by doing that?
Customer is not satisfied
Team didn’t have anything to say ++
Requirements stayed rigid throughout the project
Changes had to be hardly negotiated
Bill dispatched the work amongst his team members
Team started to work on every aspect of the application
Delays could only be identified at the end of the project
Team had to do extra hours
Team had to take shortcuts to finish on time
86. What now?
Blu
Week Day
Sto TO WI D
~ Na
rie D P O
~
s O (4) NE Mi
~
~
~
87. What now?
Blu
Week Day
Sto TO WI D
~ Na
rie D P O
~
s O (4) NE Mi
~
~
~
88. Every morning they gathered in front
of the team board
Blue
Stories TODO WIP(4) DONE
~~~~~~~~~~~~3
~~~~~~~~
Name
~~~~~~~~~~~~5
~~~~~~~
~~~~~~~~ 2
~~~~~~~~
Mis
~~~~~ 3
~~~~~~~~
~~~~~~~ 5
~~~~~
89.
90. During a “daily standup”
Blue Team
Stories TODO WIP(4) DONE
~~~~~ 3
Name tags
~~~~~ 5
~~~~~ 2 Misc.
~~~~~ 3
~~~~~ 5
3 ways the brain creates meaning
110. And what was accepted was ready to be
shipped in production
111. After the demo, Bob’s team organized a
retrospective to improve the way they work
112. What do we tackle by doing that?
Customer is not satisfied
Team didn’t have anything to say ++ ++ ++
Requirements stayed rigid throughout the project
Changes had to be hardly negotiated
Bill dispatched the work amongst his team members
Team started to work on every aspect of the application
Delays could only be identified at the end of the project
Team had to do extra hours
Team had to take shortcuts to finish on time
121. What do we tackle by doing that?
Customer is not satisfied
Team didn’t have anything to say ++ ++ ++
Requirements stayed rigid throughout the project
Changes had to be hardly negotiated
Bill dispatched the work amongst his team members
Team started to work on every aspect of the application
Delays could only be identified at the end of the project
Team had to do extra hours
Team had to take shortcuts to finish on time