Feature Teams: First Among Equals

This content is syndicated from Edge of Chaos | Agile Development Blog by Olga Kouzina. To view the original post in full, click here.

Last week, in the When One Product Owner Is Not Enough post, I shared some thoughts on when a team might consider replacing one product owner with several feature owners. This time I’d like to tell more about feature teams, and their guiding principles/values, should some of you decide to try this setup in your organizations.

The very first thing to do would be to pick up the feature owners. These people would ideally spend several years working in the organization, where they would track the evolution of the product, having the general awareness of the priorities and business objectives. Of course, the priorities and objectives can be shared and discussed in a conversation with a relatively new person, but someone with the intrinsic knowledge would fit much better. Someone who’s been in the product context for quite a while, as a dev, or as a QA, or as a UX designer, would be able to balance the strategic priorities projected on their feature. A feature owner would eventually become an informal leader, based on the “first among equals” principle (or primus inter pares, as in Latin), where this person doesn’t have the formal “order-forbid” rights, but is viewed by the other peers as a competent authority, as someone who champions the team. The feature owner would also paste this feel of awareness on the rest of the team, thus fostering engagement.

the coat of arms for feature teams

The coat of arms

Next, the #1 goal of a feature team is to release their feature as fast and as best as they can… and then re-iterate based on the feedback from customers, of course. Anyone in the team has to be aware of that, and keep that in mind. They have to learn to think in the context of the whole feature, not only their one user story, or task. In other words, go beyond their primary knowledge domain. The notorious UX-dev clashes, when developers say something like “it’s very hard to do this UX in terms of development”, have no right for living. Yes, sometimes code-related things make it hard to implement a nicer UX solution. But this is not to be left hanging in the air. Developers and designers in a feature team are supposed to sit down and discuss best viable alternatives, considering all the challenges, pros and cons from both the sides. The faster things are discussed, the higher the chance that a good approach is found faster, and this would bring the team closer to their ultimate #1 goal. That’s what integrity as a feature team value is about. 

In a feature team, there’s no subordinate relationship. A feature owner is not supposed to assign work as such. Neither it is supposed to work as “I have no tasks left, tell me what to do?”  A feature team is even more about a collective ownership of a feature, so if a team sees some challenges, they need to talk, discuss and decide by themselves. There’s no micro-management either. If there’s a bottleneck at the UX stage, or at the development stage, or at the QA stage — it’s up to the team to come to a solution. That’s what autonomy as a feature team value is about.

A few more words about engagement. This is something that really has to be in place for feature teams to exist. It can only be rooted in the culture of an organization. The genuine interest, and broad outlook, looking beyond “this is my task, and that’s all I know”. Such awareness of shared goals and priorities in product development is a must, and it’s a job of the strategic management to keep people on the same page with the objectives, updates and changes (share feedback from customers, communicate changes in the priorities, making sure that people in the team make sense out of them).

Finally, the “first among equals” principle might be better known to some of you as “organizational flatness“. In brief, this means no formal authority. The most recent example of effective organizational flatness that comes to my mind is Valve, the video games company. They have some interesting insights in their handbook for new employees (it’s a .pdf file). But one has to be aware that absolute flatness as a goal is futile. It can be reached to some extent, but it really depends on the culture of genuine engagement. And, let me re-iterate, that “flatness” as such rather means the “first among equals” setup. There’s no way for a group to go without a leader, be it a formal or an informal one. I hope to write more on organizational flatness in one of my future posts.

Leave a Reply

Your email address will not be published. Required fields are marked *

7 − seven =

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

What People Say

“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. ”


“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!”


“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.”


“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.”


“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...”


“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.”


“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.”


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


“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.”


“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!”


“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.”



To explore how we can help you, please get in touch