4. Daily Scrum Meeting
Our team has already conducted a backlog and Sprint Planning Meeting. This team meet each morning like most Scrum team in the team room. If we have
people to serve on a role, obviously they must adjust that. Team Room:
Committed Backlog Items Not Started In Progress Completed
Task board looks messy but it is for their use.
ScrumMaster: Hello, as your ScrumMaster, I'm here to help you with your daily Scrum Meeting. We do this at the same time, same place, each day, standing
up for 15 minutes.
Team Member: so, what is the ajenda. We only have 15 mins.
Scrum Master: At this meeting, each of you will report to the rest o the team your answers to the three questions.
Quiz1: Scrum Master
Which of the following are explicitly defined questions in the Dail Scrum Meeting?
Yes A. What will I do today ( Or before the next Scrum meeting)?
No B. What are my actuals compared to my estimates ( in hours or days)?
Yes C. What impedes me ( blocks my progress, reduces my effectiveness, etc.)?
No D. What time is the next Daily Scrum Meeting?
Yes E. What did I do yesterday ( or since the last Scrum meeting)?
ScrumMaster: As a self-organizing team you're collectively responsible for collaborating with each other, and this meeting can help remind you to do that.
To help with that , there are three suggested questions:
Daily Scrum three questions:
A. What will I do today ( Or before the next Scrum meeting)?
B.What impedes me ( blocks my progress, reduces my effectiveness, etc.)?
C.What did I do yesterday ( or since the last Scrum meeting)?
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. Also yesterday I dropped by to visit Sammy Seagull-- that sales manager who keeps asking a couple of you for special fovors-- to show him
where his request are on the product backlog and how to reach the product owner about moving them up. I think he knew that, but he didn't realize the
effects of distracting the team were 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 you wanted help learning Test Driven Development.
My impediments today...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
ScrumMasters to contibute to the organizational impediments list we posted on the wall. (7 obstacles to Enterprise Agility by Michael James)
Team Member 1: Hi team, Yesterday I finished mapping the legacy database schema....at least the parts that we'll need for the View Grades PBI. I'm not a
database expert, but I got a lot of help from Peter, who is. So, now we both know it. We checked each other's work, so I'm going to move this task to
"completed".
Today I will start on the code to read the grades from the legacy database, writing tests at the same time, as I've started learning. I've like to pair program
with Andy on this.
Quiz 2: Has the team member finished her report to the team?
Yes A. No. She did not report her impediments yet.
No B. Yes. She said when she did yesterday, and what she will do today. She even showed us how they relate to the Sprint goals on the taskboard.
ScrumMaster: You forgot to answer the third question! Tell us whether you have any impediments.
Team Member 1: I was just getting to that. I'm uncertain whether the automated tests should go all the way to the database tables written by the legacy
system, or if I should just use mock objects.
Team Member 2: I've got some ideas about that. I'll work with you on it.
Quiz 3: Team member
Test Driven Development (TDD) involves creating tests and code nearly simultaneously, while constantly improving the design. Many Agile
developersdevelopers believe TDD helps ensure correct implementation while reducing the cost of change. Id TDD part of Scrum.
No A. Yes. Scrum is a complete methodology containing everything you need to succeed.
Yes B. No Scrum is only a management framework. It does not specify particular technical practices.
Team Member 2: Wait a minute. our Product Owner isn't here.
ScrumMaster: Yes, today the product Owner is out sharing our product vision with the CEO.
TeamMember2: 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 Owner is the final arbiter of requirements questions.
Team Member 3: 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.
Team Member 1: Yeah! Plus if we can't function 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. Atleast our product can influence the CEO. Would you rather have clueless Clyde or Myopic Myron?
ScrumMaster: While the Product owner has an explicit role in the other meetings, Scrum's rules all the Product Owner to either attend, or not attend, the
daily scrum. as with Many issues, Scrum leaves this for the team to decide.
Team member1: Are we on topic for the daily Scrum
Team Member 2: No. probabily not. This should probably be a sidebar.
ScrumMaster; Let's keep a list of sidebar topics so whoevr's interested can discuss after the meeting.
SIDEBAR:
* Team agreement whether to require Product Owner at Daily Scrum
Quiz 4: ScrumMaster
Which is the timebox for the Daily Scrum Meeting?
No A. As long as necessary
No B. 1 hour
Yes C 15 mins
TeamMember 2:
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
stylesheet.
Team Member 3: I'll Pai program with you. We're still cleaning up the mess from the last time we wrote code without pair programming.
Team Member 2: 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.
Quiz5: Team member
Many people feel pair programming reduces errors and increases maintainability. What is pair programming?
Yes A. Two people share one workstation, typically taking turns typing while others pay attention and helps.
No B. One person checks in code so another person can review it later, leaving a clear audit trail to the 'single wringable nect' when errors are discovered.
No. C. Code is wtritten two lines at a time to reduce errors.
TeamMember 3: Ok 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 (TDD). As you all know, that includes writing few lines of failing test code, then writing few lines of the product code, then
refactoring to improve the design without changing behavior and then we did the whole process again.
Failing Tests
Write tests ->Write Product Code -> Refactor code -> Write tests
Team Member 4: 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 the database
contention.
Today I 'd like to keep working on this if it's OK with you guys.
I do have one impediment today: I have to leave work early to get my dad from the airport.
Team Member 5: Hi Team. As Carla Said, I spent most of yesterday pair programming with her on the Update Grade PBI. As a traditional tester, I'm not
very familiar with programming. But since Carla was describing her thoughts as writing the code, I 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 code so we could refactor it.
Today I want to keep working 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 the Scrum team. Sometime I need to retreat
to my old office to take a break.
Team Member 6: Ok team. What I did, What I will do, and what impedes me. Yesterday I got our new continuous Integration server running. It reruns all
the tests everytime we make a code change and alert us instantly about regression failures.
Today I plan to plug our old tests into our new continuous Integration process.
Hey, where is Eddie anyway? Eddie's in space-time continuum.
Eddie: Hi guys, sorry I'm late again. Did I miss anything?
Quiz 6:
Other than Eddie, who is responsible for the integeity of Eddie's agreements with his team?
Yes A. The team, and the ScrumMaster must help create the circumstances for the team to take this responsibility. This may include techniques such as
nudging people and modeling behavior.
No B. The ScrumMaster, The ScrumMaster manages the team.
No C. The product Owner. The product owner is in charge.
Team member: Eddie, I know you were up all night working on the build file by yourself, and you probably thinks this speeds us up. But, we see product
development primarily as knowledge creation, not just construction.When you work in isolations and miss meetings like this one, it actually slows us down
in the long run.
Let's talk about this offline, in another sidebar. I'll try to mediate.
ScrumMaster: We've got some sidebar topics here that some of you want to stay and talk about afterwards.
The daily Scrum is over.
Quiz 7.
The daily Scrum is one technique to encourage team collaboration. Which physical arrangement encourages collaboration the most?
Yes A. Standing in an unobstructed circle, without laptops or phones.
No B. In a typical conference room, with large comfortible chairs encouraging people to stay longer.
No C. In a typical classroom set up, with all chairs facing the front of the room.
Quiz 8.
What is a good size for a Sprint task?
No A. 2-3 people 2-3 days, so that every Product Backlog Item equals one Sprint Task.
Yes B. One person day or less, so other team members can easily defect when a task is stuck.
Quiz 9
During Sprint Execution, a Scrum Team uses 'information radiators' such as the taskboard or sometimes Sprint Burndown Chart. Who are these for?
Yes A. The team, so they can take responsibility for their own work habits.
No B. Outside managers, so they can intervene as soon as they don't like how a Sprint is going.
Quiz 10
Martin Fowler's book refactoring: Improving the Design of Existing Code helped popularize the term "refactoring". The term is often misused. What does
this term mean when applied to source code?
Yes A. Improving internal structure only e.g. removing duplicate code.
No B. Improving functional behavioronly, e.g. fixing bugs
No C. Improving both internal structure and functional behavior.
Quiz 11
Some scrum team fully embrace Agile technical practices. How often do these teams integrate their work and rerun the regression tests?
Yes A. Continuously as things change; potentially many times per day
No B. Once per day ( or night)
No C. Only at the end of each Sprint
Quiz 12
When is Sprint execution completed?
No A. When all tasks are complete.
No. B. It depends
Yes. C. When the timebox expires.
No. When all committed Product backlog Items meet their definition of "done"
No comments:
Post a Comment