Diversity Framework

A Guideline for Managing Behavioral Differences in Project Teams

The framework consists of four phases that represent the traditional process phases in any project (initiation / planning / implementation / closure) or the software development approach Rational Unified Process (inception / elaboration / construction / transition):
Stacks Image 5434

The workflow is structured in five stages that partly build upon each other.
  1. The first stage aims at increasing awareness for the topic diversity and for differences and commonalities within the project team.
  2. In the second stage, a deeper diversity analysis can be performed that allows more insights into the team’s expectations, behavioral preferences, and potential gaps between those preferences.
  3. In the third stage, solutions for the investigated diversity gaps can be elaborated and integrated into the project organization.
  4. Furthermore, a fourth stage that deals with assessing arising challenges or chances is suggested.
  5. Finally, the stage model is complemented by a continuous re-assessment and learning stage.
PROJECT TEAM or STAKEHOLDERS?
It is possible to perform the Elaboration phase and the consecutive phases also with external stakeholders.
This should be done in 2 iterations:
  1. In a first iteration the Elaboration phase should be performed within the project team.
  2. In a second iteration it is possible to include powerful stakeholder - for instance the customer.

ROLES
The following roles appear in the steps of the framework:
Project Manager
The project manager is “the person assigned by the performing organization to lead the team that is responsible for achieving the project objectives” (Project Management Institute, 2013, p. 16). Her/his responsibilities are for instance:
  • focusing on specific project objectives and managing constraints
  • leading the project team
  • understanding different organizational styles and cultures that may affect a project
  • ensuring effective communication with all relevant stakeholders and managing their influences on the project
Project Team /
Project Team Member
The project team includes
  • all persons of the core team members,
  • project manager,
  • and project owner.
Supporter
In many cases the project manager might not have sufficient skills and/or experience for applying the diversity framework alone. Especially for the group-based discussion procedure in the elaboration phase, an additional supporter is required to take the role of a (co)-moderator during the workshop. For the mixed procedure part of the workshop, a supporter is also highly recommended. For inexperienced project managers the supporter can also be of great value during the individual-based procedure or throughout all four phases.

A supporter can either be an external coach (e.g. a change coach) or (cultural) trainer, but also a person within the organization.
Including a supporter into the diversity workflow is especially important when applying the workflow for the first or second time. The supporter will accompany the process and help the project manager to learn from the application. In the best case, the supported project manager can support other project managers after a few applications as a supporter and therefore acts as a multiplier in the organization.
Other Roles
  • Stakeholder
  • Project Management Office (PMO)
  • Trainer
CONNECTION TO INTERNATIONAL PROJECT MANAGEMENT STANDARDS
The framework is connected to the following fields in project management according to the standards PMBOK® , ICB 4.0 and PRINCE2.
PMBOK®
(Project Management Institute, 2017)
The diversity framework touches the following knowledge areas defined in PMBOK Guide of PMI:
  • Project communications management
  • Project risk management
  • Project stakeholder management
  • Project resource management
Furthermore, the framework adds up to the social skills defined in the PMBOK® as well to the Project Manager Competency Development Framework (CDF).
ICB 4.0 (International Project Management Association, 2015)
In the new version of IPMA’s baseline, the following competence elements are affected:
  • Power and interest
  • Culture and values
  • Personal communication
  • Relationships and engagement
  • Leadership
  • Teamwork
  • Conflict and crisis
  • Organization and information
  • Stakeholder
PRINCE2 (Projects in Controlled Environments)
The framework is reflected in the PRINCE2 standard in the following principles, themes, or processes:
  • Learn from experience (principle)
  • Project organization (theme)
  • Projekt risk (theme) / risks (processes)