Managing the Agile Team Environment
It is a well known fact that people leave managers, not organizations. Though, Agile teams are known to have camaraderie amongst team members, however the relationship of the manager with the team members and the organizational ecosystem as a whole holds the key to being an successful Agile manager.
Johanna Rothman suggested that Agile managers can no longer afford to be functional managers. They need to be champions for their teams. This means that the manager has to learn about all the team members by doing a weekly, biweekly one-on-one. Managers should be able to provide feedback, meta-feedback (i.e., feedback about how to give feedback) and meta-coaching (i.e., coaching about how to coach).
Managers should also provide career development. This not only helps them build a relationship of trust with the team but also provides a an impetus to the organizational goals. According to Johanna,
Career development is rarely linear. People experiment with different roles at work. It’s even easier to experiment on an agile team, where the team members are generalists. A manager — one who is not responsible for a specific iteration’s goals but is responsible to the organization — can suggest alternatives for a person to take on different responsibilities.
Lyssa Adkins suggested that the Agile manager is responsible for all the activities happening around the Agile team. He is responsible for managing teams, managing investments, and managing the organization’s environment. The subcategories under these categories are
- Managing Teams
- Agile team management
- Resource management
- Performance management
- Managing Investments
- Managing through metrics and reporting
- Agile portfolio management
- Managing the Environment
- Internal partner management
- Supplier managemend and outsourcing
- Organizational change
Likewise, Jeffrey Palmero mentioned that apart from the team, the Agile manager has to manage the customer well so that the Agile team ecosystem can continue to function smoothly. According to Jeffrey,
Part of your job is managing the development team, but you must also manage the customer. Customer satisfaction depends so much on managing expectations. Customers don’t like surprises. You shouldn’t provide surprises.
Lyssa mentioned a series of questions to help an Agile manager analyze if they measure up to the Agile managers role. Some of the questions were
- Are you catalyzing organization change to support agile values, starting with marshalling a culture of value delivery?
- Do you provide significant organizational roadblock removal for agile teams? Do they perceive you as a coach and leader more than as a manager?
- Do you use metrics to help teams improve their performance and to help senior leaders make decisions that improve value delivery?
- How are suppliers encouraged to work in an agile way? Does your outsourcing help or hinder your agile teams?
Thus, the expectations from an Agile manager are much wider and far reaching than just managing a team and delivering a project. They range from career development of team members to removing roadblocks at the organizational level to helping the customers stay happy and realize the business value on their investments.
Are you an Agile manager yet?
ie - 'Agile' managers remove blockers for their team and work on building a relationship with their customers. Therefore, non-agile managers don't do these things and are bad.
Replace 'agile' with 'good' in the above article and tell me this doesn't just rehash common wisdom and knowledge around the role of effective management.
series of questions
Bringing Teams Together With Deployment Automation
Craig Motlin Sep 01, 2014