I met with my project manager today and we discussed my formal responsibilities on DASL. I've recently been working on stabilizing my work pace, and in order to do so, it's important to know what the heck I'm supposed to be doing.
About a month ago, I met with my boss, one of the owners of BIG, and we discussed this kind of stuff too. But now that we have some time behind us after I delegated some things away, it was great to review what I've been doing and actually document it--very refreshing actually.
(Updated 12/6/2007 to reflect some fine tuning by my boss)
- Application Development
- Technical architecture and design
- Define best practices and standard design patterns
- Ensure code quality
- Adherence to standards
- Maintainability
- Performance and efficiency
- Provide design direction
- Technology, platform and tool selection
- Manage technical aspects of software integrations
- Advanced development projects
- Provide technical direction for future development and projects
- Developer Management
- Provide work estimates
- Maintain developer task assignments
- Track developer activity and status
- Ensure established development timelines are met
- Development support
- Facilitate developer success
- Mentor junior developers
- Ensure appropriate skill growth
- Builds, deployments and internal environments
- Support and manage creation and maintenance of all internal development, support and QA environments
- Support and manage internal and production builds
- Select, create and support build tools, utilities and automation
- Production code deployments
- Analysis and field support
- Maintain and administer the DASL QAPR website
- Advanced technical support as necessary
- Internal subject matter expert support
While trying to document the list, I went to my desk and grabbed a month's worth of task tracker sheets to make sure that everything I've been doing was covered in the list.