Scrum Development Blog

Better teams make better products.

Archive for the ‘Scrum Questions’ Category

Team Rhythms and Noise

Scrum Questions | Posted by doug.shimp
Feb 07 2011

quiet scrum teamsScrum makes an assumption that you have a dedicated team who can focus on something for a sustained period of time. Most highly cognitive products require sustained focus and a consistent team rhythm.

Teams tend to get into a common rhythm in which quiet time andscrum rhythmsnoisy time are synced so that team members don’t bother each other very much. People whose work is disconnected have different rhythms. Noise is a real problem when you’re trying to do something that is highly cogitative.  So protecting the team from out-of-sync noise can be very important.

Questions

How do you protect teams from out-of-sync noise?

One might expect that surrounding an entire team with some noise protection (walls or space) would be sufficient. Does that work?

It shouldn’t be important to protect team members from each other’s noise. Do you agree?

What have you observed? What has worked in the past?

Is there a demographic shift between older and younger?

Should I Take Advanced or Beginner Agile Training?

Scrum Questions | Posted by The 3Back Team
Oct 21 2010

Agile / Scrum Training should cover the fundamentals in every course. Agility is a deep practice that requires years of effort to master and maintain mastery. The fundamentals are the underpinnings that enable a practitioner to manifest deep applied skill and technique in the face of day to day complex work.

We are regularly asked questions like the following section in green.

fundamentals of agility

We would like to sign up a group of people that do have some working knowledge of SCRUM. They are currently in the Product Owner, ScrumMaster or Team role.Is your course advanced enough to give us value or is it meant more for beginners?  We want to know more about how to properly create and manage our stories, prioritize, etc….do our jobs better and more effectively…but we already do understand the high level scrum process.

Our response typically goes something like …

The difference between advanced and beginners is a concept that we work to break down as follows. By asking for advanced or beginner agile training you are already driving thought in an unnecessary and limiting way, which is not agile! Agile training should always cover the fundamentals, which never go away and you will always need to work on. So an agile course should hit the fundamentals of agility and exploring agility using a Scrum Framework (or other agile method). The course should be built and driven by an experienced practitioner that also trains. Experienced practitioners should be able to coach as well as train so that the deep skills of agility are manifested and show up in practice. Our curriculum is designed to bring out the deep practice of Scrum as it relates to the Product Owner, ScrumMaster or Team role and help the practitioner pick up real skills / techniques that they can put to valued use. Our course is not about basic scrum mechanics / process.

Our goal with this post is to raise awareness that Agile / Scrum is a practice that requires agility for mastery. An agile pathway is needed to produce individuals with real skills that join teams that can enable real agility within an organization. Agile well formed teams are the key for product development and innovation within organizations.

When you look for agile training, look for training that comes from fundamentals.

Should we adjust the time box in Scrum?

Scrum Questions | Posted by The 3Back Team
May 19 2010
Pick one:
  1. Yes, it is ok, the team needs to be managed by the Scrum Master who decides when to adjust.
  2. Yes, if the Product Owner approves
  3. No, use the time box to help detect when things are not well understood and where clarity is needed. Time boxes bring rhythm
  4. Sometimes, if the Product Owner and Scrum Master agree

scrum timeboxtime box is a common practice underlying most agile processes especially, Scrum. Time boxing is a the closest thing in agile or scrum that we have to something that is clearly a best practice. Most managers or early adopters of Scrum wonder what they do to create a sense of urgency and the answer is simple “Time Box”.

In Scrum we have 6 formal timeboxes.

  1. Release Planning
  2. Sprint Planning
  3. Sprint
  4. Daily Standup
  5. Sprint Review
  6. Sprint Retrospective

Time boxes are a key element in Scrum. They form the a bases for how we manage the team’s energy. The general rule in using time boxes is to not adjust the time once you have set it. When the clock runs out the bell “dings” and things change.

#1 mistake those new to Scrum make is to adjust the sprint length to give the team more time to complete their work. Basic Scrum training should cover and provide an in depth explanation of why not to adjust the time box.

How do you keep your ScrumMaster certification active?

Scrum Questions | Posted by The 3Back Team
May 06 2010

Hi Joe ScrumMaster,

To keep your profile active you need to review the guidelines here.

http://www.scrumalliance.org/CSM

The Scrum Alliance has recently ascrummaster scrum master roledded/modified its existing program for CSP Certified Scrum Professional and you could look at applying for that if you have been using Scrum.

- Scrum Coach

On 04/30/10 10:05 PM, Joe ScrumMaster wrote:
——————–
Hello Scrum Coach,

I took your ScrumMaster course last May. What, if anything, do I need to do to keep my ScrumMaster certification active?

