Business Requirements: Becoming the Means to Manage the Project

This session will focus on how to develop and manage Business Requirements as a means of managing the scope of what is delivered by a project.

Learning Objectives:

• Effective Business Requirement definition
• Using a Requirement Management practice to control and monitor scope
• Using Requirement Metrics and Reports to gain perspective on project progress and drive project decisions

Jared Chartrand

Project Manager

TELUS

Jared began his IT career while in school at UBC in 1997.  After several years in the pre and post dot-com start-up world, Jared joined Accenture in 2004 to work on a long-term engagement with TELUS.  In early 2008, Jared left Accenture to join TELUS full-time.

One of Jared’s core roles within TELUS has been to transform their requirements definition and management practices.   This transformation began with IT, but has since expanded to TELUS’ business groups as well.

Since assuming this role, Jared has been able to implement a pragmatic requirements practice grounded in sound methodology.  The requirements management practice now drives the rest of the activities in the software development lifecycle.

Beyond defining the requirements management practice itself, Jared’s role has also been to transform the organization; a successful practice is useless if the organization is not capable of supporting it.  Transforming the organization has encompassed building the right skills at all levels, implementation of an org structure to support the work, and the implementation of a change management approach.