Last week, I presented the accomplishments of my applications team in 2009. I was blown away by the number and the scope of the projects my team delivered to our community. I firmly believe that the separation of our operational duties from our project work enabled us to be so productive. While most people would celebrate the project teams |(and we do!), I want to acknowledge the key enabler of this success – our Duty Analyst role.
I blogged previously about our Duty Analyst role here.
Implementing a duty analyst role minimizes the operational interruptions to our team members working on projects. Providing project members focused time to work on project challenges and meeting milestones becomes easier without operational interruptions.
I am proud to say my team delivered on our operational responsibilities and completed 43 projects in 2009.
Here is the breakdown of projects my team delivered:
- Projects by Size : Small = 19, Medium = 14, Large = 10
- Projects by Governance : BCIT Executive = 3, IT Governance Team = 14, Business Applications Committee = 5, Departmental = 11, Operational = 10
- Projects by Community : Learning and Technology Services = 20, Student Services = 9, Education = 4, Finance = 3, Human Resources = 3, BCIT Executive = 3, BCIT Student Association = 1
We continue to refine the Duty Analyst role as well as our IT Governance and Project Management approaches. I am excited to see what we can do in 2010 to continue to deliver value. We will be upgrading our ERP this year and taking a focused approach leveraging the Duty Analyst will make all the difference.