Your SlideShare is downloading. ×
0
10 Questions   for your  Scrum Master  Interview David J Bland  [email_address]
<ul><li>Agile / Scrum Job Data </li></ul>
<ul><li>Interview  </li></ul><ul><li>your  </li></ul><ul><li>Interviewer </li></ul>Just how Agile is this position?
<ul><li>Question #1   </li></ul><ul><li>Can you describe </li></ul><ul><li>your iterations? </li></ul>(Agile) – 2 weeks ma...
<ul><li>Question #2   </li></ul><ul><li>What is the team  </li></ul><ul><li>size & make up? </li></ul>(Agile) – Small & cr...
<ul><li>Question #3 </li></ul><ul><li>Are Product Owners </li></ul><ul><li>available for Q&A?   </li></ul>(Agile) – Yes & ...
<ul><li>Question #4   </li></ul><ul><li>Can you explain your </li></ul><ul><li>code deployments? </li></ul>(Agile) – Autom...
<ul><li>Question #5 </li></ul><ul><li>Do you practice Test </li></ul><ul><li>Driven Development?   </li></ul>(Agile) – Yes...
<ul><li>Question #6   </li></ul><ul><li>Can you describe  </li></ul><ul><li>your requirements </li></ul><ul><li>documentat...
<ul><li>Question #7   </li></ul><ul><li>How do you use </li></ul><ul><li>project metrics?   </li></ul>(Agile) – Story Poin...
<ul><li>Question #8   </li></ul><ul><li>How often do your </li></ul><ul><li>teams meet? </li></ul>(Agile) – Daily Stand Up...
<ul><li>Question #9   </li></ul><ul><li>Do you have executive </li></ul><ul><li>buy-in for Agile? </li></ul>(Agile) – Yes ...
<ul><li>Question #10  </li></ul><ul><li>Can you explain other </li></ul><ul><li>responsibilities for the </li></ul><ul><li...
Good luck future  Scrum Masters! David J Bland  [email_address]
Upcoming SlideShare
Loading in...5
×

10 Questions For Your Scrum Master Interview

51,867

Published on

My Slide Deck presentation for the popular 10 Questions for your Scrum Master Interview Tips as published on InfoQ.

Published in: Technology, Business
8 Comments
24 Likes
Statistics
Notes
  • Hilarious! Seen it happening.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • These questions and answers give you the chance to evaluate the level of scrum methodology adoption and understanding of your future employer (or the interviewer). You may see as opportunities if they responded poorly as you can potentially be the champion and making your presence felt. nice!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • No offense taken.

    This is a litmus test to determine where they are with Agile, and for a newbie Scrum Master you may not want to jump into an Agile transformation head first.

    If you are up for some heavy transformation work as a consultant, the red flags may actually entice you :)
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hi David,

    No offense intended, but:

    Your 'green' answers desrcibe how I would like my client to be when I leave - so why should I start there in the first place if he's already there?
    Or is the idea to use the questions only for possible employments (in contrast to contracted consulting) to rule out the challenging ones?

    Or did I get something wrong?

    Michael Mahlberg
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Like it, short, sweet and full useful information, thank you
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
51,867
On Slideshare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
1,057
Comments
8
Likes
24
Embeds 0
No embeds

