Creating Agile HR, Part 6: the Agile Compensation System

I wrote about career ladders in Creating Agile HR, Part 5: Performance Management, the Career Ladder. Once you have a career ladder, it’s easy for everyone to understand the criteria for a given level. That means you can use an “agile” approach to manage compensation. Compensation is part of career management. Career management includes: Recognition (what …

Creating Agile HR, Part 5: Performance Management, the Career Ladder

One of the big roles of HR is to shepherd the assessment of people and their fit for their jobs. That’s called “managing performance.” Managing performance is about: Creating and curating a career ladder for all jobs. That’s exempt (salaried), non-exempt (hourly), and all management. Manage salary parity. HR might help a manager learn how to provide feedback and coaching. (I …

Defining “Scaling” Agile, Part 6: Creating the Agile Organization

We might start to think about agile approaches as a project change. However, if you want to “scale” agile, the entire culture changes. Here is a list of the series and how everything changes the organization’s culture: Defining “Scaling” Agile, Part 1: Creating Cross-Functional Feature Teams. Without feature teams, I don’t see how you can …

Defining “Scaling” Agile, Part 5: Agile Management

One of the challenges I see in organizations is how managers can use agile approaches. One of the biggest problems is that the entire organization is organized for resource efficiency (think silos of functional experts). Agile approaches use flow efficiency. Thinking in flow efficiency changes everything. Many people in organizations believe that dividing up the …

Defining “Scaling” Agile, Part 4A: Sharing Agile Outside of Product Development

Note to my dear readers: As I write, I realize this series is growing. Thank you for your understanding in advance. In Defining “Scaling” Agile, Part 4: Sharing Agile Outside of Product Development, I wrote about an independent workgroup with one stream of work. I used Customer Support as an example. Support has one stream: …

Defining “Scaling” Agile, Part 4: Sharing Agile Outside of Product Development

Here’s where we are so far in this discussion of what it might mean to “scale” agile approaches: Part 1: Creating Cross-Functional Feature Teams (Teams that can produce features on a regular basis) Part 2: Programs of Cross-Functional Feature Teams (Programs (multiple teams working together) that deliver features on a regular basis) Part 3: Agile Product …

What’s the “Right” Term for an Agile Transition or Transformation?

As I finish the agile project management book (Create Your Successful Agile Project), I am working on what stays in this book and what I use in the agile management book (next up after the PO book). That leads me to this question: What do you call a transition to agile approaches? Is there a …

Defining “Scaling” Agile, Part 3: Creating Agile Product Development Capabilities

In the “Scaling” Agile: Part 1, I wrote about cross-functional collaborative teams. The cross-functional collaborative feature team is the basis for “scaling” agile. In “Scaling” Agile, Part 2, I wrote about programs. I realized I need another part before my original part 3 :-). This new part 3 is about creating agile product development capabilities. …