-
okay welcome everyone we are here today
-
to talk about the agility insurance
-
project um so before we get started so
-
we're going to go through visioning and
-
go through the various activities to
-
understand what this project is about so
-
thanks to everyone who's here um and I
-
would like to maybe start with something
-
important called team Norms team Norms
-
are uh ground Rules meeting Norms that
-
we set for ourselves to stay on track
-
without distraction or or dysfunction so
-
um as all of you right now are sort of
-
doing a lot of different other things um
-
what do you guys think are some common
-
meeting distractions dysfunctions that
-
we'd like to protect ourselves from that
-
you've been experiencing through other
-
meetings how about Electronics by
-
exception Electronics by exception what
-
does that mean Kelly phones off on vi vi
-
oh so let's let's put that cell phone on
-
vibrate please can we all just put our
-
cell phones on vibrate now together
-
we'll just do the ceremony
-
yay thank you that's awesome what about
-
laptops uh laptops as as as wonderful as
-
this looks that everyone has a laptop if
-
you guys don't mind um during our
-
collaborative sessions we' like you to
-
put your laptops down um I know I'm so
-
sorry it's okay it's okay we do say
-
laptops by exception so if you've got a
-
production support issue or something
-
that you really need to to look at let
-
us know and and and we can use that but
-
we'll give you enough breaks uh to take
-
care of that but it's really important
-
for collaboration that we're all
-
together so let's put iics by exception
-
what else you
-
guys be
-
respectful yeah like one conversation at
-
a time one conversation at a time I love
-
that one how about being on
-
time I like that one I really like that
-
one be on time how about and on time and
-
on time B and can I put that over here
-
end on time what else what are other
-
comments take take notes yes
-
okay take
-
notes stay focused on the topic yes
-
please as much as possible and and it
-
will be okay if you start talking about
-
something and it's off the topic or
-
maybe you're going into the details too
-
early or something like that um we'll
-
bring you back again so
-
stay do you guys think that actually
-
happens quite a bit when we're doing
-
requirements Gathering that we might
-
want a solution too early as opposed to
-
just stick with what the problem is you
-
guys definitely so what can we put up
-
here to make sure that we focus on the
-
Sol on on not the solution but focus on
-
the actual problem that they have as
-
opposed to the
-
solution do we have an agenda we do have
-
an agenda so stay on topic agenda
-
yep and then focus on the what not the
-
how right focus on what they want not
-
the how
-
very good um do you ever experience in
-
meetings where people sometimes think
-
that everything is not going to work so
-
all these Solutions are just not going
-
to go well so like the art of positive
-
art positive I love us being openminded
-
concentrating on what's
-
possible yes so concentrate on what's
-
possible um it doesn't mean that you
-
can't bring up concerns or this is not
-
going to work it just means that okay so
-
how are we going to solve that problem
-
okay awesome well thank you guys that's
-
awesome these are all of our team Norms
-
so as we're facilitating this session
-
don't be upset if we have to sort of
-
hold ourselves accountable for the team
-
Norms okay here's the purpose um of our
-
simulation provide a glimpse into how an
-
agile team goes through the agile life
-
cycle and our very first part of our
-
agenda is going to be visioning so
-
understanding from our product owner
-
from our sponsor from our business user
-
what is this project about what is it
-
that we're trying to accomplish what's
-
the purpose of the project and then
-
we're going to go through and brainstorm
-
the requirements now that we're we
-
visioned what are the actual stories
-
that we have to deliver here then we
-
need to slice some of them down so a lot
-
of times we'll have stories but they'll
-
be epics so they'll be too big to get
-
down so we'll slice them and break them
-
down into smaller chunks and then we're
-
going to do non-functional requirements
-
this usually gets missed because people
-
are always thinking oh here's the
-
functional stories these are the
-
foundational um architectural anything
-
that we need to do to be on the right
-
page and then we're going to go through
-
prioritizing um and then sizing and
-
estimating and then finally developing a
-
plan um and then our next part of the
-
agenda is actually going into the
-
iteration itself and experiencing some
-
of the activities so let's get started
-
with visioning