Junilu Lacar wrote:making sure that team members are not doing any "hidden" work that's not related to the sprint goals.
Junilu Lacar wrote:An astute Scrum Master can point out when code reviews are happening later than when they are most effective, which is what typically happens when teams don't collaborate and do things like TDD/BDD. The Scrum Master can point out these types of waste and coach the team or find a coach to help them adopt TDD/BDD and other practices that make code reviews more timely and effective.
Satyaprakash Joshii wrote:
Jeanne Boyarsky wrote: and make adjustments as needed.
Adjustments like ?
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Satyaprakash Joshii wrote:
Junilu Lacar wrote:An astute Scrum Master can point out when code reviews are happening later than when they are most effective, which is what typically happens when teams don't collaborate and do things like TDD/BDD. The Scrum Master can point out these types of waste and coach the team or find a coach to help them adopt TDD/BDD and other practices that make code reviews more timely and effective.
Yes. I understand. I think also there may be time when scrum master would help a developer decide on the priority in case he has multiple things at one time.
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Satyaprakash Joshii wrote:
Jeanne Boyarsky wrote:I invest in coaching new people on how to communicate better.
Could you please share what communicate better means to you. Hearing this from you would be valuable.
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:
"Yesterday I started coding the rest api and today I plan to continue to rest api." So... you did work? That conveys nothing.
Jeanne Boyarsky wrote:
It's done, except... - so it's NOT in fact done. If there's a but/except, that means it isn't done
Jeanne Boyarsky wrote:
People obviously not paying attention - this is harder to do remotely
Satyaprakash Joshii wrote:Thank You
Jeanne Boyarsky wrote:
"Yesterday I started coding the rest api and today I plan to continue to rest api." So... you did work? That conveys nothing.
Instead of this is it better to say as Yesterday, I created application for REST APIs and added controller class. Today, I will add the implementation for methods in the controller?
Satyaprakash Joshii wrote:
Jeanne Boyarsky wrote:
It's done, except... - so it's NOT in fact done. If there's a but/except, that means it isn't done
When something is almost complete , is it acceptable to say ..I have done a,b,c,d,e and once f is done, this user story will be complete.
Satyaprakash Joshii wrote:
Jeanne Boyarsky wrote:
People obviously not paying attention - this is harder to do remotely
I have seen this practically happening. why because developers are consolidating thoughts in their mind for the time when their turn comes to speak.Not just developers any humans if they are to speak one by one on any simple thing when their turn comes, focus on consolidating their thoughts and lose focus of what others are speaking.It happens with me too to some extent.
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:
Tip. Write down what you want to say. On a post it in person or in notepad on your computer. Then you don't have to worry about forgetting it and can focus on your teammates
Satyaprakash Joshii wrote:It is not just about focus but sometimes people get into a mindset that all one is doing is wait for our turn. Not just with developers ,I think that's human tendency.
That mindset has to change.
Jeanne Boyarsky wrote:Sometimes the SM is the one to note that Sally is waiting on Katie to give her some information to unblock a task.
Junilu Lacar wrote:it's not a status meeting, it's a planning meeting. The team should come away from the standup with a clear idea of what they're going to do for the rest of the day.
Satyaprakash Joshii wrote:In that case instead of saying what one plans to do today, should one say how one plans to do that today ?
Junilu Lacar wrote: Good communication results in shared understanding. Poor communication results in misunderstanding.
Jeanne Boyarsky wrote:
The first two mean I'm not going to get as much work done as I hoped. However, the team can probably adjust and meet the sprint goal (if nothing else goes wrong.)
Satyaprakash Joshii wrote:
Jeanne Boyarsky wrote:Sometimes the SM is the one to note that Sally is waiting on Katie to give her some information to unblock a task.
Yes. Although SM would help do this, Sallly should also consider it as her responsibility to speak up if she is waiting for something from Katie.
nThe first two were my smaller examples where it is possible to recover. The team (should) be calculating velocity based on past sprints and availability. On average, there's a certain amount that goes wrong each sprint. In particular, you shouldn't be planning to 100%. My team has a lot of variation because we are a DevOps team. What we do every sprint (at sprint planning) is identify some "below the line" tasks. These are the tasks that it would be nice if we get done but don't go against the sprint goal or commitment. If we have less user/prod support and/or tasks go smoothly, we do those. If not, no worries. That's our team deals with our reality. Other teams I'm sure have other approaches.Satyaprakash Joshii wrote:
Jeanne Boyarsky wrote:
The first two mean I'm not going to get as much work done as I hoped. However, the team can probably adjust and meet the sprint goal (if nothing else goes wrong.)
How would the team meet the sprint goal in such cases ?
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Satyaprakash Joshii wrote:Thank You. Also as shown in this example it doesn't necessarily be that one by one everyone has to speak on their turn.It can be random and dynamic as in this.
Satyaprakash Joshii wrote:Thank You. Also as shown in this example it doesn't necessarily be that one by one everyone has to speak on their turn.It can be random and dynamic as in this.
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:I wonder what about the standup makes it a nervous experience. It should be just as comfortable as talking to your teammates. And hopefully you aren't nervous with them when working on stuff.
Jeanne Boyarsky wrote:
Tip. Write down what you want to say. On a post it in person or in notepad on your computer. Then you don't have to worry about forgetting it and can focus on your teammates
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:And if the anxiety is about speaking in general (vs the meeting), I recommend Toastmasters to get more comfortable presenting both formally and informally.
Junilu Lacar wrote: Talking during a standup should be no more nerve-racking than telling your mom what you did in school today
Jeanne Boyarsky wrote:
Tip. Write down what you want to say. On a post it in person or in notepad on your computer. Then you don't have to worry about forgetting it and can focus on your teammates
It wasn't my idea to go to some crazy nightclub in the middle of nowhere. I just wanted to stay home and cuddle with this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|