Showing posts with label leadership. Show all posts
Showing posts with label leadership. Show all posts

Sunday, September 6, 2020

The 5th Agile Principle, leaders must enable teams

            Build projects around motivated individuals.
    Give them the environment and support they need,
            and trust them to get the job done.

Think for a moment about Indian Cricket team, India won “One day International Cricket World Cup” twice – in 1983 under the captaincy of Kapil Dev and in 2011 following the captaincy of Mahendra Singh Dhoni. I bet no one told these winning teams: “To start practicing at a certain time of the day or to play shots using only a specific technique or focus on only an area”. The very idea is absurd.



In-fact, they were all motivated bunch of individuals and had freedom to execute the job in hand with utmost precision with autonomy. They truly represent a self-organizing team.

Leaders, captain, support staff and sponsors played a vital role in building the environment for winning team. Whether you’re fixing a car, learning to ride a bicycle or launching a satellite, Autonomy plays a vital role for all of us. Autonomy, Mastery and Trust explained by Daniel H. Pink, author of the book “Drive; the surprising truth about what motivates us” is closely knitted to Agile principles.


The 5th Agile Principle is for leaders who must bring following attributes to the project environment:

  1. Be available and approachable to resolve day to day impediments and celebrate success along with team.
  2. Bring transparency in budgets, timelines, project road map and make it accessible for everyone visually.
  3. Encourage culture of continuous constructive feedback, cheer conversations, advertise courage and care.
  4. Develop deep understanding of business goals and objectives among teams and this "Shared understanding” ensure that teams heads in the same direction of common goals.
  5. Provide tools and resources to boost team effectiveness.

Accountability during autonomy

For leaders, it is vital to not lose focus on element of accountability when we entrust team with autonomy. Per Motivation 2.0 “people by-pass responsibility when they have autonomy”, however Motivation 3.0 presume that people want to be accountable. Explained by Daniel H. Pink, author of the book “Drives”.

Too much freedom may result in chaos and it is a space leaders must avoid, and it is a continuous uphill struggle to strike a perfect balance especially in complex project environment, where execution of tasks by autonomous teams is challenged by the need to coordinate and align work with multiple experts, sponsors and other units in the organization.



Let’s look at three frameworks which provides appropriate eco-system to maintain autonomy among teams, we they all stick around together and utilizes the true power of Autonomy.

The 5th Agile Principle “Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

1. With-in Scrum framework, values of Commitment, Courage, Focus, Openness and Respect are catalyst to the Agile delivery model and bringing Autonomy, Mastery and Trust in complex project environments. The agile ceremonies especially Retrospective and Sprint Planning keeps up the morale and trust with-in the team.

2. In LeSS (Larg Scale Scrum), the problem of potential chaos by many autonomous teams is solved by having several teams work on the same backlog and avoid creation of multiple self-organizing teams.

3. In SAFe (Scaled Agile Framework), Business Owners create a boundary to the autonomy of the teams by determining the goals of product development and the event PI planning sets the right tone for team, everyone is involved in planning sessions not just Managers and Architects and sense of ownership is created.

Agile coaches and Scrum masters must be careful and understand the needs of different individuals on the team to create environment of creativity and high performance.

They can help team aligned to common goals by maintaining the required degree of autonomy and thus meeting the Agile 5th Principle.

Sunday, April 16, 2017

Trust and Communication at work place

My three problems are solved by Trust and Communication

Why are we talking about trust?
Trust is only factor which binds humans as well as animals together.   To achieve your defined success in an environment, it is important to build trust. In this article I’ll share my encounter with “Trust”.

Why are we talking about communication?
If we have a trust, it has to be communicated with team. Your trust in your team has to be visible from your actions.

Trust and Communication solved my below three issues.


1. Your team member does not deliver what is expected (Time, Quality, and Scope)
My take:
a. Gather thoughts from team member before allocating assignment or commitment on an end date.
b. Get team's inputs (ideally team should come up with Time, Quality, Scope metrics ), trust their inputs and communicate them the adjusted estimates and delivery timelines.
Outcome:Your team will have commitment to a delivery and you do not have to run around and follow-up.

2. You are contradicted in a team meeting by one or two members of your team

My take:
a. Teams should always know what is being presented in a meeting (especially during: Iteration review and Retrospective). Which will mean that a brainstorming is already done before we present ideas or facts in iteration or retrospective meetings.
b. Highlight views as “team views” and not your own. Stop taking credit of your team work.
c. Do not break a news/ideas in a team meeting, no one like surprises. Always have a conversation with key stakeholders before hand.
Outcome:Your meeting will have fewer roadblocks from your own internal stakeholders. Increased confidence in meetings/workshops or fusions.

3. Team member misrepresent a status of task assigned

My take:
a. Gather thoughts from team on definition of “Done”, communicate this to all members and trust when status is reported.
b. Gather inputs on “how as a team we gather status of task”. Formalize the process and communicate. Re look and adjust the process as we progress.
Outcome:Get near agreed status on assigned tasks and deliverable.
     


Feel free to add details and comment!