Estimations: stop asking when
Download as PPTX, PDF10 likes24,973 views
仂从仍舒亟 从仂仆亠亠仆亳亳 SQA Days 2013 仂 仗亳仂仍仂亞亳亳 仂亠仆亳于舒仆亳亳 仂从仂于.
1 of 87
Downloaded 24 times
Recommended
弌亠亞亠亶 仂亠于 仂亳 仆仂于亠 仂亳弍从亳 亳 仂 亰仆舒仍 仗仂 仄亠仆亠亟亢仄亠仆 亰舒 仗仂亠亟亳亶 亞仂亟
弌亠亞亠亶 仂亠于 仂亳 仆仂于亠 仂亳弍从亳 亳 仂 亰仆舒仍 仗仂 仄亠仆亠亟亢仄亠仆 亰舒 仗仂亠亟亳亶 亞仂亟404fest
油
仂于亶 亳仆亠仍仍亠从舒仍仆亶 亳仗亳亰. 亠亠亟仆舒 仗弍仍亳仆舒 亳仗仂于亠亟. 弌于亠亢亳亠 仍亠亰 舒从舒礌亳. 丐舒亟亳亳仂仆仆仂亠 仂仗亠仆亳亠 亞亠仂于.
http://2014.404fest.ru/reports/new-mistakes/
10 things to drive your meetings nuts
10 things to drive your meetings nutsAlexey Krivitsky
油
The document lists 10 things you can do to drive your meeting nuts: 1) Accept invitations for overlapping meetings, 2) Come late with coffee, 3) Finish other conversations, 4) Keep your laptop open for other tasks, 5) Never interrupt the speaker, 6) Dominate discussions when given a mic, 7) Check your phone for updates, 8) Avoid follow-up tasks, 9) Try to use all the scheduled meeting time for other topics, and 10) Leave early for your next meeting. The author suggests these behaviors undermine meetings and disrupt collaboration.Agile Coaching Canvas
Agile Coaching CanvasAlexey Krivitsky
油
This document discusses focused agile coaching. It encourages coaches to develop a clear vision and plan for their coaching work. It discusses establishing a coaching product and techniques like helping teams adopt Scrum from zero. The document also discusses starting coaching where teams currently are and focusing on key areas like business involvement, teamwork, and engineering processes. It provides exercises for coaches to navigate these areas and dream big with the teams they support. Finally, it discusses coaching skills and an Agile Coaching Canvas tool to help plan coaching sessions.How to grow learning multi-site agile organizations
How to grow learning multi-site agile organizationsAlexey Krivitsky
油
What is making organizations so complex and slow? Why an "enterprise" is an equivalent to "inefficient"? How to de-scale organizations? There is no easy answers. But understanding the internal system dynamics is the key skill here.Certified ScrumMaster: class desk, posters and photos
Certified ScrumMaster: class desk, posters and photosAlexey Krivitsky
油
This document provides an overview of agile principles and the role of a ScrumMaster. It discusses concepts like Lean, Kanban, the eight wastes, and Scrum ceremonies. It emphasizes that Scrum is based on empirical process control and focuses on transparency, inspection, and adaptation. The role of the ScrumMaster is explained as a coach, facilitator, and servant leader who helps the team improve continuously. Their goal is to help the team and organization become more self-organizing and deliver value to customers.Advanced Scrum
Advanced ScrumStephan Janssen
油
This document provides an overview of Advanced Scrum concepts and practices. It discusses Agile values like prioritizing individuals, interactions, and working software over processes, documentation, and contract negotiation. Scrum is presented as a tool that delivers working software and flexibility. Key Scrum processes like retrospectives, product ownership, estimations, user stories, task boards, forecasting and planning are summarized. Scaling Scrum through techniques like Scrum of Scrums is also covered. The benefits of cross-functional teams are explained.Agile Coaching Canvas: dream up, co-create and share your agile coaching visi...
Agile Coaching Canvas: dream up, co-create and share your agile coaching visi...Alexey Krivitsky
油
This document outlines an "Agile Coaching Canvas" workshop for developing an agile coaching vision. It introduces the facilitator, Alexey Krivitsky, and describes his background. The workshop helps participants explore their dreams and challenges in four areas of agile coaching: navigating the present, visioning the future, and detailing the path. Participants are guided through exercises to explore a current coaching challenge, envision the future, and identify skills and support needed to achieve their vision. The facilitator hopes the workshop will help reconnect participants with their dreams and drive new changes in their coaching practice.Agile Coaching Canvas at #agile2016
Agile Coaching Canvas at #agile2016Alexey Krivitsky
油
This document outlines Alexey Krivitsky's Agile Coaching Canvas, which is intended to help agile coaches dream, co-create, and share their coaching vision. It discusses the daily work of a Scrum Master compared to the broader impact of agile coaching. It prompts coaches to explore four areas - their usual focus, comfort zone, stretch area, and area needing attention. Coaches are encouraged to think of a real coaching situation and discuss how it relates to the four areas. The document emphasizes listening without judgment to understand others and asking open-ended questions to help explore. It has coaches envision visiting their company in the future after achieving their dreams to see what has changed.Understanding Complexity of Organizational and System Dynamics
Understanding Complexity of Organizational and System DynamicsAlexey Krivitsky
油
This document discusses understanding complexity in organizational and system dynamics. It provides examples of causal loop diagrams that can be used to model cause-and-effect relationships within a system. It also discusses strategies for driving transformation, such as understanding current system dynamics, designing experiments to test new approaches, facilitating formation of new team structures, and establishing coordination practices. The goal is to holistically change parts of the existing system to create a new product organization.Complexity of organizational design and its effect scaling agility
Complexity of organizational design and its effect scaling agilityAlexey Krivitsky
油
This document discusses the complexity of large organizations and its effect on scaling agility. As organizations grow, they typically add more roles, meetings, documentation and managers, which increases indirection and coordination needs. This added complexity can lead to uneven workloads, out-of-sync development, and a focus on process over work. The document proposes organizing for value delivery through high alignment, clear constraints and high autonomy as a way to reduce complexity and improve agility at scale. It provides examples of structuring products and teams to optimize for customer value.Studying organizational complexity and its effects on scaling agility
Studying organizational complexity and its effects on scaling agilityAlexey Krivitsky
油
This document discusses the complexity of organizations and how it affects their ability to scale agility. It explores how inherent technical complexity and added complexity from factors like specialization can increase coordination needs. It also examines how organizations often try to manage this complexity by adding roles like managers, which paradoxically increases complexity further. The document advocates studying an organization's dynamics to better understand these complexity issues and proposes variables like cycle time, quality, work in progress to analyze.Agile Software Development With SCRUM
Agile Software Development With SCRUMAlexey Krivitsky
油
Materials from one-day training on Agile Software Development with SCRUM done by SCRUMguids.com in Kharkiv, Ukraine
Jan 2009Certified Scrum Product Owner: class desk, posters and photos
Certified Scrum Product Owner: class desk, posters and photosAlexey Krivitsky
油
The document provides an overview of agile product management and scrum. It discusses key concepts like lean, agile, scrum roles and artifacts, ceremonies like sprints and planning, and topics like minimum viable products, user stories, prioritization techniques, and product backlog refinement. The document is a training guide or presentation on agile product management best practices.Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...Alexey Krivitsky
油
Is Agile dead? It depends on what you mean by 'Agile'. If you mean that the organizations are not getting the promised benefits because they were focusing too much on the team-level agile "ways of working" instead of systemic global improvements -- then we are in agreement. It is a misunderstanding of Agility that led us down a dead-end. At Org Topologies, we see bright sparks -- the signs of the 'second wave of Agile' as we call it. The emphasis is shifting towards both in-team and inter-team collaboration. Away from false dichotomies. Both: team autonomy and shared broad product ownership are required to sustain true result-oriented organizational agility. Org Topologies is a package offering a visual language plus thinking tools required to communicate org development direction and can be used to help design and then sustain org change aiming at higher organizational archetypes.Strategic Org Design with Org Topologies
Strategic Org Design with Org TopologiesAlexey Krivitsky
油
Org Design is a core skill to be mastered by management for any successful org change.
Org Topologies in its essence is a two-dimensional space with 16 distinctive boxes - atomic organizational archetypes. That space helps you to plot your current operating model by positioning individuals, departments, and teams on the map. This will give a profound understanding of the performance of your value-creating organizational ecosystem.Driving the second wave of Agile revolution with #OrgTopologies
Driving the second wave of Agile revolution with #OrgTopologiesAlexey Krivitsky
油
This document discusses improving organizations beyond team-level agility. It argues that while agile practices at the team level have benefits, they have limited impact without broader organizational changes. The document advocates for redefining value more broadly across the organization, enriching teams through more customer interaction, upgrading management practices, and using Scrum to inspect and adapt organization-wide. This would help organizations design value-creating ecosystems and move to higher architecture types with benefits like multi-team learning, whole-product focus, and reduced complexity.Org Topologies at Scrum Day Europe 2022, Amsterdam
Org Topologies at Scrum Day Europe 2022, AmsterdamAlexey Krivitsky
油
Organizational Topologies: your roadmap towards an innovative, resilient and adaptive product development organization.
Many organizations struggle to adopt "agile" in a way that delivers on its promise to make the company fast, flexible and efficient.
Global consultancy firms have great pitches on how to adopt different so-called Agile frameworks. The marketing is great, but are the results too? We see how our clients get stuck in adopting a framework - forming agile teams, appointing product owners and then clustering all this into tribes. Thus creating robust structures that make further organizational improvements and adaptability difficult, slow, and expensive.
This talk offers ideas how to go beyond these limiting ideas and explores a map of organizational transformation based on orgtopologies.com.Organizational Topologies: a roadmap towards a resilient and adaptive product...
Organizational Topologies: a roadmap towards a resilient and adaptive product...Alexey Krivitsky
油
This document introduces the Adaptivity Map, which provides a roadmap for organizational transformation towards being adaptive and agile. The map shows different stages of organizational topology labeled A1 through C3, with the goal of C3 being optimal value delivery across the whole product. It emphasizes that true transformation requires paradigm shifts in how the organization works, such as establishing cross-functional teams or taking full responsibility for end-to-end delivery. Jumping directly to later stages like C3 from A2 can be an effective approach for organizations with around 50 people. The map is intended as a guide rather than a mandatory process, as transformations will vary in approach and speed depending on each organization's needs.Improve your Product Backlog Refinement (PBR) Process
Improve your Product Backlog Refinement (PBR) ProcessAlexey Krivitsky
油
The document provides guidance on conducting effective Product Backlog Refinement sessions, including splitting user stories, estimating effort, focusing on business value, and collaborating with stakeholders. It emphasizes refining items into testable increments and considering both positive and negative scenarios to ensure stories are appropriately sized. Stakeholders should be engaged as collaborators to provide input and help the team learn.#lego4scrum with Large-Scale Scrum (LeSS)
#lego4scrum with Large-Scale Scrum (LeSS)Alexey Krivitsky
油
This document describes a simulation exercise for practicing Large-Scale Scrum (LeSS) using LEGO and other materials. Participants will build a transportation business connecting European cities using LEGO sets for buses, buildings, and terrain materials. The goal is for teams to work together profitably to meet customer demands for transportation between cities. The document outlines setting up cross-functional teams, area product owners, an initial product backlog refinement, and sprint planning and execution for the simulation.Culture follows structure
Culture follows structureAlexey Krivitsky
油
This document discusses how organizational structure impacts culture. It argues that culture emerges from and is shaped by structural decisions over time, according to the principle that "culture follows structure". Several examples are provided of how specific structural decisions around teams, roles, and domains can influence cultural behaviors, habits, and norms. Systems thinking concepts are introduced to analyze the dynamic interrelationships between variables like quality, cycle time, motivation that are affected by structural changes.Powerful interventions for agile coaching
Powerful interventions for agile coachingAlexey Krivitsky
油
Workshop by Alexey Krivitsky on challenging status quo and adopting the "Kaikaku" thinking.LeSS simulation with LEGO at #agileee 2017. (lego for scrum)
LeSS simulation with LEGO at #agileee 2017. (lego for scrum)Alexey Krivitsky
油
This document provides an overview of a LEGO simulation of Large-Scale Scrum (LeSS). It discusses key principles of LeSS including customer focus, lean thinking, empowered teams, transparency, and constant learning. It outlines the product being built, which is a transportation system connecting European cities using LEGO sets. It also describes the initial setup process for the LeSS framework simulation including forming cross-functional teams, refining product backlogs, and getting ready for the first sprint.Dejirafication: free your process from tools
Dejirafication: free your process from toolsAlexey Krivitsky
油
The document discusses issues with over-reliance on Jira and backlog management tools in meetings, calling this "Jirandicitis". It proposes a "jira rehab program" with techniques like using mind maps instead of lists, just-in-time story creation, shuffling groups for backlog refinement, and lean coffee discussions to reduce tool dependence and improve collaboration.Dejirafication - clean your process
Dejirafication - clean your processAlexey Krivitsky
油
The document discusses "dejirafication", or freeing product development processes from over-reliance on Jira and other backlog management tools. It argues that meetings often become focused on updating the tool rather than team collaboration. The author proposes a "jira rehab program" using paper artifacts instead of Jira, including mind maps for themes, just-in-time story slicing, mixed group backlog refinement, and lean coffee discussions with confidence voting. Following these steps is said to make meetings more lively and focused on shared understanding rather than tool updates.Agile and Scrum for ORSCers
Agile and Scrum for ORSCersAlexey Krivitsky
油
1. The document introduces Agile and Scrum frameworks for system workers, focusing on teamwork, working products, customers, and adapting through inspection.
2. It discusses how work has evolved from individual tasks to complex projects requiring collaboration and knowledge workers. Traditional command structures are replaced with coaching to empower teams.
3. Key aspects of Agile include cross-functional teams that work together long-term, transparency through daily stand-ups and information boards, and continuous learning rather than post-mortem reviews. Departments shift to flexible teams that think about systems rather than just individual jobs.More Related Content
Viewers also liked (9)
Certified ScrumMaster: class desk, posters and photos
Certified ScrumMaster: class desk, posters and photosAlexey Krivitsky
油
This document provides an overview of agile principles and the role of a ScrumMaster. It discusses concepts like Lean, Kanban, the eight wastes, and Scrum ceremonies. It emphasizes that Scrum is based on empirical process control and focuses on transparency, inspection, and adaptation. The role of the ScrumMaster is explained as a coach, facilitator, and servant leader who helps the team improve continuously. Their goal is to help the team and organization become more self-organizing and deliver value to customers.Advanced Scrum
Advanced ScrumStephan Janssen
油
This document provides an overview of Advanced Scrum concepts and practices. It discusses Agile values like prioritizing individuals, interactions, and working software over processes, documentation, and contract negotiation. Scrum is presented as a tool that delivers working software and flexibility. Key Scrum processes like retrospectives, product ownership, estimations, user stories, task boards, forecasting and planning are summarized. Scaling Scrum through techniques like Scrum of Scrums is also covered. The benefits of cross-functional teams are explained.Agile Coaching Canvas: dream up, co-create and share your agile coaching visi...
Agile Coaching Canvas: dream up, co-create and share your agile coaching visi...Alexey Krivitsky
油
This document outlines an "Agile Coaching Canvas" workshop for developing an agile coaching vision. It introduces the facilitator, Alexey Krivitsky, and describes his background. The workshop helps participants explore their dreams and challenges in four areas of agile coaching: navigating the present, visioning the future, and detailing the path. Participants are guided through exercises to explore a current coaching challenge, envision the future, and identify skills and support needed to achieve their vision. The facilitator hopes the workshop will help reconnect participants with their dreams and drive new changes in their coaching practice.Agile Coaching Canvas at #agile2016
Agile Coaching Canvas at #agile2016Alexey Krivitsky
油
This document outlines Alexey Krivitsky's Agile Coaching Canvas, which is intended to help agile coaches dream, co-create, and share their coaching vision. It discusses the daily work of a Scrum Master compared to the broader impact of agile coaching. It prompts coaches to explore four areas - their usual focus, comfort zone, stretch area, and area needing attention. Coaches are encouraged to think of a real coaching situation and discuss how it relates to the four areas. The document emphasizes listening without judgment to understand others and asking open-ended questions to help explore. It has coaches envision visiting their company in the future after achieving their dreams to see what has changed.Understanding Complexity of Organizational and System Dynamics
Understanding Complexity of Organizational and System DynamicsAlexey Krivitsky
油
This document discusses understanding complexity in organizational and system dynamics. It provides examples of causal loop diagrams that can be used to model cause-and-effect relationships within a system. It also discusses strategies for driving transformation, such as understanding current system dynamics, designing experiments to test new approaches, facilitating formation of new team structures, and establishing coordination practices. The goal is to holistically change parts of the existing system to create a new product organization.Complexity of organizational design and its effect scaling agility
Complexity of organizational design and its effect scaling agilityAlexey Krivitsky
油
This document discusses the complexity of large organizations and its effect on scaling agility. As organizations grow, they typically add more roles, meetings, documentation and managers, which increases indirection and coordination needs. This added complexity can lead to uneven workloads, out-of-sync development, and a focus on process over work. The document proposes organizing for value delivery through high alignment, clear constraints and high autonomy as a way to reduce complexity and improve agility at scale. It provides examples of structuring products and teams to optimize for customer value.Studying organizational complexity and its effects on scaling agility
Studying organizational complexity and its effects on scaling agilityAlexey Krivitsky
油
This document discusses the complexity of organizations and how it affects their ability to scale agility. It explores how inherent technical complexity and added complexity from factors like specialization can increase coordination needs. It also examines how organizations often try to manage this complexity by adding roles like managers, which paradoxically increases complexity further. The document advocates studying an organization's dynamics to better understand these complexity issues and proposes variables like cycle time, quality, work in progress to analyze.Agile Software Development With SCRUM
Agile Software Development With SCRUMAlexey Krivitsky
油
Materials from one-day training on Agile Software Development with SCRUM done by SCRUMguids.com in Kharkiv, Ukraine
Jan 2009Certified Scrum Product Owner: class desk, posters and photos
Certified Scrum Product Owner: class desk, posters and photosAlexey Krivitsky
油
The document provides an overview of agile product management and scrum. It discusses key concepts like lean, agile, scrum roles and artifacts, ceremonies like sprints and planning, and topics like minimum viable products, user stories, prioritization techniques, and product backlog refinement. The document is a training guide or presentation on agile product management best practices.More from Alexey Krivitsky (18)
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...
Designing and Sustaining Large-Scale Value-Centered Agile Ecosystems (powered...Alexey Krivitsky
油
Is Agile dead? It depends on what you mean by 'Agile'. If you mean that the organizations are not getting the promised benefits because they were focusing too much on the team-level agile "ways of working" instead of systemic global improvements -- then we are in agreement. It is a misunderstanding of Agility that led us down a dead-end. At Org Topologies, we see bright sparks -- the signs of the 'second wave of Agile' as we call it. The emphasis is shifting towards both in-team and inter-team collaboration. Away from false dichotomies. Both: team autonomy and shared broad product ownership are required to sustain true result-oriented organizational agility. Org Topologies is a package offering a visual language plus thinking tools required to communicate org development direction and can be used to help design and then sustain org change aiming at higher organizational archetypes.Strategic Org Design with Org Topologies
Strategic Org Design with Org TopologiesAlexey Krivitsky
油
Org Design is a core skill to be mastered by management for any successful org change.
Org Topologies in its essence is a two-dimensional space with 16 distinctive boxes - atomic organizational archetypes. That space helps you to plot your current operating model by positioning individuals, departments, and teams on the map. This will give a profound understanding of the performance of your value-creating organizational ecosystem.Driving the second wave of Agile revolution with #OrgTopologies
Driving the second wave of Agile revolution with #OrgTopologiesAlexey Krivitsky
油
This document discusses improving organizations beyond team-level agility. It argues that while agile practices at the team level have benefits, they have limited impact without broader organizational changes. The document advocates for redefining value more broadly across the organization, enriching teams through more customer interaction, upgrading management practices, and using Scrum to inspect and adapt organization-wide. This would help organizations design value-creating ecosystems and move to higher architecture types with benefits like multi-team learning, whole-product focus, and reduced complexity.Org Topologies at Scrum Day Europe 2022, Amsterdam
Org Topologies at Scrum Day Europe 2022, AmsterdamAlexey Krivitsky
油
Organizational Topologies: your roadmap towards an innovative, resilient and adaptive product development organization.
Many organizations struggle to adopt "agile" in a way that delivers on its promise to make the company fast, flexible and efficient.
Global consultancy firms have great pitches on how to adopt different so-called Agile frameworks. The marketing is great, but are the results too? We see how our clients get stuck in adopting a framework - forming agile teams, appointing product owners and then clustering all this into tribes. Thus creating robust structures that make further organizational improvements and adaptability difficult, slow, and expensive.
This talk offers ideas how to go beyond these limiting ideas and explores a map of organizational transformation based on orgtopologies.com.Organizational Topologies: a roadmap towards a resilient and adaptive product...
Organizational Topologies: a roadmap towards a resilient and adaptive product...Alexey Krivitsky
油
This document introduces the Adaptivity Map, which provides a roadmap for organizational transformation towards being adaptive and agile. The map shows different stages of organizational topology labeled A1 through C3, with the goal of C3 being optimal value delivery across the whole product. It emphasizes that true transformation requires paradigm shifts in how the organization works, such as establishing cross-functional teams or taking full responsibility for end-to-end delivery. Jumping directly to later stages like C3 from A2 can be an effective approach for organizations with around 50 people. The map is intended as a guide rather than a mandatory process, as transformations will vary in approach and speed depending on each organization's needs.Improve your Product Backlog Refinement (PBR) Process
Improve your Product Backlog Refinement (PBR) ProcessAlexey Krivitsky
油
The document provides guidance on conducting effective Product Backlog Refinement sessions, including splitting user stories, estimating effort, focusing on business value, and collaborating with stakeholders. It emphasizes refining items into testable increments and considering both positive and negative scenarios to ensure stories are appropriately sized. Stakeholders should be engaged as collaborators to provide input and help the team learn.#lego4scrum with Large-Scale Scrum (LeSS)
#lego4scrum with Large-Scale Scrum (LeSS)Alexey Krivitsky
油
This document describes a simulation exercise for practicing Large-Scale Scrum (LeSS) using LEGO and other materials. Participants will build a transportation business connecting European cities using LEGO sets for buses, buildings, and terrain materials. The goal is for teams to work together profitably to meet customer demands for transportation between cities. The document outlines setting up cross-functional teams, area product owners, an initial product backlog refinement, and sprint planning and execution for the simulation.Culture follows structure
Culture follows structureAlexey Krivitsky
油
This document discusses how organizational structure impacts culture. It argues that culture emerges from and is shaped by structural decisions over time, according to the principle that "culture follows structure". Several examples are provided of how specific structural decisions around teams, roles, and domains can influence cultural behaviors, habits, and norms. Systems thinking concepts are introduced to analyze the dynamic interrelationships between variables like quality, cycle time, motivation that are affected by structural changes.Powerful interventions for agile coaching
Powerful interventions for agile coachingAlexey Krivitsky
油
Workshop by Alexey Krivitsky on challenging status quo and adopting the "Kaikaku" thinking.LeSS simulation with LEGO at #agileee 2017. (lego for scrum)
LeSS simulation with LEGO at #agileee 2017. (lego for scrum)Alexey Krivitsky
油
This document provides an overview of a LEGO simulation of Large-Scale Scrum (LeSS). It discusses key principles of LeSS including customer focus, lean thinking, empowered teams, transparency, and constant learning. It outlines the product being built, which is a transportation system connecting European cities using LEGO sets. It also describes the initial setup process for the LeSS framework simulation including forming cross-functional teams, refining product backlogs, and getting ready for the first sprint.Dejirafication: free your process from tools
Dejirafication: free your process from toolsAlexey Krivitsky
油
The document discusses issues with over-reliance on Jira and backlog management tools in meetings, calling this "Jirandicitis". It proposes a "jira rehab program" with techniques like using mind maps instead of lists, just-in-time story creation, shuffling groups for backlog refinement, and lean coffee discussions to reduce tool dependence and improve collaboration.Dejirafication - clean your process
Dejirafication - clean your processAlexey Krivitsky
油
The document discusses "dejirafication", or freeing product development processes from over-reliance on Jira and other backlog management tools. It argues that meetings often become focused on updating the tool rather than team collaboration. The author proposes a "jira rehab program" using paper artifacts instead of Jira, including mind maps for themes, just-in-time story slicing, mixed group backlog refinement, and lean coffee discussions with confidence voting. Following these steps is said to make meetings more lively and focused on shared understanding rather than tool updates.Agile and Scrum for ORSCers
Agile and Scrum for ORSCersAlexey Krivitsky
油
1. The document introduces Agile and Scrum frameworks for system workers, focusing on teamwork, working products, customers, and adapting through inspection.
2. It discusses how work has evolved from individual tasks to complex projects requiring collaboration and knowledge workers. Traditional command structures are replaced with coaching to empower teams.
3. Key aspects of Agile include cross-functional teams that work together long-term, transparency through daily stand-ups and information boards, and continuous learning rather than post-mortem reviews. Departments shift to flexible teams that think about systems rather than just individual jobs.Agile Retrospective Kickstarter @Riga
Agile Retrospective Kickstarter @RigaAlexey Krivitsky
油
16 exercises to kick start your retrospectivesKickstart Your Retrospectives with a Cheat Sheet
Kickstart Your Retrospectives with a Cheat SheetAlexey Krivitsky
油
A workshop based on http://retrospective-cheat-sheet.com/Art of Facilitation
Art of FacilitationAlexey Krivitsky
油
This document outlines the key aspects of facilitating engaging meetings and workshops. It discusses raising engagement through involving participants and changing work modes. It introduces facilitator stances like balancing involvement and helping participants expand their thinking. Meeting design is covered, highlighting the need to move beyond traditional formats. The concept of activity strings is presented for structuring meetings across convergent and divergent phases. Various activities are suggested for different meeting goals like sharing information, advancing thinking or building capacity. The document provides tools to help facilitators design dynamic, productive meetings and workshops.Art of Facilitation. Part 1.
Art of Facilitation. Part 1.Alexey Krivitsky
油
This document provides guidance on facilitating meetings to raise engagement and advance thinking. It discusses three key parts:
1. Raising engagement through techniques like frequent involvement, individual writing, and changing work modes. This helps increase productivity.
2. Facilitator stances like balancing involvement, zooming in and out of discussion, and helping participants think beyond their initial responses.
3. Designing meetings using format strings to structure activities and achieve goals like sharing information, advancing thinking, and building capacity. This moves meetings beyond "business as usual" formats toward more dynamic discussions.Stop asking WHEN?
Stop asking WHEN?Alexey Krivitsky
油
This document discusses the problems with estimation and focusing too much on timelines. It argues that estimates will always be inaccurate due to randomness and variability. Instead of focusing on estimates, the document suggests discussing capacity and scope, and continuously improving capacity while minimizing work. The overall message is to stop asking "when?" and to stop relying on estimates, as accuracy can never be guaranteed.Estimations: stop asking when
- 9. CHAOS REPORT 仂 Standish Group 弌亠亟仆亠舒亳亳亠从亳 仗仂亠从 仗仂 舒亰舒弍仂从亠 亰舒从舒亰仆仂亞仂 仂舒 x2 亟亠仆亠亞 x1.6 于亠仄亠仆亳
- 10. 丼乘 丕 弌 丱丼丐 乘 亂乘 丶 乘 乘丕弌 乂 弌 丼丐 丐亂
- 11. 丼乘 丕 弌 丱丼丐 乘 亂乘 丶 乘 乘丕弌 乂 弌 丼丐 丐亂 弌丐丐弌亊 乂 弌 乘丕弌丐亂 亊 乘 乂 亂乘 丶弌 丼丐 丐亂 弌亂
- 12. 丐亳仗亳仆亶 IT 仗仂亠从
- 13. 丼丐 乘 丐???
- 18. 弌丐亊 丼 亊 1. 弌丐 弌丐亊丐 $1,10 2. 乘丿亂 亊丼 - 弌亂 弌丐丐 亊丼?
- 19. 束仂亠損 仆舒亠亞仂 仄仂亰亞舒 亠 束弍舒亞亳損. 丕 仆舒 仆亠 于亠 于 仗仂磲从亠 仂亠仆亳于舒仆亳亠仄. 仂 仆亠 仂亞舒仆亳亳于舒亠 仂仗亳亠从亳仄亳 亳仍仍ﾐ経狐礆亳.
- 21. 丼丐丐 亅丐丐 丐弌丐 乘丼弌亊丐 3x3 = ?
- 25. 3x3 = 亅丐 弌 丿 束亊丶損 丼丐
- 27. 丼 束亊丶損?
- 28. 丼 乂 丱丿 束亊丶損?
- 29. 弌亂 丕丐 17x38 ?
- 31. 丼丐 丕 弌丕豫 豫?
- 32. MCMLXXXIV 仍亠仆 :) 丼丐 丕 弌丕豫 豫?
- 33. 丐丕丶亊 弍亠 于亳仍亠仆亳 仍仂亢仆亠 于亳仍亠仆亳 仄舒仍亶 舒仂亟 仆亠亞亳亳 仂亞仂仄仆亶 舒仂亟 仆亠亞亳亳 亊丶 vs. 丼丱
- 34. 亊丶 vs. 丼丱 2.0 乘 乘丼弌亊丐 弌 亊 弌弌丐 丐 弌丼丐?
- 35. 弌从仂仍从仂 弍仍仂 仍亠 舒舒仄亠 舒仆亟亳, 从仂亞亟舒 仂仆 仄亠?
- 36. 弌从仂仍从仂 亠仄 弍仍仂 仍亠, 从仂亞亟舒 仂仆 仄亠? 1. 仍仂 仍亳 舒舒仄亠 舒仆亟亳 仄亠仆亠亠 100 仍亠, 从仂亞亟舒 仂仆 仄亠? 1. 仍仂 仍亳 舒舒仄亠 舒仆亟亳 弍仂仍亠亠 60 仍亠, 从仂亞亟舒 仂仆 仄亠?
- 37. 83 亠亟仆亠亠 68 亠亟仆亠亠 1. 仍仂 仍亳 舒舒仄亠 舒仆亟亳 仄亠仆亠亠 100 仍亠, 从仂亞亟舒 仂仆 仄亠? 1. 仍仂 仍亳 舒舒仄亠 舒仆亟亳 弍仂仍亠亠 60 仍亠, 从仂亞亟舒 仂仆 仄亠?
- 38. 亅丐 豫弌. 丿.
- 40. 豫弌. 丐 .
- 42. 丐 弌 丐豫丐 乘 乘
- 52. 于亠仄 于亠仂仆仂 1 丕丼亊 丶 亅丐 亊丐 亊 丿亊
- 55. 于亠仄
- 57. 丐 豫弌?
- 58. 仗仂亠 亞仂于仂: 乂 丐亂, 丼 丕弌丐亂!
- 65. 弌丐亂 乘丱???
- 67. (舒仄 亟舒仍亠从仂)乘
- 70. 83 亠亟仆亠亠 68 亠亟仆亠亠 1. 仍仂 仍亳 舒舒仄亠 舒仆亟亳 仄亠仆亠亠 100 仍亠, 从仂亞亟舒 仂仆 仄亠? 1. 仍仂 仍亳 舒舒仄亠 舒仆亟亳 弍仂仍亠亠 60 仍亠, 从仂亞亟舒 仂仆 仄亠? 弌 弌 丐丐 - 76 亂乘 丐丐 - 78 !
- 72. AS A USER blah blah blah
- 76. 2 5 2 1 8 3 2 5 5 2 3 2 丿 弌弌丐亂 弌丐 仗亳仆
- 82. 仗亳仆 丶?
- 83. 仗亳仆 亅丐 亂弌丐亂.
- 84. 亞亳仄亳 仍仂于舒仄亳 (1) 弌丐亂丐 个丕弌丐亂弌亊 丶丱 (仂仆亳 于亠亞亟舒 弍亟 从亳于仄亳)
- 85. 亞亳仄亳 仍仂于舒仄亳 (2) 丐 丕弌 丿 弌弌丐 乖 丐
- 86. 亞亳仄亳 仍仂于舒仄亳 (3) 弌丐亊 丐丐 乘丿 丿 弌弌丐 丕亂丿 乖 丐
- 87. 弌丐 亂丐 弌丿 丐亂 ?