Willy's Reflections

| Willy-Peter Schaub | Visual Studio ALM Rangers | In search of IT simplicity, quality and tranquility |

Ruck is not another process, it is simply “loose Scrum” … in the context of the ALM Rangers

Ruck is not another process, it is simply “loose Scrum” … in the context of the ALM Rangers

Rate This
  • Comments 2

We recently ran a “quick poll” with the Rangers asking what they thought of Ruck. The results are interesting and worth sharing:

  1. 78% of the Rangers were happy with Ruck.
  2. No-one selected three of the “alarm bell” options.
  3. 22% selected three of the options which sparked this blog post and raised comments highlighted in red below.

image

survey comments

Here are comments that were submitted as part of the poll, listed “as is”:

  1. I really like Facts & Tables - couldn´t we have one called "Ruck Vs. Scrum"? Just with the differences in a very easy way for all the scrum-knowing teams out there?
  2. My experience is that it works well (=lightweight) but requires a visible ruck master to help the PL/team to stay on track.
  3. I haven't really seen anything about this 'methodology' that couldn't be achieved using Scrum.
  4. As a newbie Ranger I have at times felt that there's been too much flexibility, to the point where I've felt uncertain what to do. Obviously the solution is to communicate with your team, PL and Ruck Master but this might not always happen if the new Ranger is afraid to show 'just' how new he/she is ;-) This is just the classic need for additional attention placed on new people in a group, but I wanted to surface it for consideration.
  5. I'm still learning about Ruck, but my main question is: why did we create a new process? What problem does it solve that isn't already addressed by Scrum?
  6. Love it. It is simple and straight forward - Lightweight, which is perfect for distributed teams.
  7. For the teams that I've been involved with that use it, it seems to be working out just fine.
  8. Great guidance Brian! Keep up the phenomenal mentorship and sharing of best practices. You are a "rocking" STAR!

quick responses to some of the comments

Hopefully by reading the Ruck Guide, the related publications (see below) and most importantly by attending one of Brian’s regular and “phenomenal” talks, we can tick off 3 and 5.

We ask all Rangers to review the Ruck Guide, work with their peer mentor and not be afraid to ask anything. Remember that the only *silly* question is the one that was never asked!

ruck != process

Fortunately only one comments mentions “process”, but we have heard the question “why another process” many times. Ruck is not  a new process! In fact we spoke about “Scrum” until we had numerous heated discussions with subject matter experts who argued that we were breaking all types Scrum rules and that we should not be calling it Scrum. To avoid interesting, but time and energy consuming debates, we started saying “loose Scrum” and eventually “Ruck”, as maul or ruck implies loose Scrum in Rugby. See What is a loose scrum in rugby called .

 … whenever the word “zealot” pops up in heated debates,  I think of the lower-ranked Starkraft Templars Smile

Brian’s session: being Agile … Scrum … teams are not collocated and not dedicated

Brian Blackman has been running information sharing sessions, also known as RangerTalks or brown bags, sharing the learning’s of mentoring projects in the often challenging Ranger project team environments. Let’s share a few of his slides …

Slide8 Brian emphasises that we are working with and respecting the manifesto for Agile software development. See Manifesto for Agile Software Development.
Slide9 Important Scrum basics that need to be understood, before we proceed.  

Peruse the many invaluable posts by
Martin Hinshelwood, for example You are doing Scrum but the Scrum Master tells the team what to do for more insight into Scrum.
Slide7

This is where the reality, or the rubber hits the road.

Consider a team X consisting of 9 volunteers located in Canada, East US, West US, South-Africa, Japan, Germany and Australia. Every team member has a day-time (real) job and a family, resulting in very limited and non-guaranteed (committed) bandwidth. Most team members use English as their mother-tongue and we have a mix of traditions, and cultures that need to be considered.

  • How easy will it be to schedule and meet daily 15min scrum?
  • How easy will it be to meet as a team for sprint planning, review and retrospectives?
  • How easy will it be to establish a cadence?
Slide10 The pictures speak a thousand words Smile
Slide11Slide12

While our cheat sheet poster looks like Scrum, there are distinct realities, tweaks and “loose” implementations of Scrum:

  • As with Scrum we have a PO who owns the backlog and the team works in sprints, each delivering a potentially shippable product and each ending with a review and retrospective. So far so good.
  • This is where we start deviating from Scrum basics, which you will appreciate if you are involved in similar community projects or have ever tried to schedule a series of regular meetings with team X as above.
    • We schedule weekly scrums, with the use of email and video recording to share progress.
    • We refine and prune the plan and associated backlogs weekly, pro-actively embracing distractions due to day-time jobs and families.
      family > job > rangers! 
    • We perform planning, review and retrospective meetings using a combination of email, teleconferencing and messaging.
    • We often tolerate less than ideal burn-downs.

So to get back to the question “why are we not using Scrum?”

Well, we are using Scrum, but loosely!

related publications

We would appreciate your candid feedback!

  • How long are typical sprints in Ruck, if you're stand-ups occur weekly instead of daily?

  • @Matt, we typically work with calendar month sprints. We experimented with 2-week sprints and >1 month sprints, but found that there was an overhead with the former and a sense of non-urgency introduced with the latter. A monthly pulse seems natural and we obviously limit the objectives and deliverables due to part-time availability.

Page 1 of 1 (2 items)
Leave a Comment
  • Please add 7 and 8 and type the answer here:
  • Post