According to the Agile Practice Guide and the PMBOK® Guide, servant leadership is the foundational leadership style for agile environments. It shifts the focus from " command and control " to supporting and developing the team.
Coaching as a Characteristic: In the context of resource management (specifically human resources), coaching is a vital skill. A servant leader doesn ' t just manage tasks; they focus on the development of the individuals. By coaching team members, the leader helps them improve their technical skills and collaborative abilities, which directly optimizes the " resource " performance and team velocity.
Supportive Environment: Coaching fosters a safe environment for learning and growth. Instead of penalizing mistakes, the servant leader uses them as coaching moments to ensure the team becomes more self-organizing and cross-functional over time.
Empowerment: This approach empowers the team to make their own decisions. The leader acts as a facilitator, removing " impediments " (roadblocks) so the team can focus on delivering value.
Analysis of other options:
Lecturing (Option A): This is the opposite of servant leadership. It implies a top-down, one-way communication style that stifles the collaborative and self-organizing nature of agile teams.
Construing (Option B): This means interpreting or explaining the meaning of something. While a leader may interpret requirements, it is not a defining characteristic of servant leadership that specifically supports resource management.
Measuring (Option C): While agile teams use metrics (like burn-up or burn-down charts), a servant leader ' s primary focus is on the people and the process, not just the rigid measurement of output. Measuring without coaching often leads to " command and control " behavior.
Per PMI standards, the primary role of a servant leader is to provide the team with what they need to be successful. Coaching is the primary mechanism used to develop the team ' s capabilities and ensure they can manage their own work effectively.