Thanks,
Joe Scrum Master

Should Retrospective Notes be Publically Posted

Scrum Questions | Posted by The 3Back Team
May 05 2010

scrum questionsBelow is a conversation between Joe ScrumMaster and Scrum Coach.

——————————————————————–
On Fri, Apr 30, 2010 at 7:21 AM, Joe ScrumMaster wrote:
Hi Scrum Coach,
I have question for you regarding the Sprint Retrospective. Should the notes a ScrumMaster take during this meeting be publically posted for interested folks to read?
Thanks,
Joe Scrum Master

——————————————————————–

Hi Joe Scrum Master,
Good to hear from you.
I would be careful with this kind of information. Focus instead on what scrum goals came out of the team meeting. Sensitive conversations need to be handled gingerly. Some of them can blow up into an HR issue. If it were me I would like an opportunity to get better without being public-ally embarrassed. As long as you (ScrumMaster) see a movement to improve then let people improve with grace.
Focus on team goals and key learnings. It is not a data thing. We are dealing with a system of people and the message matters.
All of the observations a ScrumMaster might take should not be made public.
Hope that helps.
- Scrum Coach
Do you agree?

What is the basic building block in applied Scrum?

Scrum Questions | Posted by The 3Back Team
Apr 13 2010

What is the basic building block in applied Scrum?

Choose:basic scrum team building block

  1. Team
  2. Individuals
  3. Practices
  4. Scrum Team
  5. Scrum Framework

The Scrum Team is self organizing, self managed, cross functional and self aware. Organizations using scrum rely on the basic building block of a Scrum Team to understand how to it can be applied in their context. There is an assumption here that the team exists for some purpose and they have been assembled. So the team is not self assembling. The Scrum Team figures out how to do its work, manages itself to do the job, has all the skills necessary to get the job done and uses its values to deepen its understanding of self to perform better as a well formed team.

Forces on Quality

Scrum Questions | Posted by The 3Back Team
Apr 12 2010

quality forcesDo I want any force that causes quality to go down?

New to Scrum? Find more questions by reading our Scrum FAQ

When is a requirement truly required?

Scrum Questions | Posted by The 3Back Team
Feb 12 2010

Choose

  1. The development team creates a spec.desirements requirements acceptance test
  2. The Product Owner says it is.
  3. The business asks for it.
  4. There is a test which actually requires it to be there and fails when it is not.

Comment: We often find ourselves lost in the desirements trying to find the real requirements for our system. Those things which seem required often end up being only desired. The word requirement has suffered more from confusion and misuse than just about any other word in the IT lexicon of development. What is a “nice to have” requirement? I mean really! I have close to 20 years of experience in the industry including training and writing requirements. Even with all of that experience the word still makes me a little crazy. I like the word desirement because of it’s contrast with requirement. When there is a test that makes it required with a pass/fail then it is a requirement, until then it’s just a a desirement.

So, a more interesting question is …. When is a requirement truly required?

When are you ready for sprint planning?

Scrum Questions | Posted by The 3Back Team
Feb 10 2010

Choose:

  1. The PO says go.ready set go sprint
  2. The Teams says they are ready.
  3. The SM has determined a time box for the sprint.
  4. The team and PO agree to a time box
  5. The PO understands and is prepared to talk about the stories

Comment: There are a number of things you should do before you can even begin planning.  The most important thing you can do is make sure that your Product Owner is prepared, and understands what the stories are about.  Remember that the Product Owner is a role here, so what we’re actually saying is that someone on the Team knows about each story; that is, each story has its own champion (Story Owner) who represents the Stakeholder’s needs/wants to the Team. This may require that the Product Owner (person) coordinates the

How do you fill a sprint?

Scrum Questions | Posted by The 3Back Team
Feb 08 2010
  1. You get past work experience. And calculate the amount of work the team can handlestory fill sprint epic too big
  2. Get estimates from the team and double the number they give you to determine work load.
  3. Meet with each individual and see how much work they can take on. Build a sprint plan from that information. Then gather everyone, show the sprint plan and kickoff the team sprint.
  4. Use the PO/SM powers to challenge the team to take big bites. Get as much loaded in the sprint as possible. The PO/SM can form a powerful pincer to overcome resistance.
  5. This is sprint planning.  You commit one story at a time. Make sure the team is committing to sharp definitions of done.

Comment: After a Story is committed to, the Team (with the PO in the lead) has the option to reprioritize the Story list, and the Team takes the next one to consider. Once again, the Team comes to the “doneness” Agreement and commits to adding the Story to the list of already-committed-to Stories. This process is repeated until the Sprint is “full” and the Sprint Plan is complete.