Transitioning from QA Analyst to Scrum Master

I had another great question from someone on LinkedIn and I thought I’d share it and my answer here.

I would like advice on career advancement in Software Development and becoming a Scrum Master. Currently, I am a QA analyst and was wondering is it a smooth transition for someone with that skill set?

Congratulations on wanting to become a Scrum Master! Yes, I think it would be a relatively smooth transition for a QA Analyst to become a Scrum Master. I’ve actually seen several QAs become Scrum Masters and several Scrum Masters take on the extra duties of QA to assist the team when they need it.

As a QA Analyst, I’ll presume you’re one of the last steps in the development process before things are approved to merge into the master branch and/or deploy to production. As you’re already the final say in the definition of the task being done, it’s not a big step towards helping the team adhere to their overall Definition of Done.

You also already have a solid set of skills with creating and following a test plan. That easily expands to following the Scrum process and helping to enforce it both in the team as well as with the product owners. The hardest part (in my opinion) is keeping the external influences at bay to allow the team to focus on their current Sprint.

The hardest part of your transition is probably going to be actually getting the job. The easiest way would be to try and move within your current company. You already know your way around, and they know you (which is hopefully a good thing on both sides!) If there’s another Scrum Master there, pair up with them, learn from them, and ultimately get a team of your own to work with.

A brief side note: Many organizations now I’m finding are starting to merge the Scrum Master in with a Project Management role. They think that they can have one person do all of it. Sometimes you can, but most times I think it’s best to have these roles separate.

While you’re doing all that, I’d look into becoming a Certified Scrum Master. It’s usually a two-day class and it covers everything you’ll need to get your feet wet. From there try practicing Scrum on some small projects at home. It’s a little unusual to clean your house using Scrum, but it will help you see how to break the tasks down as well as estimate times and determine what Done means. Then on your interviews, while you may be “green”, you can discuss how you’ve been utilizing it in areas other than IT. It shows that you have a clear understanding of how to utilize Scrum processes in any scenario. The best and worst thing I ever did was teach my wife Scrum…

I hope that helps some and I haven’t rambled too badly. If you have any other questions, don’t hesitate to reach out to me.

How Important is a Degree?

I was recently contacted on LinkedIn by someone looking for advice and they had a very good question.

I was wondering how important is it to have a degree from a distinguished college in the field of IT?

The importance of a degree is somewhat up in the air. I personally don’t have a degree in any software or IT field. However I do have a Masters in Electrical Engineering and a Bachelors in Physics, so there is at least the assumed logic solving abilities in that combination.

There’s really three levels on this, and it all depends on the employer and hiring manager:

  • I have found that some places will place emphasis on having a specific degree as they are literally looking to check off as many boxes as they can for a candidate check list and only interview those who fit 90-100% of the criteria.
  • Other companies look at if you have a any type of degree coupled with some experience. The thought there is that any 4 year degree gives you some credibility in to completing a long term commitment (and that you’ll be willing to stay with the company for several years as opposed to jumping ship 8 months in to the job).
  • Still other places, and more so with start ups, degrees don’t mean much. It’s all about experience coupled with willingness to learn. Many places would be willing to consider a junior level position to someone who has just completed a coding boot camp and has a good recommendation from the instructor. I’ve taught a few boot camps, and have seen some students get placed in entry level roles after they completed the course. Keep in mind though, at least here in Dallas most of them took 3-6 months to find something.

Usually talking with the recruiter or HR at the hiring company you can get an idea as to how critical the degree is for the role and which of the three categories above the employer falls in.

Don’t let the lack of a degree stop you from wanting to enter the IT industry. Start going to meet ups in your area which are over topics that you’re interested it. Learn what you can from them and network with the people there. Odds are you’ll find someone who is willing to help mentor you some and help you learn more about the topics you’re interested in. Apply to entry level roles and highlight your self-study. You never know when or how that initial opportunity will come.

Questioning the Boss: Challenge to Authority or Collaboration Opportunity?

I recently was declined for a job interview. Not because I wasn’t qualified, but because one of the managers turned out to be a manager that I had worked with in the past, and they felt that I would not be a good fit for their team. They didn’t think I’d be a team player.

You see, back when we worked together, I questioned him.

A lot.

