Transcript
Use with ChatGPT / Claude Auto-scroll A
Introduces the daily scrum in the context of the sprint and explains the meeting's purpose, timing, and three guiding questions.
welcome to part 4 of scrum training series the daily scrum meeting i'm michael james i help organizations do scrum and related agile practices as you learned in part 3 our team has already conducted a backlog refinement meeting anda sprint planning meeting now we'll watch one of their daily scrum meetings somewhere in the middle of sprint execution i'll quiz you during the scene as usual each morning like most scrum teams wonder what we'll find in theteam room this time
task board may look messy to us but it's for their use not to make outsiders comfortable for the ultimate in realism and to save on production costs some of these characters are voiced by actual scrum team members allthe situations in these modules are based on things i've experienced as a team member or seeing as a coach hello as your scrum master i'm here to help you with your daily scrum meeting we do this at thesame time same place each day standing up for 15 minutes so what is the agenda we only have 15 minutes as a self-organizing team you're collectively responsible for collaborating with each other and this meeting can help remind youto do that to help with that there are three suggested questions what did i do yesterday what will i do today what impedes me
Team members share progress on database work and testing, while surfacing uncertainties about test scope and pairing on the task.
i'll start yesterday i went to the facilities department to get better blinds for the team room windows because you guys said you couldn't see your screens on sunny days or siesta dropped by to visit sammy seagull you knowthat sales manager who keeps asking a couple of you for special favors to show him where his requests are on the product backlog and how to reach the product owner about moving them up i think he already knewthat but he didn't realize the effects of distracting the team was so visible to everyone now that we're doing two week iterations today i'll be with you here in the team room because a couple of you said youwanted help learning test driven development my impediments today hmm sometimes i know what needs to be done but struggle with the courage to do it i'm finding it difficult to persuade the other scrum masters to contribute to the
organizational impediments list we posted on the wall
hi team yesterday i finished mapping the legacy database schema at least the parts that we'll need for the view grades ppi i'm not really a database expert but i got a lot of help from peter who is sonow we both know it we checked each other's work so i'm going to move this task to completed i'll start on the code to read the grades from the legacy database writing tests at the same time as i'vestarted learning i'd like to pair with andy on
this
tell us whether you have any impediments i was just getting to that i'm uncertain whether the automated test should go all the way to the database tables written by the legacy system or if i should just use mockobjects i've got some ideas about that i'll work with you on it okay
The team reacts to the product owner's absence and debates whether that is appropriate, then redirects the conversation back to the daily scrum.
wait a minute our product owner isn't here
yes today the product owner is out sharing our product vision with the ceo i thought the product owner was supposed to be at every daily scrum even though we've got other business expertise on the team the product owneris the final arbiter of requirements questions i thought the product owner was not allowed at the daily scrum we'll never know our true potential for self-organization if someone who outranks us in the company watches our every move yeahplus if we can't function for one day without the product owner the organization might delegate the role to someone with no real vision or authority just because they're less busy at least our product owner can influence the ceowould you rather have clueless clyde or myopic myron while the product owner has an explicit role in the other meetings scrum's rules allow the product owner to not attend the daily scrum
are we on topic for the daily scrum no probably not this should probably be a sidebar let's keep a list of sidebar topics so whoever's interested can discuss this after the meeting
yesterday i did the page layout for the view grades pbi with help from andy who checked my work today i'd like to write the related html and style sheet i'll pair program with you we're still cleaning up themess from the last time we wrote code without pair programming
my only impediment is that i wanted to show our page layout to the product owner for feedback and he's not here i'll add a task to make sure it doesn't get forgotten
Carla and Tim describe their test-driven development work, the database contention issue, and personal impediments affecting their collaboration.
okay team what i did what i will do and what impedes me i spent yesterday pair programming with tim on the update grades pbi using test driven development as you all know that includes writing a few lines offailing test code then writing a few lines of product code
then refactoring to improve the design without changing the behavior
and then we did it again
tim and i went through that cycle many times yesterday finally getting the normal use case done
tim helped me find an error condition we corrupt the database if the legacy system tries to write the same record at the same time so i'm adding a new task for us to handle database contention
today i'd like to keep working on this if it's okay with you guys i do have one impediment today i have to leave work early to get my dad from the airport
hi team as carla said i spent most of yesterday pair programming with her on the update grades pbi as a traditional tester i'm not very familiar with programming but since carla was describing her thoughts as writing the codei found i could contribute a lot i was able to point out edge cases she wouldn't have thought of write some of the automated tests and spot messy codes so we could refactor it today i want to keepworking with carla on the database contention issue with update grades as far as impediments i'm an introvert i'm still getting accustomed to the amount of interaction expected on a scrum team sometimes i need to retreat to my oldoffice to take a break
The team discusses the new continuous integration server, Eddie's late arrival, and the importance of working transparently before the scrum ends.
okay team yesterday i got our new continuous integration server running it reruns all the tests every time we make a code change and alerts us instantly about regression failures today i plan to plug our old tests into ournew continuous integration process my impediment is that i don't understand some of the recent changes eddie made to the build file hey where is eddie anyway eddie's always late eddie's in the space-time
continuum
hi guys sorry i'm late again did i miss anything
eddie i know you were up all night working on the build file by yourself and you probably think this speeds us up but we see product development primarily as knowledge creation not just construction when you work in isolationand then miss meetings like this one it actually slows us down in the long runlet's talk about this offline in another sidebar i'll try to mediate
we've got some sidebar topics here that some of you want to stay and talk about afterwards the daily scrum is
over
eventually you might not need me for this
meeting
that was just one example of a daily scrum meeting to learn more about scrum explore these links to learn a lot more about scrum try one of our classes this concludes module 4.