No notes for slide
  • Indeed.com job trend data can be found: http://www.indeed.com/jobtrends Google.com search volume data can be found: http://google.com/trends
  • You need to ask precise questions to determine agility. The Interviewer may not offer up these insights with a bit of prodding from your side.
  • Ideally this is 2 weeks, but if it is close within reason it is a positive sign. Be wary of extremely long answers that slip into months, as these are not agile characteristics.
  • Small, cross functional teams are important. Take note of any answers that lean towards large silos of developers. You may also want to follow up on whether or not the team is distributed or co-located.
  • A non-existent Product Owner can wreak havoc on an agile team. This could be why the Scrum Master position is vacant!
  • It is difficult to remain true to the tenets of agile with a clunky batch process for code deployment. Try to pin them down on what tools they use here to prevent them from sidestepping the question.
  • Similar to CI above, TDD is another indicator of agility. Again try to find out the tool set they use for this process, as it will vary by technology stack.
  • There is no one perfect answer for this, but they should touch on small excerpts of functionality that are on a task board or in project management software. Lengthy SRS or functional specifications should raise a red flag.
  • Points or hours should be sufficient. I’d pay attention on whether or not their fibonnacci scale goes to extremes. Measuring actuals vs estimates can lead the conversation to some interesting areas. Try to determine whether or not actuals are used against team members.
  • This should be every day if you are playing the role of a true Scrum Master. This can be more challenging with distributed teams in different time zones.
  • Agile isn’t only bottom, it is also top down. Try to determine if the person selling you on this agile position actually has any say within the company.
  • Depending on the organization this can vary, but it is worth asking especially if they responsibilities do not interest you in the least. It is better to know about them now!
  • Transcript of "10 Questions For Your Scrum Master Interview"

    1. 1. 10 Questions for your Scrum Master Interview David J Bland [email_address]
    2. 2. <ul><li>Agile / Scrum Job Data </li></ul>
    3. 3. <ul><li>Interview </li></ul><ul><li>your </li></ul><ul><li>Interviewer </li></ul>Just how Agile is this position?
    4. 4. <ul><li>Question #1 </li></ul><ul><li>Can you describe </li></ul><ul><li>your iterations? </li></ul>(Agile) – 2 weeks max (Agile?) – Over 1 month (Red Flag!) – What’s an iteration?
    5. 5. <ul><li>Question #2 </li></ul><ul><li>What is the team </li></ul><ul><li>size & make up? </li></ul>(Agile) – Small & cross functional (Red Flag!) – 20+ members in vertical silos (Agile?) – Large but collaborative
    6. 6. <ul><li>Question #3 </li></ul><ul><li>Are Product Owners </li></ul><ul><li>available for Q&A? </li></ul>(Agile) – Yes & often (Agile?) – Yes about once a week (Red Flag!) – They weigh in after launch
    7. 7. <ul><li>Question #4 </li></ul><ul><li>Can you explain your </li></ul><ul><li>code deployments? </li></ul>(Agile) – Automated continuous integration (Agile?) – Frequent manual deployments (Red Flag!) – Very large, infrequent batches
    8. 8. <ul><li>Question #5 </li></ul><ul><li>Do you practice Test </li></ul><ul><li>Driven Development? </li></ul>(Agile) – Yes & Behavior Driven Development (Agile?) – Yes on the important bits (Red Flag!) – We have QA for testing
    9. 9. <ul><li>Question #6 </li></ul><ul><li>Can you describe </li></ul><ul><li>your requirements </li></ul><ul><li>documentation? </li></ul>(Agile) – User Stories with INVEST model (Agile?) – Small paragraphs of requirements (Red Flag!) – Large SRS documents
    10. 10. <ul><li>Question #7 </li></ul><ul><li>How do you use </li></ul><ul><li>project metrics? </li></ul>(Agile) – Story Points for Release Planning (Agile?) – We estimate most of our tasks (Red Flag!) – Only use MS Project with Gantt
    11. 11. <ul><li>Question #8 </li></ul><ul><li>How often do your </li></ul><ul><li>teams meet? </li></ul>(Agile) – Daily Stand Ups (Agile?) – A couple times a week (Red Flag!) – Only monthly status meetings
    12. 12. <ul><li>Question #9 </li></ul><ul><li>Do you have executive </li></ul><ul><li>buy-in for Agile? </li></ul>(Agile) – Yes and we’ve trained our teams (Agile?) – They suggested we try it out (Red Flag!) – My boss thinks it is a fad
    13. 13. <ul><li>Question #10 </li></ul><ul><li>Can you explain other </li></ul><ul><li>responsibilities for the </li></ul><ul><li>Scrum Master? </li></ul>(Agile) – Mentor, Tester, Coder, Designer (Agile?) – Also Project Manager (Red Flag!) – Also the Product Owner
    14. 14. Good luck future Scrum Masters! David J Bland [email_address]
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×