Technical Project Management
I manage technology projects from concept to production, combining traditional project management discipline with Agile execution where appropriate.
Typical responsibilities
- Business requirement gathering
- Project charter creation
- Scope definition
- Functional requirements
- Technical requirements
- Work Breakdown Structure
- Milestone planning
- Sprint planning
- Stakeholder management
- Risk identification
- Dependency management
- Change request management
- Vendor coordination
- Development tracking
- QA coordination
- UAT management
- Deployment planning
- Project handover
- Lessons learned
- Project closure documentation
Delivery approaches
Agile & Scrum
Sprint planning, backlog refinement, and iterative delivery for products that evolve with user feedback.
Waterfall
Clear phases, sign-offs, and change control for fixed-scope and compliance-driven projects.
Hybrid delivery
Milestone-based governance with Agile execution inside each phase, often the best fit for client projects.
Why a technical project manager
My background combines disciplines that are often handled by different people, so I can communicate with business stakeholders and technical teams while keeping the project focused on measurable business outcomes.
Tools & technologies
Project charter, WBS, Risk register, Change requests, UAT plans, Jira-style boards, Microsoft 365, Google Workspace
Frequently asked questions
What is the difference between a project manager and a technical project manager?
A technical project manager also understands the architecture, APIs, data and testing involved, so they can challenge estimates, spot integration risks early, and translate between business stakeholders and developers.
Can you manage external vendors and developers?
Yes. Vendor coordination, development tracking, change-request management and acceptance testing are core parts of how I run projects.