People Management: The Process

The following process goal diagram overviews the potential activities associated with disciplined agile people management. These activities are performed by, or at least supported by, your people management (often called a human resource) team.

People Management Goal Diagram

Figure 1. The process goal diagram for People Management (click to enlarge).

The process factors that you need to consider for people management are:

  1. Build agile culture. An important aim for your people management efforts is to enhance the agile facets of your organizational culture.
  2. Guide careers. Your organization should support the career aspirations of its staff, providing opportunities to people and supporting their efforts to achieve their goals.
  3. Reward staff. There are many ways that people and teams can be rewarded, including base pay, bonuses, and non-monetary rewards. For some people in some organizations their pay is publicly known (for example, in Canada public employees who make over a certain amount have their salaries published annually) whereas for most people their remuneration strategy is private.
  4. Manage staff changes. Your organization needs to perform basic functions such as hiring (onboarding) staff, letting people go (offboarding), promoting, demoting, transferring them and providing benefits to people.
  5. Ensure diversity and inclusion. Diversity strengthens your organization, and when you include a range of diverse voices in your decision making you will prove to be more innovative and more likely to delight your customers.
  6. Organize groups. What is your strategy for organizing your IT department? Your Marketing department? Your Finance department? For example, for IT do you do it by job function (e.g. have a business analyst group, a project management group, and so on), by geography (e.g. a North American IT department, a European IT department, and so on), by business division (e.g. an IT group to support Retail banking, an IT group to support brokerage, and so on), or by value creation (e.g. an IT group to support a specific product line). Or combinations thereof?
  7. Staff groups. You need to identify, and plan for, your organization’s staffing needs. This includes succession planning for senior people, critical technical positions (yes, that includes all those legacy COBOL programmer positions), and other critical roles such as product owners. This also includes staff capacity planning/forecasting as well as determining your mix of full time employees (FTEs) and contractors.
  8. Form teams. There are different types of teams that can be formed to address IT functions, each of which are (self) organized differently.
  9. Evolve teams. Team membership and structure evolve over time, and there are several common strategies that enable this. Some teams are ad-hoc, forming when their needed and disbanding when they’re not, with little or no management intervention. Sometimes people are assigned to teams and sometimes people volunteer to be on a team. Some organizations are holacracies where teams are self-organizing and have defined strategies for enabling collaboration and communication between teams.
  10. Govern people management. Your people management activities, just like all other activities, should be governed effectively. An important aspect of people management governance is the definition of roles and responsibilities (see Roles on DAD Teams and DA Roles at Scale for suggestions), as is the usual measurement and monitoring activities. Governance of your People Management effort is an aspect of your overall Control strategy.

Related Reading