There comes a time in every developer's career when they have to decide what direction they want to go in. For many, this may mean becoming a manager of a software development team. In this course, we look at what it means to be a manager, and whether it is the right decision for you. If it is, then this course covers how to tackle your first 90 days in your new role, as well as some essential management and personal skills that you can use.
Stephen Haunts is an experienced Software Developer and Leader who has worked across multiple business domains including Computer Games, Finance, and Healthcare Retail and Distribution. Stephen has worked in languages ranging from Assembler, various forms of BASIC, to C and C++, and then finding his love of C# and .NET.
What Does It Mean to Be a Manager? Welcome back to this module for the Developer to Manager Course. My name is Stephen Haunts. In this module we'll look at what it means to be a manager of a software team. This module will be split down into the following sections, first well look at a typical career path for a software developer heading into management. Then we'll look at the difference between a manager and a leader and how you will need to fit both these roles. Then we'll look at some of the different types of leadership styles that you can adopt. We will then look more into the roles and traits of a software leader. And finally, we'll look at how you can decide if this is the right thing for you. I'll also tell you about my story of how I became a manager and some of the thought processes I went through.
Your Team Welcome back to this module for the Developer to Manager Course. My name is Stephen Haunts. In the previous module we looked at what it means to be a manage or leader of a software development team and we looked at whether it is the right decision for you. Hopefully you have decided that it is the right decision for you and you are keen to find out more. In this module we'll look at what a typical software development team looks like, including typical software development team roles and who you can expect to be working for you on your team. Next, we'll look at employee contract types, like permanently employees and consultants. We'll also look at the advantages and disadvantages of both types of employee. Then, we'll look at hiring and firing within your team, and then finally, we'll look at motivation and innovation without your development team. Now let's take a look at some of the typical roles you will find on a software development team.
Your First Month Welcome back to this module for the Developer to Manager Course. My name is Stephen Haunts. In the previous two modules we looked at what it means to be a manager and then tried to help you determine if it is the right career move for you. Then, we looked at what your team should potentially look like and how your team impacts you as a manager. Those two modules contained more of the theory content for this course. What follows now is more practical advice. In this module and the two that follow, I'm going to help you put a plan together to help you through your first three months as a manager. You don't necessarily have to follow this plan exactly, but you can use it as a guide to tailor your own plan. Every company or department is different, so this will influence your plan. I recommend watching all of the following modules prior to you starting a new job if you can and then refer back to them refresh your mind while you are working your way through your first three months. In this module about your first month, we will cover the following subjects. Getting your bosses expectations. It's important to know what your own management expects of you. Introducing yourself to your team. Gathering information about your team's projects. Domain knowledge is a very critical thing for you to master. And finally, getting to know your team. If you are at a new company you will not know any of the people in your team. If you are becoming a manager at a company that you already work at, then you may already be familiar with the people. But you'll need to get to know them a lot better.
Your Second Month Welcome back to this module for the Developer to Manager Course. My name is Stephen Haunts. In the previous module we looked at a plan to help you through your first month as a new manager. In this module we'll cover a plan for your second month as a manager of a software development team. In this module we'll cover the following subjects. First we'll look at reviewing the first month and seeing whether you are happy. Then we will sense check your team. Have you observed any conflict? Are they delivering and do people have a clear understanding of their roles? Then we'll talk about meeting your business and IT stakeholders. Next, we'll take a look at evaluating your team's development practices to make sure they are fit for purpose. Then we'll take a look at mentoring, but not for your team, this time the mentoring is for you. With all the information and experience you have so far at the company, we will then look at starting to document your vision for the team. And finally, you will try to identify one major problem that you think needs to be fixed and will be a candidate for an early win or set of wins.
Your Third Month Welcome back to this module for the Developer to Manager Course. My name is Stephen Haunts. In the previous module we looked at a plan to help you through your second month as a manager. In this module we'll cover a plan for your third month as a manager of a software development team. In this month we will cover the following subjects. First we will look at soliciting feedback from your boss and taking any corrective action if necessary. Then we will look at putting a plan in place to implement the items in your vision document. Then we will take a look at some metrics for measuring the progress and improvement in your team. Then we will look at developing a set of knowledge, skill, and behavior documents, which serve as a way of identifying what you should expect from your staff in terms of what they know, the skills they have, and the behaviors you expect. Finally, we will take a look at objective setting for the members on your team.