Blog

Agile Facilities: what a small exercise can force you to think differently as an agile coach.

Mid January 2017, I attended an interview meetings with a customer of a Global player and I got an unusual exercise: how to arrange a facility to make it agile?

My first reaction was WTH is that and then roughly I told myself to play this game, and I liked it.

So what means agile for a facility?

After this interview, I needed serious feedback, so I shared this exercise on Facebook and got awesome feedback from my pairs. On one day, I’ve got around 40 feedbacks that I can categorise in this way (sorry, have to summarise the content):

Ask the team

  • “Don’t design. Let people explore, learn and adapt. Give them some time to find out their own setup, they wanna start with. Let them be adults and don’t parent them, just because the IBM guys asked you to … “

  • “how do you get the team to take ownership of their team area”

  • “Remember the “self-designing team workshop” – let them figure out their collab setup, their appropriate work environment, their learning style the same way. Encourage “moving around” instead of creating fixed desks as little territories. This exercise is either a joke or a good demonstration, why the large ones don’t really get it 😉 “

  • “Although teams can give individual preferences and to an extent collaboration agreements but the scrum master has to do some interior designing to manage conflict if and when it occurs E.g. Open floor plans vs Private offices vs somewhere in between”

  • “Don’t mix up prescribing detailed practices (acting like a parent) and growing from first principles. Room setups will hopefully only follow an in-depth elaboration l why such a team wants to collab at all. If this is not understood, better stick to where people are coming from. A coach or Scrum Master starting to design work spaces should go back and learn the basics”

  • “Didn’t prescribe any; talking about conflict resolution. Kurt’s answer is pretty good”

  • “The correct answer is probably the caves and the commons where everyone sits and does pair programming in the open common area in the middle but has private rooms for when the bosses are doing deals on the phone or the rock stars are coding AI algorithms and need to concentrate.”

Worthless

  • “This is why the term “Agile coach” is worthless. Your test is about creating a seating arrangement and defending it? Really? Sounds like something for an interior decorator. Better question: how do you get the team to take ownership of their team area react”

  • “Hey, we need to design the new space for the Viper Project. Who can do that?”

  • “Fine as an interview question. Interview questions are not for getting at an answer; rather they are for learning how someone thinks.”

Proposition

  • “I think the chairs should be located on top of the monitors and the project managers should live in the bathroom.”

  • “As long as I had my iPhone, living in the bathroom could work”

  • “Architecture the layout following the agile principles. E.g Onion layered and circle “

  • “My first reaction is to design the work area. My next reaction is, ask the team! Get them involved, ask them to design their own work area. I bet they’ll like it better if it’s theirs than if it’s imposed on them.”

  • “My answer would get those people in the room and have them design it. I would have to go by some sticky notes and sharpies and add that to the list. “

  • “Love this exercise! The answer would be quite telling.”

  • “There’s some interesting stuff to probe into that go beyond space design: “the core team is about 20 people”, the siloing of technical/”SME” roles before they’ve even started, and including executive sponsors on the team. Definitely ask the team to design their own space…but before that, ask them to *design their own team* before imposing all these roles on them.”

  • “Especially if you find out they are all remote”

  • “So my answer of: pile everything into the center of the room and say, “Team – your first assignment is to organize this space to maximize the effectiveness of your team.” And then watch what happens. And not let them break the safety and fire codes. “

  • “Before I would try to solve the problem, I would point to them there are severe inconsistencies and ambiguities with the problem itself:1) there are “bad overlaps” of traditional and Scrum roles: a) sponsors and PMS “

