A

  F  
Agile Meetings Cube Agile Meetings Cube
Team   Team  
Sprint Review Sprint Restrospective
1  >  h   1  >  h  
ADer  sprint   PO,   ADer  sprint   Invited  
✶ Team  take  collec1ve  ownership/responsibility/pride  in   Others   ✶  Inspect  and  adapt  engine  
what  they  have  done  
✶  Team  take  responsibility  for  its  own  way  of  working  
✶ Product  Owner  accepts  sprint  
   
✍ De
✍ Ti mo  of  wo
m rk
✍ Va e  Boxing   ing  soDw
q  What did we finish? ✍ Fe l i d a1o are
q  What happened this sprint?
edba n/Accep
q  How does it work? ✍ Q&A c k   t an ce
q  How do we feel about it?
 se
q  What have we learnt? d✍ One  fro ssion   q  What can be improved?
B  

emon m  ea

E  
Is it OK? c
q  ✍ 1   strates
h  team   q  What’s most important to
h ou r
q  Any questions?   p repa
ra1o improve?
What did we not accomplish? n  
q  q  What different ideas on how to

Peter Antman, 2014

Peter Antman, 2014

improve do we have?
q  What do we do next?
q  Have we done what we planned
last time?
ü  Knowledge  on  what  the  
team(s)  have  achieved   ü  An  understanding  of  what  
works  and  what’s  not  
ü  Acceptance  of  what  has  been  
done   ü  A  short  list  of  improvements  
ü  Team  bonding  
ü  Sense  of  progress  
C   D  
 B   C  
Agile Meetings Cube Agile Meetings Cube
Team   Team  
Daily Standup Sprint Planning
15  min   1  –    4  h  
Every  day   PO,   Start  of  sprint   PO  
✶  Make  a  plan  for  the  next  24  hours  on  how  to  move  the   Others   ✶ Team  chose/pull  most  priori1zed  work  and  make  a  
most  important  story  forward  to  comple1on   shared  plan  for  the  sprint  (focus  &  commitment)  
✶  Transparency    on  progress   ✶ Transparency  on  what’s  realis1c  to  work  on  
   
✍ Talking  s1c
k  
✍ Time  boxin
g  
q  What did I do yesterday? ✍ No  repor1n q  Which are the most important stories
g   this sprint?
✍ Update  boa ✍ Velocity/Yesterdays  
q  What do I plan to do today? rd  
q  Is there an overall goal with this weather  
✍ Burndown  
q  Any impediments? sprint? ✍ INVEST  
G  

✍ Time  Boxin

D  
q  How long time is left for this g   q  How many stories can we take on? ✍ Spike  
✍ Tech  
story? discussion  aDe q  Are the stories small enough? ✍ Planning  poker/Task  
r   q  Do we need to do a spike?
mee1ng   point  sizing  
q  Anyone I can help?

Peter Antman, 2014

Peter Antman, 2014

q  How are we going to demonstrate ✍ Story  tag  cloud  
q  Are we doing all we can to get each story ✍ Time  Boxing  
the top story done? q  Do we know all the steps we need to
take (DOD)?
q  Do we believe in this?

ü  Agreement  on  what  to  work  on   ü  A  priori1zed  sprint  backlog  
ü  Sense  of  collec1ve  
with  stories  the  team  
responsibility  
ü  Discovery  of  impediments   believes  in  

H   I  
 G   H  
Agile Meetings Cube Agile Meetings Cube
PO   PO  
Release Planning Backlog Grooming
1/2  –    2  d   1  –  2  h  
Theme  or  Epic   Team,   In  every  sprint   Team  
✶ Help  PO  or  stakeholder  to  handle  expecta1ons  by   Others   ✶ Prepare  User  Stories  for  sprint  planning  
crea1ng  an  agile  plan  
✶ Create  a  shared  understanding  of  customer  needs    
✶ Align  business  and  team  understanding  of  customer  and  
business  value   &  business  value  expressed  in  user  stories  

ing  
ry  Mapp
User  Sto apping
q  Why are we doing this? ✍
ct M
✍ Impa eses q Are the right stories at the top
q  What is the impact? th n&
How do we know?
✍H y p o
man Es
timatio q Do we understand them? I ndepen
q  ✍ Bock d
Negotia ent
q Do they give value?
A  

q  What needs have the user? Prio ble

g Valuable
stormin

I  
q  What’s the highest risk? ✍ Brain point sizing q Can we do them in a week? Estimable
q  Technical? ✍ Story Usable
&
✍ Valu  
able & q Do we know when they are TSemall

Peter Antman, 2014

Business?

Peter Antman, 2014

q  stable
le
q  Social Feasib finished?
q  What’s the least we can do?
q  What step do we take?
q How can we test them?
q  How big are the steps? q How do we demo?

ü  User  Stories  that  are  

ü  A  preliminary  backlog   understood  and  that  can  be  
ü  A  visualized  release  plan   planned  during  the  sprint  
mee1ng  
F   E