We will continue our agile transformation with a short recap of previous 2 meetups "The Agile Mindset" and "Agile processes and frameworks", and then quickly continue to talk about the agile roles and how these roles will be fit in side the organization.
This is session 3 out of 5 sessions with the goal to help all who joins to get started with an Agile transformation.
6. Agile Principles About Teamwork
❏ 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 best architectures, requirements, and designs emerge from self-
organizing teams.
7. Agile is a team approach
● Self organizing teams
● Cross functional teams
● Motivated Teams
https://www.mountaingoatsoftware.com/blog/self-organizing-teams-are-not-put-together-randomly
https://www.mountaingoatsoftware.com/blog/cross-functional-doesnt-mean-everyone-can-do-everything
12. Manager VS Leader
● Drive vs Coach
● Taking Decisions vs Facilitating Decisions
● Managing people vs Managing Work
● Monitor vs Trust
● Extrinsic motivation vs Intrinsic motivation
● Develop products vs Develop team who develop product
Agility – Ability to move quickly
Business Agility
Agile Manifesto and principles
What value we are getting from agile
Doing VS Being Agile
Scrum Basic – Sprints, Events, Team Size, Work Increment, ROI (early value)
Kanban Basic – Flexibility, Certainty, WIP limit
Scaling – Why scaling: What happens when team size increases
Our conclusion is agile is a team approach. Which kind of team we need to be successful in agile environment.
Self-Organizing Team:
The best architectures, requirements and designs emerge from self-organizing teams.
It’s the Ability, every human being have it.
Encourage Shared Responsibility and Decisions
Believe on Collected wisdom
Things out of responsibility of the self-organizing team
Goal
Team organization
HR
etc.
Cross functional Team:
Business people and developers must work together daily.
Varity of skills people
Enough skills to do their job without external dependencies
Not every member is cross functional
May have specialist
Imagine the team of 10 people (Mike Cohn Example)
Component vs functional teams
Motivation:
Build projects around motivated individuals.
Autonomy
Mastery --- Seeking Knowledge – continuous improvement --- Myth about agile about skills
Purpose --- Story Why cutting woods
Daniel Pink Reference: Carrot and tick not works for agile.
Balance between autonomy and alignment – Spotify
Product Owner
Set the product Vision and direction
Groom the stories with the team
Prioritize the backlog items
Maximize the value of team work
Define Sprint Goal
Development Team
Pull the work from backlog in sprint
Cross functional team does end to end development work
T shaped team
Scrum Master
Guide the team in scrum practices
Guide the product owner about
Remove Impedance
Developers:
Decide what to do
Write tests
Code Reviews
Customer:
What to do
Write user stories
Decision Maker
Confident
Tester:
Helping Customer to write functional test cases
Runs functional tests
Tracker:
Monitoring Estimates
Get information without interruptions
Coach:
Process keeper
Consultant and Managers:
Supporting Roles
How team works in Kanban. WIP limit. Resolve Bottlenecks. Visibility
Spotify Engineering culture, Tribes, Chapter Guild
Bottom Up Approach, Shu Ha Ri
