Update on the New Job
Time flies. All the sudden, I'm well into the fourth week of my new job. Here is a quick update.
Changes are difficult, job change is no exception. I have switched job many times in the past, and I found coming in as a dev manager is especially difficult. Here is a list I made for myself before I took the job.
- Technology
- Code base
- Infrastructure (system and hardware)
- Production SLA and monitoring
- Process
- Development life cycle
- Deployment process
- Troubleshooting process
- Support and escalation
- Any relevant company policies
- Domain knowledge
- High level business logic for all key components
- Product/service in relation to revenue
- My team
- Skill set
- Career goals
- Interests
- Management
- Who has influence over my team, directly or indirectly
- Peer teams
- Whom my team need to work with
- History between my team and peer teams
Checking my progress again the list, I still have a long way to go.
3 comments:
Still using SCRUM at the new role?
Yup. SCRUM + Kanban
Your list is a great one. Another thing I would get is the past year's incidents/primary bugs - this will give you a very good idea on what exact product you are getting into.
Post a Comment