In Agile framework the role of a Project manager becomes critical to help the team manage themselves or be autonomous rather trying to set targets, audit and devise control measures
2. • Systems sets the bar on people to perform
• Focus is on compliance to Structure ( Control,
Threshold , Efficiency )
• The leader is more of a hike Guide ( Sets the pace,
More Responsible than Accountable )
• People set the bar on what the system could achieve
• Focus is on Flow ( Forming , norming , storming,
Value )
• The leader is a “Floater”, sometimes at front, some at
the rear ( Help move forward , Accountable >
Responsible )
Command – Control Systems Self Organized
3. Agile Principles
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support
they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
Agile processes promote sustainable development. The sponsors, developers, and
users should be able to maintain a constant pace indefinitely.
At regular intervals, the team reflects on how to become more effective, then tunes
and adjusts its behavior accordingly
4. Business people and developers must work together daily throughout the project.
Outlook =
Optimistic
Fuel = Feasibility
Focus =
Destination
Outlook =
Pragmatic
Fuel =
Challenges
Focus = Journey
Business Technologist
5. Pep Guardiola → Moved away from playing around
a talented player to possession & pressing style
requiring more participation across the board.
Gary → Before the start of every series, he would
give the players a survey about what he expected
from them and, at the end of it, he would give them
his assessment. He praised and riled them in
private.
Kumble → you are just trying to prepare the team
for the best of their ability, for all conditions and all
eventualities. You can't really plan for adversity, but
to try to prepare the team to handle those
adversities.
Build projects around motivated individuals. Give them the environment and support they need,
and trust them to get the job done.
Motivation = Skill x Space x Attitude
6. Analysts - Architect, Logician,
Commander, Debater
Diplomats - Advocate, Protagonist,
Campaigner, Mediator
Sentinels - Logistician, Defender,
Executive, Consul
Explorers --Virtuoso,
Entrepreneur, Adventurer,
Entertainer
https://www.16personalities.com/pe
rsonality-types
The most efficient and effective method of conveying information to and within a development team
is face-to-face conversation.
7. Agile processes promote sustainable development. The sponsors, developers, and users should
be able to maintain a constant pace indefinitely.
Communication is the key
Engage Enable Empower
Governance outcomes
1 : 1 catchups
Face to Face critical
feedback
Opinions on Key
decisions
Active solicitations of
ideas of improvement
Team Marketing
Critical Feedback
Goal setting
Expectations
Retrospectives
Client visit dumps
Delivery Assurance
• Information Radiators
• Community and office
sharing sessions
• Tech Debt - Business Value
debates
8. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts
its behavior accordingly
The TEAM owns up to
1. Never stop communicating
2. Customer is always right ( with
valid data points )
3. Share without the fear of being
judged
4. Thinking of common good is
essential to get things done even
at a lower / secluded area
5. Everyone is doing their best with
the context and skill they have on
their hand
6. Feedback is the only way to keep
moving forward
7. Determining what is right and
wrong is a collective decision and
not based on voting
8. Agreeing to disagree
9. Hold each other accountable
9. Recap
Business people and developers must work together
daily throughout the project.
Build projects around motivated individuals. Give
them the environment and support they need, and
trust them to get the job done.
The most efficient and effective method of conveying
information to and within a development team is
face-to-face conversation.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts
its behavior accordingly
Be cognizant of stakeholders drivers ,
expectations and desired outcomes
Its all about motivation to match skill , Challenge
and attitude
Watch out for personality types
Communication to engage, enable and empower
Key behaviours team needs to arrive and own up
10. 1. Always lean on the vision over the method
2. Feedback should not be compromised
3. Never generalize good or bad behaviour
4. Watch body language
5. Space is important to grow, so staff accordingly.
6. Safety to express over Safety to perform
7. You need not be part of every decision
8. Celebrate failures with learnings
9. Never feign ignorance
10. Groupism is a taboo
11. It’s ok to manufacture empathy
12. You should be seen as a solver at any point, especially when it comes to customer engagement
13. Trust is a glass vase, never break it
14. Collaboration over Collusion
15. Maintain tension at the right level to induce discomfort in to the system, only then innovation
happens.
16. Everyday think about next week, next month, next quarter and next two quarters
17. 1 : 1 is still relevant
18. Look for reverence displayed for skill ( not for exp )
19. Set and Monitor for Closer feedback loops
20. Work with a core team to the extent that they are not core because you work with them
21. Put a self worth for what you bring to the table - Like a program objective
22. Feedback cycles vary from seconds to months .. be cognizant of it to balance priorities
(Maha) Gyaan
Hinweis der Redaktion
Self organizing teams are at the core of Agile Principles, Let us take a look at some of them which deals with people. The highlighted words are my keyholes to look at these.
These interactions were spaced out and stages ensured quality gates were present
Any backward movement required lesser moderation / facilitation, if records were kept
When Technology helped business there was a tilt towards business, but when you have technology is the business its more of a even keel and it also hampers movement :-), this makes the PM job even more critical to hold the vision true.
Environment here, is about how people are set up to perform their best
Watch out for the persona types and their voices, be cognizant that all are doing their best and there are no good or bad types.
Be watchful to not box people in personalities.
Keep the chatter alive
Engage →
Determining a behaviour whether it’s beneficial or not is easy, let it be systems, process or people. Let the team decide for itself.
Behaviours are easily institutionalized or dropped if mooted and monitored by the team.
Build fixing, Pair rotations, Iteration planning, retrospectives, Release feedback are expected to bring about appreciable changes in behaviour
Mob behaviour is a good tool to get in people with indifferent working styles to fall in line.
Watch out for personalities to create & sustain movements.