The document discusses agile teams and scrum methodology. It describes that agile is broader than scrum and that agile teams don't have to use scrum. It also discusses the roles of product owner, scrum master and development team in scrum. It provides examples of scenarios that can destabilize teams and strategies for high performing distributed teams.
The document discusses the evolution of management over time. It describes how early companies did not have dedicated managers, but as companies grew larger problems arose regarding quality, integration, and motivation. This led to the emergence of many specialized manager roles to address these issues. However, managing problems and people directly can fix only symptoms, not root causes. Better management focuses on enabling purpose, autonomy, and mastery for self-organizing teams. The role of managers is to coach and empower teams rather than control them.
1) Management styles have evolved from direct control to facilitating self-organizing teams. Early managers directly managed tasks and problems but more effective modern managers focus on higher-level goals and enabling autonomy.
2) Two historical examples are the managers of The Beatles who took different approaches - one micro-managed while the other gave the band space to learn and organize themselves.
3) There are three types of modern managers - manager-entrepreneurs who own products, manager-facilitators who guide cross-functional teams, and manager-mentors who coach individuals. The most effective managers focus on purpose, mastery, and autonomy rather than controlling people and problems.
The document discusses the role and responsibilities of a Scrum Master. It describes how the Scrum Master facilitates the Scrum process and ceremonies like daily stand-ups, sprint planning and retrospectives. The Scrum Master also helps resolve impediments, enables self-organization of the team and protects the team from external interference. Key responsibilities include enforcing timeboxes, maintaining artifacts and metrics, and guiding the team on Agile best practices. The document provides checklists and guidelines for Scrum Masters to effectively perform their duties.
The survey captures information about a team's sprint planning and execution practices. It includes yes/no questions about the tools, processes, and participants involved in activities like sprint planning meetings, backlog management, daily standups, and retrospectives. The survey also prompts for additional details to understand how and why the team approaches certain agile practices the way they do.
This document provides an introduction to the Scrum framework presented by Céline Dedaj to the Geek Girls Carrots group. The workshop goals are to understand what Scrum is, how it works, why it is used, and get participant feedback. Scrum is explained as an iterative process involving sprints, daily stand-up meetings, sprint planning, reviews and retrospectives. Key Scrum roles of Product Owner, Scrum Master and cross-functional team are also outlined. The workshop concludes with a hands-on activity mimicking a sprint goal and process.
What is the rol of scrum master in Agile?Mario Lucero
The Scrum Master is responsible for facilitating the Scrum process and removing impediments for the team. They ensure that the team follows Scrum theory, practices and rules and helps everyone understand Scrum. The Scrum Master also protects the team from external interferences and shields them from distractions.
"Being Agile" presents an introduction to Scrum, an Agile software development methodology. In addition to the basics of the iterative development process and roles, this talk explores Agile concepts related to requirements, documentation, communication, planning, and overall business strategy.
Presented to Cedar Rapids IIBA 2/10/2010
The document discusses the evolution of management over time. It describes how early companies did not have dedicated managers, but as companies grew larger problems arose regarding quality, integration, and motivation. This led to the emergence of many specialized manager roles to address these issues. However, managing problems and people directly can fix only symptoms, not root causes. Better management focuses on enabling purpose, autonomy, and mastery for self-organizing teams. The role of managers is to coach and empower teams rather than control them.
1) Management styles have evolved from direct control to facilitating self-organizing teams. Early managers directly managed tasks and problems but more effective modern managers focus on higher-level goals and enabling autonomy.
2) Two historical examples are the managers of The Beatles who took different approaches - one micro-managed while the other gave the band space to learn and organize themselves.
3) There are three types of modern managers - manager-entrepreneurs who own products, manager-facilitators who guide cross-functional teams, and manager-mentors who coach individuals. The most effective managers focus on purpose, mastery, and autonomy rather than controlling people and problems.
The document discusses the role and responsibilities of a Scrum Master. It describes how the Scrum Master facilitates the Scrum process and ceremonies like daily stand-ups, sprint planning and retrospectives. The Scrum Master also helps resolve impediments, enables self-organization of the team and protects the team from external interference. Key responsibilities include enforcing timeboxes, maintaining artifacts and metrics, and guiding the team on Agile best practices. The document provides checklists and guidelines for Scrum Masters to effectively perform their duties.
The survey captures information about a team's sprint planning and execution practices. It includes yes/no questions about the tools, processes, and participants involved in activities like sprint planning meetings, backlog management, daily standups, and retrospectives. The survey also prompts for additional details to understand how and why the team approaches certain agile practices the way they do.
This document provides an introduction to the Scrum framework presented by Céline Dedaj to the Geek Girls Carrots group. The workshop goals are to understand what Scrum is, how it works, why it is used, and get participant feedback. Scrum is explained as an iterative process involving sprints, daily stand-up meetings, sprint planning, reviews and retrospectives. Key Scrum roles of Product Owner, Scrum Master and cross-functional team are also outlined. The workshop concludes with a hands-on activity mimicking a sprint goal and process.
What is the rol of scrum master in Agile?Mario Lucero
The Scrum Master is responsible for facilitating the Scrum process and removing impediments for the team. They ensure that the team follows Scrum theory, practices and rules and helps everyone understand Scrum. The Scrum Master also protects the team from external interferences and shields them from distractions.
"Being Agile" presents an introduction to Scrum, an Agile software development methodology. In addition to the basics of the iterative development process and roles, this talk explores Agile concepts related to requirements, documentation, communication, planning, and overall business strategy.
Presented to Cedar Rapids IIBA 2/10/2010
An Agile mindset believes that diverse teams with complementary skills are best equipped to thrive in today’s business environments.
Many organizations, working with Agile methodologies, talk about changing mindsets. I know from extensive experience that Agile principles and practices by themselves will not lead to this kind of transformation. A real Agile transformation is about not just doing Agile, but being Agile.
‘Follow Agile’ mindset will only help us get into the water but ‘Being Agile’ mindset will help us swim in the current. Most Agile implementations fail and their practitioners cannot tell why. Managers jump onto the Agile bandwagon, and quickly discover that the change runs much deeper and wider than they’d been told. Worse yet, people decide for or against Agile without understanding it properly. It does not have to be this way. This will be an interactive workshop leading toward the Agility.
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
It is the team who does all the work. Team is self-organising. Team decides and plans. So what is the role of scrum master? Is it a full time role? How is it different from a project manager? Can a project lead or manager be a scrum master? It is probably the least understood and the most abused role in scrum. Let's explore these points in details further on April 10, 3:00 PM.
3 Roles in Scrum
Role of scrum master
Challenges of a scrum master
Skills, Knowledge & mindset required
Full time or part time?
Future career path of scrum master
Benefits:
Uncover the true role of a scrum master which is that of a facilitator, protector, negotiator and a coach.
Understand the true meaning of coaching.
Learn how scrum master can coach the team.
Understand the skills, knowledge and mindset required as a scrum master.
Perform better as a scrum master by getting introduced to some magical techniques and fad words like gamestorming, innovation games and visual thinking to facilitate collaborative decision making.
Learn points which you can use to make people understand the vital role a scrum master plays.
Appreciate the difference between project manager and a scrum master.
Learn who can be a good scrum master.
Attend the webinar and separate yourself from the crazy herd of people blindly accepting or discarding the role of scrum master!!
The document discusses how perceptions of a Scrum Master's role can vary widely between different groups. It summarizes surveys that found 40% of organizations don't understand Scrum and 60% of teams don't have dedicated Scrum Masters. It emphasizes the importance for Scrum Masters to understand how others perceive their role in order to effectively facilitate Agile transformations.
Scrum Masters are core to creating an environment to help teams be as effective as possible. They are responsible for ensuring the team lives up to the Agile values and principles. The team is their primary focus.
What should a Scrum Master do when an individual on the team is struggling and the focus on the team is not an effective response?
Mentoring leverages skills that Scrum Masters practice every day but it is different in some key dimensions. This deck supports a conversation between Laura Richardson as she talked with Syndey Kimball, CSM about her mindset shift from Scrum Master to Mentor. The conversation was enriched by Monica Cassman, the mentee who worked directly with Sydney as they took the journey together.
The webinar covered:
1) Review the characteristics of the Certified ScrumMaster role
2) Explore the role of Mentor
3) Learn from Monica about how she benefited from the Mentor/Mentee relationship
4) Discuss steps that Scrum Masters can take to add Mentor skills and tools to their own toolkit
The document discusses various Agile concepts and myths. It covers topics like sprint planning, daily scrums, sprint reviews, retrospectives, and backlog refinement. For sprint planning, it recommends dividing it into three sections - discussing what needs to be done, estimating effort, and finalizing commitments. It provides guidance on running effective daily scrums, sprint reviews, and retrospectives in distributed teams. It also debunks several common myths around Agile practices.
There's been a lot of talk recently the benefits of on #agile adoption on non-development teams. In this presentation, first delivered at @ncwit, I explore the benefits of agile to #diversity and #inclusion
The document discusses key roles in Agile development including the Product Owner, Scrum Master, and Team Members. The Product Owner builds and manages the product backlog and ensures everyone understands the work. The Scrum Master coaches the team and resolves impediments. Team Members are ideally 5-7 cross-trained individuals who forecast work and help each other ensure success. Other important roles that interact with but are not part of the core team are also mentioned.
An introduction to the Scrum framework. If you are practicing agile or are looking to do complex projects in a quick iterative - Inspect & adapt cycles - you should evaluate scrum .
While working on Agile transformations, through multiple organisations, I have realized one common roadblock in achieving this vision; Managers. Read on to know why managers fear agile implementation
What are the characteristics of a good Scrum Team? Are you willing to be a Product Owner or Scrum Master? Are you wondering about the maturity of your development team? This presentation will give you insights about how the evolution of the development team, scrum master, and the product owner.
Safe Scrum Master
A person who leads and coaches Agile teams and helps train teams on Scrum, Extreme Programming (XP), Kanban, and Safe to ensure adherence to agreed Agile processes after completion of Scrum Master certification. It also helps to remove roadblocks and create an environment for strong team dynamics, continuous flow, and constant improvement.
This webinar is worth 1 PDU. The recorded webinar and presentation slides will be made available online after the session. Information will be provided on how to claim your PDU and access the materials. The webinar will cover several topics related to adopting agile practices, including the manager's role in scrum, working with offshore teams, scaling agile, and addressing cultural issues.
AGILE! Who cares - Tell me what to do @ADC2014Suman Guha
"AGILE! Who cares - Tell Me What To Do. " I presented this at Agile Day Conference 2014 in Pune, India http://www.agiledayconference.com/conference-in-pune
I bet you have encountered this title in your role (e.g. Agile Coach or Mentor) when helping teams in transitioning to Agile. So I did encounter this too and in one such discussion, Chris (Principal Architect) asked me to share my thoughts on handling a Scrum team who simply wanted to be “told what to do”. On the surface, this doesn't seem like such a bad thing. In fact, I’ll bet these folks are bright, capable and work very hard. So if there is an issue with this in agile teams, what is it? And why would it be a problem? Hence this session is about "Transitioning to Agile".
Safe Scrum Master
A person who leads and coaches Agile teams and helps train teams on Scrum, Extreme Programming (XP), Kanban, and Safe to ensure adherence to agreed Agile processes after completion of the Scrum Master certification process. It also helps to remove roadblocks and create an environment for strong team dynamics, continuous flow, and constant improvement.
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
This document discusses how Agile has become outdated or "dead" due to misinterpretations and misapplications over time. The author argues that many companies claim to be Agile but are actually focused on processes and tools rather than outcomes. True Agility values individuals, interactions, working software, and responding to change. The author suggests companies need to refocus on delivering value to customers rather than following rigid practices. Overall, the document criticizes a "cargo cult" mentality around Agile and advocates returning to its original principles of empowering individuals, collaboration, and continuous improvement.
A Guide to a Winning Interview June 2024Bruce Bennett
This webinar is an in-depth review of the interview process. Preparation is a key element to acing an interview. Learn the best approaches from the initial phone screen to the face-to-face meeting with the hiring manager. You will hear great answers to several standard questions, including the dreaded “Tell Me About Yourself”.
An Agile mindset believes that diverse teams with complementary skills are best equipped to thrive in today’s business environments.
Many organizations, working with Agile methodologies, talk about changing mindsets. I know from extensive experience that Agile principles and practices by themselves will not lead to this kind of transformation. A real Agile transformation is about not just doing Agile, but being Agile.
‘Follow Agile’ mindset will only help us get into the water but ‘Being Agile’ mindset will help us swim in the current. Most Agile implementations fail and their practitioners cannot tell why. Managers jump onto the Agile bandwagon, and quickly discover that the change runs much deeper and wider than they’d been told. Worse yet, people decide for or against Agile without understanding it properly. It does not have to be this way. This will be an interactive workshop leading toward the Agility.
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
It is the team who does all the work. Team is self-organising. Team decides and plans. So what is the role of scrum master? Is it a full time role? How is it different from a project manager? Can a project lead or manager be a scrum master? It is probably the least understood and the most abused role in scrum. Let's explore these points in details further on April 10, 3:00 PM.
3 Roles in Scrum
Role of scrum master
Challenges of a scrum master
Skills, Knowledge & mindset required
Full time or part time?
Future career path of scrum master
Benefits:
Uncover the true role of a scrum master which is that of a facilitator, protector, negotiator and a coach.
Understand the true meaning of coaching.
Learn how scrum master can coach the team.
Understand the skills, knowledge and mindset required as a scrum master.
Perform better as a scrum master by getting introduced to some magical techniques and fad words like gamestorming, innovation games and visual thinking to facilitate collaborative decision making.
Learn points which you can use to make people understand the vital role a scrum master plays.
Appreciate the difference between project manager and a scrum master.
Learn who can be a good scrum master.
Attend the webinar and separate yourself from the crazy herd of people blindly accepting or discarding the role of scrum master!!
The document discusses how perceptions of a Scrum Master's role can vary widely between different groups. It summarizes surveys that found 40% of organizations don't understand Scrum and 60% of teams don't have dedicated Scrum Masters. It emphasizes the importance for Scrum Masters to understand how others perceive their role in order to effectively facilitate Agile transformations.
Scrum Masters are core to creating an environment to help teams be as effective as possible. They are responsible for ensuring the team lives up to the Agile values and principles. The team is their primary focus.
What should a Scrum Master do when an individual on the team is struggling and the focus on the team is not an effective response?
Mentoring leverages skills that Scrum Masters practice every day but it is different in some key dimensions. This deck supports a conversation between Laura Richardson as she talked with Syndey Kimball, CSM about her mindset shift from Scrum Master to Mentor. The conversation was enriched by Monica Cassman, the mentee who worked directly with Sydney as they took the journey together.
The webinar covered:
1) Review the characteristics of the Certified ScrumMaster role
2) Explore the role of Mentor
3) Learn from Monica about how she benefited from the Mentor/Mentee relationship
4) Discuss steps that Scrum Masters can take to add Mentor skills and tools to their own toolkit
The document discusses various Agile concepts and myths. It covers topics like sprint planning, daily scrums, sprint reviews, retrospectives, and backlog refinement. For sprint planning, it recommends dividing it into three sections - discussing what needs to be done, estimating effort, and finalizing commitments. It provides guidance on running effective daily scrums, sprint reviews, and retrospectives in distributed teams. It also debunks several common myths around Agile practices.
There's been a lot of talk recently the benefits of on #agile adoption on non-development teams. In this presentation, first delivered at @ncwit, I explore the benefits of agile to #diversity and #inclusion
The document discusses key roles in Agile development including the Product Owner, Scrum Master, and Team Members. The Product Owner builds and manages the product backlog and ensures everyone understands the work. The Scrum Master coaches the team and resolves impediments. Team Members are ideally 5-7 cross-trained individuals who forecast work and help each other ensure success. Other important roles that interact with but are not part of the core team are also mentioned.
An introduction to the Scrum framework. If you are practicing agile or are looking to do complex projects in a quick iterative - Inspect & adapt cycles - you should evaluate scrum .
While working on Agile transformations, through multiple organisations, I have realized one common roadblock in achieving this vision; Managers. Read on to know why managers fear agile implementation
What are the characteristics of a good Scrum Team? Are you willing to be a Product Owner or Scrum Master? Are you wondering about the maturity of your development team? This presentation will give you insights about how the evolution of the development team, scrum master, and the product owner.
Safe Scrum Master
A person who leads and coaches Agile teams and helps train teams on Scrum, Extreme Programming (XP), Kanban, and Safe to ensure adherence to agreed Agile processes after completion of Scrum Master certification. It also helps to remove roadblocks and create an environment for strong team dynamics, continuous flow, and constant improvement.
This webinar is worth 1 PDU. The recorded webinar and presentation slides will be made available online after the session. Information will be provided on how to claim your PDU and access the materials. The webinar will cover several topics related to adopting agile practices, including the manager's role in scrum, working with offshore teams, scaling agile, and addressing cultural issues.
AGILE! Who cares - Tell me what to do @ADC2014Suman Guha
"AGILE! Who cares - Tell Me What To Do. " I presented this at Agile Day Conference 2014 in Pune, India http://www.agiledayconference.com/conference-in-pune
I bet you have encountered this title in your role (e.g. Agile Coach or Mentor) when helping teams in transitioning to Agile. So I did encounter this too and in one such discussion, Chris (Principal Architect) asked me to share my thoughts on handling a Scrum team who simply wanted to be “told what to do”. On the surface, this doesn't seem like such a bad thing. In fact, I’ll bet these folks are bright, capable and work very hard. So if there is an issue with this in agile teams, what is it? And why would it be a problem? Hence this session is about "Transitioning to Agile".
Safe Scrum Master
A person who leads and coaches Agile teams and helps train teams on Scrum, Extreme Programming (XP), Kanban, and Safe to ensure adherence to agreed Agile processes after completion of the Scrum Master certification process. It also helps to remove roadblocks and create an environment for strong team dynamics, continuous flow, and constant improvement.
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
This document discusses how Agile has become outdated or "dead" due to misinterpretations and misapplications over time. The author argues that many companies claim to be Agile but are actually focused on processes and tools rather than outcomes. True Agility values individuals, interactions, working software, and responding to change. The author suggests companies need to refocus on delivering value to customers rather than following rigid practices. Overall, the document criticizes a "cargo cult" mentality around Agile and advocates returning to its original principles of empowering individuals, collaboration, and continuous improvement.
Similar to Agilni timovi startit 7. februar 2019. (20)
A Guide to a Winning Interview June 2024Bruce Bennett
This webinar is an in-depth review of the interview process. Preparation is a key element to acing an interview. Learn the best approaches from the initial phone screen to the face-to-face meeting with the hiring manager. You will hear great answers to several standard questions, including the dreaded “Tell Me About Yourself”.
Leadership Ambassador club Adventist modulekakomaeric00
Aims to equip people who aspire to become leaders with good qualities,and with Christian values and morals as per Biblical teachings.The you who aspire to be leaders should first read and understand what the ambassador module for leadership says about leadership and marry that to what the bible says.Christians sh
Resumes, Cover Letters, and Applying OnlineBruce Bennett
This webinar showcases resume styles and the elements that go into building your resume. Every job application requires unique skills, and this session will show you how to improve your resume to match the jobs to which you are applying. Additionally, we will discuss cover letters and learn about ideas to include. Every job application requires unique skills so learn ways to give you the best chance of success when applying for a new position. Learn how to take advantage of all the features when uploading a job application to a company’s applicant tracking system.
5. @jazilla @agilehumans
Agile V Scrum
● Agilno je šire od Scruma
● Agilni timovi ne moraju biti nužno Scrum timovi
● Kažu da su dizajnirani tako povećaju fleksibilnost, kreativnost i produktivnost?
13. @jazilla @agilehumans
Agilno je kultura
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
● Individuals and interactions over processes and tools
● Working software over comprehensive documentation
● Customer collaboration over contract negotiation
● Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
14. @jazilla @agilehumans
Svaki tim koji uspeva da...
● isporučuje (valuable) proizvod rano, često i kontinuirano
● prihvata i integriše promene zahteva (welcoming change), čak i one kasne
● dnevno sarađuje sa poslovnim sektorom
● poklanja pažnju tehničkoj izvrsnosti i dobrom dizajnu
● komunicira efikasno/efektivno (face-to-face)
● sam se organizuje
● veruje da je softver koji radi glavna mera uspeha
● čuva motivaciju članova tima
● ima sistem inspect i adapt i u pogledu ponašanja u timu (retrospektiva)
● ume da razdvoji “žito od kukolja” i maksimizuje količinu neurađenog posla
15. @jazilla @agilehumans
Last but not Least
Agilan tim je onaj tim koji ima podršku.
Agini tim je onaj tim kom se ukazuje poverenje “to get the job done”.
Agilan tim je onaj koji dobro razume prve vrednost Agilnog manifesta.
19. @jazilla @agilehumans
Scrum Master Role - Responsibilities
● Promoting and supporting Scrum by helping everyone
understand Scrum theory, practices, rules and values (coaching,
explaining the rules)
● Ensuring that the team is fully functional and productive
● Removing the barriers, increasing transparency, and the culture
inspect and adapt
● Enabling close cooperation across all roles and functions
● Inviting to ceremonies, facilitating Scrum events
● Shielding the team from external interferences
20. @jazilla @agilehumans
Product Owner Role - Responsibilities
● The sole person responsible for managing the Product Backlog
● Represents and manages stakeholders
● Responsible for maximizing the value of the product - for ROI
● Presents and clarifies the product vision to the dev team
● Prioritizes the product backlog, stays open to negotiation
● Empowers the team, stays engaged
● Accepts or rejects work results
● Manages uncertainty and maintains commitment: can remove but
can't add work during the iteration
21. Development Team
The Development Team consists of
professionals who do the work of delivering
a potentially releasable Increment of “Done”
product at the end of each Sprint
Only members of the Development
Team create the Increment
22. Development Team - Responsibilities
● Self-organized - nobody (not even the Scrum Master) tells the Development Team
how to turn Product Backlog into Increments of potentially releasable functionality
○ The team estimates how much time
○ The team decides how much work it can do in an iteration
○ The team decides how to do work in an iteration
○ The team measures its own performance
● Cross-functional, with all the skills as a team necessary to create a product
Increment
○ There are no sub-teams
○ If too small, decreased interaction and skill constraints
○ If more than 9, requires too much coordination and complexity
23. Daily Scrum from Hell
Game
● Jedan Scrum Master
● 7-8 članova tima
● Svako ima zadatak kako da minira Daily
● 1 ima zadatak da odgovori kako treba
● Ostali posmatraju i pokušavaju da shvate ulogu
24. @jazilla @agilehumans
Distributed Teams
● Use tools that provide visibility and
sharing
● Organize face-to-face meetings
whenever possible
● Establish available hours with as
much overlap as possible Co-locate
team as often as possible.
● Don’t let anyone go dark.
26. @jazilla @agilehumans
High Performing Teams
Google Teams
https://www.inc.com/leigh-buchanan/most-productive-teams-at-google.html
The data demonstrate psychological safety is critical, said Welle.
26
Psychological safety Members feel they can be vulnerable. They know their ideas and opinions will be respected
and considered, even when they conflict with those of the rest of the team.
Dependability Members are confident their coworkers will deliver what they are supposed to when they are
supposed to.
Structure and clarity Members understand their roles and the roles of others, and the goals of the team overall.
Meaning Members feel that what they are working on is important to them personally.
Impact Members believe what they are doing will have a positive effect on the organization and the
world.
35. @jazilla @agilehumans
Pravila
● učesnici se grupišu u timove od 7
● svaki član tima ima svoj broj od 1 do
7 (član tima br. 1, član tima br. 2. itd.)
● svaki učesnik hvata konopac po
krugu s obe ruke
● učesnici prave mrežu od konopca
ukršaćuji ga međusobno, mreža
treba da može da nosi balon
● asistenti stavljaju balon na mrežu.
Zadatak tima je da ne dozvoli da
balon stagnira niti padne ni u jednom
scenariju koji kreira fasilitator.
●
36. @jazilla @agilehumans
Fasilitator i scenarija
Fasilitator vodi timove kroz niz scenarija i
aktivnosti.
U svakom scenariju, tim prati instrukcije koje
daje fasilitator trudeći se zadrži balon na mreži.
U svakom scenariju balon treba da bude u
laganom pokretu kao i svi timovi.
37. @jazilla @agilehumans
Svrha
● iskustvo podeljene odgovornosti
● ilustracija tima kao sistema u kom svaki deo utiče na sve druge delove
● otkriva nezdravu dinamiku tima
● ilustruje kroz igru neke efekte disfunkcionalnog ponašanja u timu
● lako se prenosi u realan svet i dobra je osnova za diskusiju
38. @jazilla @agilehumans
Scenario broj 1
Član tima broj 1 misli da sve mora da uradi sam. Bez njega će se sve raspasti.
Član tima broj 1 preuzima na sebe 130% odgovornosti i vuče konopac na svoju
stranu.
Član tima broj 1. Kaže sebi: Moram sve sam. Propašće bez mene. I vuče, vuče da
što više postigne.
39. @jazilla @agilehumans
Scenario broj 2
Član tima broj 2 je preumoram, smoren. Samo što nije dao otkaz. Prepušta
odgovornost drugima i labavo drži konopac, sporo se kreće, pruža otpor.
40. @jazilla @agilehumans
Scenario broj 3
Članovi tima 3 i 6 imaju konflikt i svako vuče na svoju stranu držeći čvrsto
konopac.
Istovremeno,
član tima broj 4 napušta svoj tim i pridružuje se drugom timu jer je ekspert i
potreban je drugom timu na kratko.
Članovi timova broj 4 napustite svoje timove i pridružite se drugom timu.
Članovi timova 3 i 6 i dalje vuku svak na svoju stranu.
41. @jazilla @agilehumans
Scenario broj 4
Članovi timova 5 i 7 menjaju uloge.
Članovi timova 5 i 7 promenite mesto.
Istovremeno, član tima 1 je ekspert potreban i drugom timu. Počinje da radi u dva
tima istovremenom.
Član tima 1 pušta konopac jednom rukom i hvata konopac drugog tima tom
rukom.
42. @jazilla @agilehumans
Scenario 5
Član tima broj 3 i 5 rade remotely.
Članovi timova 3 i 5, zažmurite.
Istovremeno, član tima broj 4 vraća se u stari tim.
43. @jazilla @agilehumans
Diskusija
Ovo je zaista moćna igra za dramatizaciju onoga što se dešava timovima koji nisu
usaglašeni ili im spoljašnji faktori ne dopuštaju da se fokusiraju na cilj.
Razmislite o tome kako scenarija iz igre odražavaju realan život.
● Kako su promene uticale na tim?
● Šta konopci simbolizuju?
● Ima li ličnosti sa realnim načinom rada?
● Da li smo prisutni u timu na način koji želimo i koji služi svrsi?
● Kako se brinemo o zajedničkom cilju?
● Kakva bolna zapažanja našeg trenutnog načina rada postaju vidljiva?
● Šta bismo promenili i kako?
45. @jazilla @agilehumans
Any Given Sunday
Tony D'Amato (Al Pacino) delivers his
inspirational "Inches" speech in the 1999
film Any Given Sunday.
“Either we heal as a team or we gonna
crumble.”
“I can’t make you do it. You gotta look at
the guy next to you. Look into his eyes.
Now I think you gonna see a guy who will
go that inch with you. You’re gonna see a
guy who will sacrifice himself for this team
because he knows when it comes down to
it you’re gonna do the same for him.
That’s a team, gentlemen!”
45