On the recruitment

  • As a discussion exercise, I find it interesting. As the business I would learn pretty quickly quite a bit about the prospective coach. “

  • “Questions of this type can be very useful in getting to know the candidate and the hiring manager.”

  • “Correct but I saw an interesting and intriguing approach to agile behavior”

  • “It is easy to look at this on the surface and feel like the organization/person/people that designed this question do not understand Agile’s values and principles but maybe they are really looking to see how you understand the same by how you address”

  • “Isn’t that in a sense the great thing about this exercise. Everybody trying to design the room without group involvement misses the point of having an agile coach. But wouldn’t everybody who just say they would ask the team without on how they facilitate this discussion, be an ineffective coach too?”

  • “Hmm interesting guesses here. Now let’s assume that you have to Organise a stage for a project and you can have on site customers i.e. Not only developers. So here build a safe to fail Container facilitating the conversation.”

  • “I think it provides the hiring party with some great insight into the reasoning of the agile coach. Looking forward to your picture!”

This was a very interesting feedback from my fellow agile coaches and I would thank for their contribution: Michael Leber, Kurt HĂ€usler, Daniel Markham, Atif Rahman, Amr Elssamadisy, John Miller, Djebar Hammouche, Howard Sublett, Pierre Hervouet, Linda M. Cook, Alan Dayley, Bob Sarni, Ralf Kruse, Astrid Claessen, Richard Kasperowski, Stacia Heimgartner, Jeff Lopez-Stuit, Alberto Brandoloni, JB Rainsberger, Michael Feathers, Griffin Jones, Mike Beedle, Dov Tsal. Guys you are awesome and I value all your comments… all.

XO

Pierre

Agile4HR, The Project

https://agile4hr.net

AGILE4HR IS AN ON-GOING RESEARCH PROJECT WITH HR PEOPLE WITH THE INTENTION TO GET THE ANSWER ON 2 QUESTIONS:

  • is Agile HR?
  • how can we create HR Agile

In the economic context of a company, wealth is created by :

  • business value
  • knowledge value
  • optimal utilisation of inner resources including people.

HAPPY AT WORK?

Being happy at work doesn’t mean being lazy at work, it means working better, more efficiently and to be able to answer this simple question: what kind of value do you create when just doing your job? What kind of value can you create if you are fighting to survive?

OPTIMISATION OF RESOURCES?

Optimisation of resources means to create an environment where new ideas can be safely tested in a continuous flow of intrinsic innovation.

During the last decade, we learnt from agile and lean that people involvement increase business agility and reduce the response to risk. We tested this in the area of IT now it’s time to involve the whole structure.

The evolution of agile moved practitioners from engineering to organisational design and change management where « human interactions » is key.

Instead fighting against HR, shouldn’t we work together? Shouldn’t we hack HR with them to enable a human centric pivot?

AGILE4HR IS A COLLABORATIVE INITIATIVE MOSTLY HANDLED BY HR PEOPLE WITH THE PURPOSE TO BUILD AGILE ORGANISATIONS CULTURE.

Like in an agile project, this initiative is iterative, empirical and collaborative.

One year later, 10 countries and cultures later, we discovered common patterns for HR and redefine the traditional IT related relations of Agile Coaches to an enlarged organisational-based role. Consequence of this is that HR doesn’t stand for Human Resources anymore but for Human Relations.

TO REFINE THE SCOPE ALL TOGETHER WE USE CONFERENCES AND WORKSHOPS IN A SOCIALISING AND INTERACTIVE MANNER.

The presentations will explain the vision of this initiative and the cultural differences we faced during our workshops, trainings and meet’ups.

In the context of a conference, we will explain 3 steps:

Step 1: from Agile Coach point of view,

how we interfere with organisation transformation, how our roles are operational by coaching people, teams, creating a good morale, creating a sustainable pace, collecting lessons learned and manage on-demand efficient trainings. How we change the corporate culture.

Step 2: from the perspective of HR,

how recruitment can be managed, how corporate social responsibility can be managed, how to manage diversity, how to retain high qualified people, how to share the bad news, what’s about personal appraisal, etc.


Step 3: Unleashed from surviving,

work has evolved to something that matters to people. Sense making is one of the drivers in the future of work evolution. Organisations will attract their people with their corporate values: corporate social responsibility i.e. agile will be one of the principal criteria.

Potentially Outcome: the Book

Once a year, we will document our community work through the publication of a book increment.

screenshot-2017-01-02-13-18-15