Agile Careers. Careers at Ekipa.

People

• People are systematically considered to be good (reliable, self-motivated, trustworthy, intelligent).
• We’re all creative, thoughtful, trustworthy adults, capable of making important decisions.
• We’re all accountable and responsible for our decisions and actions. Integrity: our word is our bond.
• People are fallible, we make mistakes.
• We want to use our talents and skills to make a positive contribution to the organization and the world. 
• We bring positivity, play, joy, and appreciation to our workplace.

Growth and Learning

• Every problem is an invitation to learn and grow. 
• Failure is always a possibility if we strive for our purpose. We discuss our failures openly and learn from them. Hiding or neglecting to learn from failure is unacceptable.
• Feedback and respectful confrontation are gifts we share to help one another grow. 
• We focus on strengths more than weaknesses, on opportunities more than on problems. 

All power is with the team. There is no formal hierarchy, we abandon the traditional system. There are no bosses to turn to. Teams decide what they focus on, how they achieve outcomes and how they solve problems. 

Roles are fluid. We have no job descriptions. Every co-worker is free to create, modify or  remove roles. If you think something adds value to your team’s purpose, you own it and move it forward. Once a week, we organize an overall team retrospective. During this event, the teams discuss the current roles and propose additions, improvements, modifications.

Decisions are made based on the ‘advice process’. If you recognize a decision has to be made, you own that decision. We assume you can make most of the decisions by yourself. If you need the help of other co-workers, ask them for advice, make your decision and move on.

The Advice Process

There are a number of steps in the advice process:

• Someone notices a problem or opportunity and takes the initiative, or alerts someone better placed to do so.
• Prior to a proposal, the decision-maker may seek input to sound out perspectives before proposing action. 
• The initiator makes a proposal and seeks advice from those affected or those with expertise. 
• Taking this advice into account, the decision-maker decides on an action and informs those who have given advice.

_

The Team Decision Process

If the decision maker can’t reach a decision on his own to resolve important issues, a team meeting is organized with the following process:

1. Team appoints facilitator 
2. Agenda and topics selected based on current issues
3. Proposals for resolution are shared
4. Review, improve and refine proposals
5. Group makes a decision. Not consensus. Accepted is solution without anyone having a principled objection

_

Guidelines

To execute work, team(s) and chapters hold regular alignment meetings. All meetings are Mandatory; it’s beneficial for team alignment. The coaching teams on the client side will have their own meeting cadence. We have found scrum to work well. In scrum, we have the following meetings:

• Sprint planning: typically monday morning to decide what will be done during the week. Each team member creates or ‘takes’ tickets (from a Trello board). 
• Daily meeting: every day, we do a 5-15 minute skype call to align on 3 questions: what have you done yesterday, what are you working on today, do you have any ‘stucks’?
• Demo: typically on friday afternoon; team members share what they have accomplished during the week
• Retrospective: after the demo, people share what they believe went well or could be improved in the teamwork, process.

• It’s impossible to change other people. We can only change ourselves. 
• We take ownership for our thoughts, beliefs, words and actions.
• We don’t spread rumors. We don’t talk behind someone’s back. 
• We resolve disagreement one-on-one and don’t drag other people into the problem.
• We don’t blame others. When we feel like blaming, we take it as an invitation to reflect on how we might be part of the problem (and the solution). 

If two co-workers have a conflict, there is nobody but yourselves to resolve the conflict. To reach a resolution, the following conflict resolution process is followed:

1. the two co-workers sit together, discuss the conflict and try to find a resolution.
2. if that doesn’t work, you seek advice from 1 trusted colleague
3. if that doesn’t work, they elect a panel to help resolve it
4. the CEO is asked to resolve it

In all cases, you are expected to keep the information to yourselves and not seek others to be on your side. Nobody should spread the information. 

If you find it hard to open up to someone you have a conflict with, use the following three topics in your conversation with the person:

1. Here is how I feel…
2. Here is what I need…
3. What do you need?

We are a commercial company; our goal is to make profit. Teams are 100% responsible for generating profit. All financial information is open and accessible to everyone. Teams make informed decisions based on the financial information available. 

At the end of each year, 10 % of the profits will be shared with the team(s). Teams decide themselves how to distribute the profit between themselves. 

Our salaries and other compensations are based on the Ekipa salary system. In all situations where you need to spend company money, you do so with caution; frugality and savings are crucial to our company. 

When coaching customers, we adhere to strong Agile principles. Our mission is to move customers to a new way of working, not to stick with what they’ve been doing before. That sometimes creates friction and that’s ok. When you need to push, push. Use the following principles to decide when to push:

1. Ekipa changes how organisations work, think and act.  We don’t solve your problems with waterfall projects running behind schedule (we teach and coach agile, this will help with your delivery medium and long term, not short term)
2. Always think more about products and less about projects.  Even better, #noprojects! As long as there are projects, shuffling of team members and deadlines, you are not bringing the optimal benefits of Agile.
3. Move at the right speed If clients are in a hurry and want you to go faster, tell them the risks! If they move to slow, try to push the right buttons to make them move faster.
4. Use consistent terminology When clients want to set up Tribes in IT, tell them to stop and instead set up tribes across the business. Teams are functional groups of people. Squads are cross-departmental teams. Tribes are collections of squads. 
5. Always create actual value when coaching When teaching teams, use their real work, not dummy work. Our ultimate goal is to bring business value; that means more happy clients (of our client), more profit, more impact in the market. Coaching teams is a means to that end. Always keep your eyes on the ultimate value you must bring. 
6. Agile coaches should do (sprint) plans (etc) too! Create, update and communicate your coaching plans to the customer.
7. Agile = dedicated, cross-functional teams only. If stuck in silos, keep pushing to move towards cross functional, stable teams. 
8. Clients must master Agile at the team level before they try to scale!
9. Reject coaching under/overloads If clients want you to go from 2 squads to 5, reject them and tell them to hire more coaches. If you are underutilized, ask for more.