It’s better to overcommunicate than have a dead channel! Set up regular communication channel like Slack or Teams.Are your developers actively involved in code reviews and commenting on other developers’ code? Can you get a feeling of what the Cycle Time is and how long things stay in review? Is bug tracking software being used? Find out if there’s a continuous deployment setup. Review the current software development processes and identify areas for improvement.Learn about the company culture, vision, mission, and values, and how they align with the engineering team's objectives.Get to know their roles, responsibilities, and challenges. Meet with your direct reports in a regular one-on-one meeting.Here’s a sample of some 30-day goals for a new software engineering manager: Keep track of progress with regular 1:1 meetings. Fit your direct reports into the equation and write down exactly how they’ll help you reach your and your company goals. Link back every single task of yours to your macro goals. With this out of the way, start connecting the dots. This will help you understand the technical challenges your team faces. Take a deep dive into the codebase, including the architecture, tech stack, and any existing issues or bugs. Attend all-hands meetings, familiarize yourself with best practices (later you could propose new ones), and meet with other managers and stakeholders. Read about the company, the products, and the processes. Next, learn as much as you can, starting with how you’re going to attain these goals. When you’ve got that figured out, divide these goals into manageable parts. The first few big-picture ideas that come to mind may very well be your most important goals for your first quarter at the company. Here’s a 30-60-90 day plan that might work for you: Day 1 to 30 - A Roadmap for Learning and Goal-SettingĪsk yourself this question: “I was hired to…?” One of her main goals with the plan was to get her thinking differently about rewarding her direct reports and how to help them become not only better coders, but better people. She did, and it helped her think about her goals for the quarter. It was actually mentioned to me in our Slack community for engineering managers by somebody who uses it for 1:1 meetings, not long-term strategizing.Īfter they mentioned it, however, I did have a look and encouraged one of our new engineering managers to give it a try. I’ll be totally honest, with all these methodologies and project management tools in software development, it never occurred to me to read up on the 30-60-90 day plan. It’s basically your blueprint to success! This plan allows new engineering managers to gain clarity, set the tone, and communicate goals to direct reports and superiors. A key part of the onboarding process, this strategy includes a breakdown of your new priorities, including specific tasks, projects, and objectives, which you should aim to achieve within the first 30, 60, and 90 days on the job. Looking for a tool that will help you run effective 1-on-1s with your developers? Give hay a try What Is a 30-60-90-Day Plan for New Software Engineering Managers?Ī 30-60-90-day plan serves as a valuable resource for engineering managers who are new to their role.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |