Jeffrey Palermo (.com)

Do ScrumMasters still code?  I've asked this discussion with a few ScrumMasters and typically get different answers...depending on whether the person asked was a former PM or former lead developer.

Whats the method that has worked for you? Can you still knock out items off the Backlog while still playing the traditional scrum master role?

Thanks for expanding on that.  I really think Scrum sounds like a great methodology to follow, but I'm still trying to understand how best to utilize it in my environment.

Where do you draw the line between coaching and contributing?  

From what I understand, a Scrum Master is to remain a neutral party between the Team and the Product Owner.  Is there potential for a conflict of interest if the Scrum Master is also responsible for the team's items on the backlog?  Should a Scrum Master even be assigned tasks from the backlog?  

@Karthik,

I don't try to draw a line between coaching and contributing.  

Regarding conflict of interest:  This is only a concern on a dysfunctional team.  If you have an "us" versus "them" environment, you are dealing with unnecessary friction.  Your customer/product owner needs to be part of the overall team.  You should all be working together to produce software.  You shouldn't be working against the product owner, but with.

A conflict of interest occurs when there are two parties with separate priorities.  In this case, there should be one goal, one set of priorities.  Everyone should be concerned with producing software that benefits the business.  That's it.

>"tasks from the backlong?"

That's a process question, and there is no answer that works for every organization.  First, tasks should not be on the backlog, only stories.  Difference:  stories make sense and are verifiable by the product owner.  Tasks can be anything and can't be verified.  For instance:  "Drop an ununsed table in the database" is a task and has no business on the backlog.  The Product Owner can't use the app and verify this.  It doesn't bring direct value to the business.  It's not user-centric.  It needs to be done, but it's not  backlog item the Product Owner should have to worry about tracking.

For my current client, I have both helped with analysis/wire frame diagrams, development, and testing.  I coach and contribute to every part of it.  

FYI: I know the guy giving the training. He's really a great guy and sharp and knows a lot about the subject. You'll be in good hands!

My experience with being a ScrumMaster is it tends to be a full time job.  If you are a contributor as a ScrumMaster, then you are more of helper than someone working on a critical path items.

I'm a certified scrum master and developer and from my experience it's about 70% code, 30% facilitation.  

The team size ranges from 4 to 8.  Most people do not have experience with Scrum and their experience with the language is mixed; lots of C++, but little c# (unfortunately, that is the direction all the code is migrating).  All the systems are legacy systems.  The whole organization is transitioning from waterfall to "something" more agile.