I questioned everything from task prioritization (shouldn’t the ability to login and have user roles be ahead of 90% of the heavy work we need to do which is role based and not three months down the road?), to team selection (why are we putting PHP developers on a Ruby on Rails project when we have enough Ruby developers to spare?), to just about anything else you can think of. Yes, I challenged some of it because I really did think they were poor choices, and I didn’t want to be held accountable to an impossible delivery schedule. However, the majority of it I challenged and questioned because I wanted to learn more, and at the same time I wanted to share my knowledge and experience with him.

The manager saw my questions as challenges to their authority; a lack of respect. Where I thought I was being a collaborative team player, I was being seen as a trouble maker. A subversive employee whose goal was to make the manager look bad, and promote their own self-interest. I tried changing tactics to ask questions in email and in private meetings as opposed to in large meetings in front of their peers and subordinates. Unfortunately, by that time, I was still deemed a threat.

My wife was recently in a situation where a new manager came into her company.  My wife has been there for nearly 20 years, and rather than take the questions she was asking as guidance, the manager took it as a challenge.

A good manager knows that not only should they surround themselves with people smarter than they are, but they need to utilize them. My wife’s situation is a perfect example of that… someone who is new to a company should want to leverage the knowledge of someone who has been there for a long time. You cannot become a truly effective manager without fully leveraging your team and their abilities. Some of these “smart” people will have very specialized knowledge. Others will have a broad knowledge base to draw from, or they always look at the problem from a different angle. A good manager fills out their team with people which will fit the gaps in their own knowledge and experience, as well as people with different viewpoints and problem solving skills. The total of their knowledge and experience will greatly exceed the sum of their parts with a wise manager leading the way.

If an employee comes to their manager with a question, particularly one regarding the current project, processes, or even staffing, the manager should listen and respond accordingly. Sure, sometimes it will just be an off the wall question, or just someone having a grouchy day. More often than not though, the question is an opportunity, not a threat. It could be an opportunity for the manager to help mentor the employee (help them see the bigger picture, not your view of how things “should be.”). It may be an opportunity for the manager to learn something new (especially with new technologies and tools which could speed up development or delivery time).

The CTO for the company where this manager and I worked had a habit of sitting back in meetings and listening, and then just asking one question.  Granted, it was one question that sparked a series of other questions by the team.  He didn’t point out the holes, or the flaws in the plan, or come across as challenging the process – instead he simply would ask “Why? How? When?” I admired his ability to spark discussion and his openness to listen to questions from the team.  He encouraged questions, and I asked him a lot of questions.  He would constantly tell me, “You’re not asking the right question.”

Returning to my prior blog post about Who Owns the Scene, I want to elaborate on why asking questions should be taken as a compliment, and not a challenge by a manager. When people ask another individual questions, it’s generally because they want to gain something from them – besides the answer. It could be, as I’ve pointed out already, to learn something new, or to understand a process – both physical and mental. Through asking my brother-in-law questions about who owns the scene at an accident, I learned more about the processes and regulations that are behind law enforcement. He not only got to “show off” his knowledge, but he gained a bit about IT processes in the conversation. Amusingly, both of us sat down with my father-in-law to ask questions of him due to his expertise. My brother-in-law needed to understand some accounting rules as he was reconciling the books for the fire department, and I needed to understand some tax law implications as I was working on a project to try and compute tax depreciation differently. Through the conversation, I learned what I needed and more, as did everyone else sitting around with dessert and coffee. While my mother-in-law was a little bored, she made comments, which made us think differently.

If it’s the right question (you’ll know it when you hear it every time), then it gets both the manager and the employee (or the team, or in the prior example, my family) collaborating together. This results in a better understanding of the issue from all sides, and a solution which now has full buy in from all parties. If that collaboration isn’t a win for the company, then I don’t know what is a win.

I guess being shot down for an interview by a former coworker in a new company (at least this ex-colleague in particular) isn’t such a bad thing after all. Once I found out that I would have been working with him I probably would have thought long and hard about whether or not I should accept the position. The question would be, can I work with someone who is not open to questions? Can I accept that by asking questions I could be seen as difficult? Again, my intent is not to make my manager look bad, whether it’s a line manager, the CTO, or even the CEO when I reported to one. The intent has been, and always will be, to learn and ensure the project is successful.

What do you think? What is the right question to ask to make a project, manager, or employee successful?