|
|
|
|
|
|
|
|
|
|
|
Typically our engagement model would involve a team from visions@work and the client.
Our primary areas of expertise are design and implementation capabilities in E-business
technology and user-centric creativity. A fairly mature project delivery methodology
ensures that success is consistent and predictable. We use five entities to execute
the project:
Executive leadership - The executive leadership
serves as the steering committee for the project and is constituted by senior members
from the client organization - typically of the levels of CEO and CIO. The executive
leadership serves as the final escalation point for all go/no go decisions for the
project in its entirety.
The Program Management Office (PMO) - The PMO
is responsible for avoiding the 'Black Box Syndrome' that large multi-organization
teams are prone to.
Individual Project Manager - Individual Project
Managers manage resources from their respective organizations, as well as the schedules
and deliverables that are exclusively handled by their organization. Individual
Project Managers will also assume responsibility for those activities that are led
by individuals from their organization.
Communication
Communication is the key to resolve all issues. A well planned and executed communications
strategy ensures that the team and the project stakeholders are in constant communication.
Issues are resolved as they arise. Formal communications in the form of reports,
meetings and workshops are leveraged on the project. All team members share the
same processes and systems for document management and version control.
One Team – team structure and reporting relationships
The key to success in these projects is integrating teams across geographies, cultures,
work practices and work functions. Early on during the project initiation processes,
workshops establish common processes, ground rules, escalation paths and communication
plans. Teams are defined by the requirements of the project, drawing expertise,
capability and experience across functions and organizational boundaries.
At the beginning of the project, the organization hierarchy and reporting relationships
of the team members are drawn up and established. This structure over-rides otherwise
organizational hierarchies, except in cases of administrative details such as allowances
etc. Team events dissolve organization boundaries and establish bonds that the team
will draw on as the project progresses. Team events and 'ice breakers' are essential
tools to create 'one team bonding'.
|
|
|
|
|
|
|
