Changing Agile Roles – The Managers

This content is syndicated from VersionOne by VersionOne. To view the original post in full, click here.

I have a confession to make.  I'm a manager.  I've been a manager for many years.  I've led agile development teams most of that time.  I've been told I'm a pretty good manager.  And when I look in the mirror, I don't see any pointy hair.  And as a point of fair disclosure, I believe there actually is a place for managers on an agile team.

Ever since the first days of extreme programming, I've noticed a definite view in the agile development community that managers become superfluous.  Self-organizing teams, coupled with the principles and practices that ease the path toward product and project management, have removed the need for management.  This is a seemingly wonderful sentiment, but it just doesn't happen that way.  Companies will always have some sort of management structure.  Who those managers are, and what they do, will change considerably though.

There tend to be two types of managers in a software development organization.  One of those is the project manager, who is responsible for the successful delivery of the project.  His domain includes status of work items, tracking of progress, and ultimately the schedule of delivery.  As one can imagine, in an agile development environment this role will change considerably.  About the closest relationship to an agile role would be the customer, or in Scrum terms, the Product Owner.  What is truly different though, is that the Product Owner is a member of the team, and "status" is not reported directly to or from him.  Many project managers are inclined to continue to track time-lines, and to worry about such things as "percent done" or other metrics that hold little meaning to the agile community.  I like to remember how much of a change in focus this is, and I do my best to remember how hard such a change is.  The project manager who becomes an agile product owner is being asked to let go of a lot of perceived power and responsibility, and move into the uncomfortable world of "petitioner".  I say "perceived" because project managers never really had that much control over the course of a particular project, just lots of responsibility.  This is why there was so much emphasis on risk analysis and predictive analysis around the project plan.  We aren't able to affect what will happen over the course of the project, just plan what our reaction will be to any particular contingency.  Letting go of this will become liberating over the long run, but in the meantime, there is a lot of change.  A lot of this is personal, so let's give them a break.

The other type of manager is the functional manager.  Software development teams tend to be organized at some level around the type of job they do.  For instance, there is usually a development manager/director, and another for quality assurance. Much of what this manager is responsible for is still very important in an agile organization.  These functional managers tend to be responsible for many of the personnel administration issues, such as hiring/firing, budget, and many of the technology and purchasing decisions.  These traditional activities are important.  The change is the direction such activities come from and where the decisions originate.  The agile team becomes the primary focus of technical, and sometimes, personnel decisions.  A functional manager is going to be supporting these decisions, providing the "cover" necessary for experimentation exploration.  This won't change what the functional manager has to provide to the executive team.  The manager is still going to have to represent the progress that the team is making.  The manager is also going to be the one whose career is most affected by the success or failure of any particular effort, especially during a dramatic effort, such as the initial shift to agile.

So in the end, we want to keep in mind the amount of change that each agile manager experiences, no matter what their original role was.  Especially during the initial shift to agility, the managers are in extremely precarious positions.  Most of them are involved because they want to make things better, so lets give them a break.  Over time, their jobs may become completely unrecognizable compared to what they used to be, and this is a Good Thing.  In the meantime, they are going to need support in embracing this "new world".

Leave a Reply

What is 9 + 6 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”

PETER SILVA-JANKOWSKI
IPC MEDIA

“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”

LUKE SHARKEY /STRATEGY & IMPLEMENTATION LEADER
SUNCORP

“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”

GILES BENTLEY, DEVELOPMENT & OPERATIONS DIRECTOR
TIME INC

“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”

DAN PULHAM, DIGITAL DIRECTOR
TELSTRA

“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”

GINA MILLARD
GLASS'S INFORMATION SERVICES

“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”

ANDY JEFFRIES/TECHNICAL LEAD
IPC MEDIA

“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”

HANNAH JOYCE
GLASS'S INFORMATION SERVICES

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”

BRUCE WEIR/EGM
SUNCORP

“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”

BEATRIZ MONTOYA/CONSUMER MARKETING DIRECTOR
IPC MEDIA

“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”

PETER THATCHER, SENIOR ACCOUNT DIRECTOR
ThoughtWorks

“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”

JULIE PEEL
GLASS'S INFORMATION SERVICES