Agile Coach, XP-Coach, Kanban-Coach – with all these coaching related terms it is sometimes hard to know, what the job of an <xyz> coach is – this talk provides some answers. (Slides from my talk at the Lean Kanban Benelux Conference 2016)
The other team-models - beyond forming and stormingMichael Mahlberg
The 2013 version of a talk about team-models from tuckman via several j-curve models to the drexler/sibbet model. Applicable for everyone who works in a team, runs a team or wants to build a team
More and more new words come up in the context of Agile, now that Agile itself has "crossed the chasm" and is accepted as the de-facto standard of software development. But even though a lot of these new terms fit under the Agile umbrella as defined in the "Agile Manifesto" it is sometimes hard to get to the bottom of these concepts.
This presentation does exactly that - it goes to the bottom of Agile, Lean and Kanban. Without much ado we'll revisit the fundamental ideas behind Agile and then investigate Lean and the Kanban Method in comparison. Not only will you get introduced more closely to Kanbans, WIP-Limits and the pull principle, but I'll also share my experience how the different approaches fit together and complement each other in various settings.
The document discusses different stances that coaches can take, including the traditional coaching stance of believing the solution lies within the client. It also discusses stances from sports coaching like telling, showing, teaching, selling, training, and coaching. Additional stances discussed include those from interactions like consulting, mentoring, and coaching where there are deltas in knowledge, experience, and process mastery. The document advocates that coaches have flexibility in their stances and considers stances for different types of coaching like XP, Kanban, Scrum, and SAFe. It also discusses the internal stance of different coaching approaches and having the right stance for each situation and client.
Continuous Integration - I Don't Think That Word Means What You Think It MeansMichael Mahlberg
Continuous Integration has become synonymous with CI-Servers and the concept of CI/CD-Pipelines. Unfortunately, you can have continuous delivery without continuous integration. Just as you can check in directly to 'production' without having trunk-based development. (And shouldn't trunk-based development should be called master based development nowadays?).
This session aims to debunk several misconceptions about good engineering practices and proposes some ways to get from cargo-cult agile (aka in-name-only-agile) to tangible results today.
Kickstart Your Product with a Design Sprint by thestartupfactory.techProduct School
In a fluid and fast-paced world of Product, Product Management and building Product Roadmaps, even the most skilled of teams can struggle with a specific proposition, have misaligned priorities or simply get stuck from time to time. That's where the Design Sprint comes in – a process born at Google Ventures. This presentation unravels how a Design Sprint can get you and your team back on track in just 5 days. Not only that, but get a sneak peek into Design Sprint 2.0: now 20% faster than the original!
From Divided to United - Aligning Technical and Business TeamsDominica DeGrandis
This is a true story of one SaaS company's journey to gain alignment across business and technical teams by changing how four important factors were viewed: customer demand, work prioritization, team metrics, and communication etiquette.
Workshop with an introduction to Scaling Agile, the different axes when scaling, risks on scaling Agile and a compact solution to a transparant, flexible and easy-to-use format for Program, Portfolio and Project management within a Scalig Agile context. We called this the Submay map:)
This document provides an overview of a presentation on helping managers transition to an agile mindset. It discusses the challenges modern managers face and roles they should focus on. Managers are encouraged to adopt a servant leadership approach and focus on motivating teams. A key recommendation is for managers to shift their focus from directing individuals to designing organizational environments that support agility. Interactive exercises have attendees explore their current responsibilities and how to better align with agile principles.
The other team-models - beyond forming and stormingMichael Mahlberg
The 2013 version of a talk about team-models from tuckman via several j-curve models to the drexler/sibbet model. Applicable for everyone who works in a team, runs a team or wants to build a team
More and more new words come up in the context of Agile, now that Agile itself has "crossed the chasm" and is accepted as the de-facto standard of software development. But even though a lot of these new terms fit under the Agile umbrella as defined in the "Agile Manifesto" it is sometimes hard to get to the bottom of these concepts.
This presentation does exactly that - it goes to the bottom of Agile, Lean and Kanban. Without much ado we'll revisit the fundamental ideas behind Agile and then investigate Lean and the Kanban Method in comparison. Not only will you get introduced more closely to Kanbans, WIP-Limits and the pull principle, but I'll also share my experience how the different approaches fit together and complement each other in various settings.
The document discusses different stances that coaches can take, including the traditional coaching stance of believing the solution lies within the client. It also discusses stances from sports coaching like telling, showing, teaching, selling, training, and coaching. Additional stances discussed include those from interactions like consulting, mentoring, and coaching where there are deltas in knowledge, experience, and process mastery. The document advocates that coaches have flexibility in their stances and considers stances for different types of coaching like XP, Kanban, Scrum, and SAFe. It also discusses the internal stance of different coaching approaches and having the right stance for each situation and client.
Continuous Integration - I Don't Think That Word Means What You Think It MeansMichael Mahlberg
Continuous Integration has become synonymous with CI-Servers and the concept of CI/CD-Pipelines. Unfortunately, you can have continuous delivery without continuous integration. Just as you can check in directly to 'production' without having trunk-based development. (And shouldn't trunk-based development should be called master based development nowadays?).
This session aims to debunk several misconceptions about good engineering practices and proposes some ways to get from cargo-cult agile (aka in-name-only-agile) to tangible results today.
Kickstart Your Product with a Design Sprint by thestartupfactory.techProduct School
In a fluid and fast-paced world of Product, Product Management and building Product Roadmaps, even the most skilled of teams can struggle with a specific proposition, have misaligned priorities or simply get stuck from time to time. That's where the Design Sprint comes in – a process born at Google Ventures. This presentation unravels how a Design Sprint can get you and your team back on track in just 5 days. Not only that, but get a sneak peek into Design Sprint 2.0: now 20% faster than the original!
From Divided to United - Aligning Technical and Business TeamsDominica DeGrandis
This is a true story of one SaaS company's journey to gain alignment across business and technical teams by changing how four important factors were viewed: customer demand, work prioritization, team metrics, and communication etiquette.
Workshop with an introduction to Scaling Agile, the different axes when scaling, risks on scaling Agile and a compact solution to a transparant, flexible and easy-to-use format for Program, Portfolio and Project management within a Scalig Agile context. We called this the Submay map:)
This document provides an overview of a presentation on helping managers transition to an agile mindset. It discusses the challenges modern managers face and roles they should focus on. Managers are encouraged to adopt a servant leadership approach and focus on motivating teams. A key recommendation is for managers to shift their focus from directing individuals to designing organizational environments that support agility. Interactive exercises have attendees explore their current responsibilities and how to better align with agile principles.
Getting a grip on your agile maturity using the ambition chartDerk-Jan de Grood
This document discusses using an Ambition Chart to measure and improve agile maturity over time. The Ambition Chart identifies key maturity areas and allows teams to assess their current status, set incremental goals, and track progress. Examples are provided of Ambition Charts used for testing maturity and Scrum implementation. Guidance is given on identifying areas, dreaming of an ideal future state, defining small steps, using descriptive statements, and focusing on continuous improvement rather than end goals.
Bryan Berger on Distraction Free Design Sprints at Design Driven NYCBryan Berger
I lead a team of 5 Product Designers. We build platforms and solutions for online and in-person learning experiences.
I talk about wow we paused all work for 2 weeks across all teams to get back to the basics.
Why we needed to do it, what we did, and what we learned as a design team.
Close the Loop - Simplifying A3 Thinking for Team RetrospectivesCara Turner
The document discusses using A3 Thinking and the scientific method to structure team retrospectives. It presents a process for defining a goal as a hypothesis to test in the next sprint, then reviewing the results to see if assumptions were correct and how close the team is to the target state. The goal is to close the loop on continuous improvement by experimenting with changes and reviewing outcomes to guide future adaptations.
Lessons learned from managing a distributed agile teamAgileDenver
The document discusses lessons learned from managing a distributed agile team. It summarizes that distributed agile teams face additional complications like different time zones and a lack of in-person collaboration, but these challenges can be overcome. Key lessons are that everyone must follow the same processes, artifacts must be accessible remotely, strong scrum masters and business analysts are needed, and in-person meetings are still valuable when possible. Remote agile is difficult but not impossible with the right team and practices.
Mile High Agile 2016 conference is posting materials from our speakers so attendees can familiarize themselves and deepen their research and understanding.
First Speaker : Bob Galen
The document discusses three key things needed to transform an organization into an agile enterprise: backlogs, teams, and working tested software. It explains that properly formatted backlogs provide clarity, accountability, and measurable progress. Cross-functional teams allow for autonomy, mastery, and a sense of purpose. And emphasis on continually delivering working, tested software is important at scale through governance, structure, and metrics. The document also identifies common barriers such as organizational dependencies, technical debt, and improperly managed requirements.
This document outlines an agenda for a workshop on A3 thinking and problem solving. The workshop objectives are to explore lessons from Managing to Learn using A3s. The agenda covers defining an A3, working through examples, applying A3 thinking to problems, and discussing uses of A3s for proposals and reports. Time is allotted to introduce A3 concepts, examine example A3s, have participants apply the process to their own work, and reflect on learning. The workshop aims to help participants recognize effective A3 stories and create different sections of an A3 through practice and discussion.
A guide to creating a quality project schedule it-toolkitsIT-Toolkits.org
Successful projects start with a good quality project schedule. Creating a schedule is one of the first tasks you should do when given a project to manage. There is often a temptation to get on with the work and worry about the schedule later, but this is a mistake. You will be left exposed and if challenged, will have no evidence of whether your project is on time or running late.
Roles of Project Managers in Agile TeamsAaron Medina
Roles of Project Managers in Agile Teams
[Traditional] Perspective of PMs
Scrum Team Roles
Servant Leadership
When will need our PMs?
A Question of Scale and Complexity
PM Roles and Responsibilities
La quasi totalità degli sviluppi software è basata su un approccio per progetto. Un progetto, per definizione, è qualcosa di effimero. Ha un inizio, e soprattutto una fine, qualcosa di temporaneo. Il software non è temporaneo. Un software sopravvive fino a quando esiste almeno una persona che lo utilizza. A volte sopravvive anche più a lungo.
Perché continuiamo ad usare qualcosa di effimero per gestire qualcosa che effimero non è? Quali alternative abbiamo? Possiamo fare veramente a meno dei progetti?
A design sprint is a 5-phase framework that helps teams answer critical business questions through rapid prototyping and user testing. The phases are: Map (understand the problem), Sketch (generate ideas), Decide (select the best concept), Prototype (build something testable), and Test (get user feedback). This process helps spark innovation, encourage user-centered design, align teams, and launch products faster. A key benefit is that it provides validated direction and user input to inform product development. Design sprints are best for when a team needs clarity on a new opportunity or is stuck on an issue.
#noprojects: Live happily ever after without projectsDimitri Favre
This document discusses the concept of #noprojects, which advocates switching from a project mindset to a product mindset when developing software. It presents #noprojects as a deliberate act of continuous product management. The document outlines #noprojects in 4 stages: 1) experiments over projects, 2) stable teams over temporary endeavors, 3) products over software, and 4) outcomes over execution. It also provides 10 principles for guiding a #noprojects approach, such as funding capacity not scope, bringing work to stable teams, and ensuring roadmaps are driven by needs not features. The overall message is that organizations should stop viewing software development as projects and instead focus on continuous product management and development.
Henny Portman "Will the Project Manager survive in the Agile world?"Lviv Startup Club
The document discusses how project managers can survive in an agile world. It begins with the speaker's biography and then covers several key topics:
- The differences between project work and ongoing work in organizations
- How agile practices improve predictability compared to traditional approaches
- The roles of product owners, scrum masters, and how they differ from traditional project roles
- Frameworks for scaling agile such as SAFe and LeSS across multiple teams
- How organizations can implement a hybrid project management approach using both agile and traditional methods
- The changing role of the PMO in supporting agile teams and programs
Many Agile practitioners are comfortable working iteratively in small slices once there’s a basic foundation, but struggle with where to start on a new project, product, or other big idea. Participants in this session will learn how to use Richard’s Feature Mining technique to find early slices of any big idea that provide value, learning, and risk-mitigation.
Agile For All clients have used this successfully for all kinds of software products, for combined software and hardware systems, and even beyond software in such areas as park construction and office remodeling. In some cases, projects with apparent significant up-front infrastructure requirements were able to ship a valuable slice to customers after just one or two sprints.
The document discusses how to become agile through 5 questions:
1) What does agility mean and what are its key characteristics?
2) What values do agile workers have such as simplicity, openness, learning?
3) What is the purpose of a company's work?
4) How do agile workers work with and obtain feedback from users?
5) How do agile workers communicate and learn from each other through open communication?
Methodology Madness: The Origins, Issues and Advantages of AGILELou Russell
Over the years, methods for buildin solutions have gone from Top Down, to Rapidly Development, to Agile, to Design Thinking... and on and on. The Best method depends on your problem.
Agile Anywhere in the 21st Century: Setting up distributed teams to be effectiveAgileDenver
This presentation will focus on the topic of working in a distributed agile team. We’ll go over terminology (remote vs near shore vs offshore vs distributed vs satellite etc) and I will share three different examples of distributed teams I’ve worked on and how we managed to be agile with our practices around pairing, knowledge sharing, and minimizing upfront design.
We will discuss why the notion of distributed teams is becoming more and more relevant for modern organizations, what advantages and drawbacks exist, and what leadership needs to carefully evaluate when asking if distributed is right for their teams.
The 5-day Design Sprint process provides teams a structured approach to answering critical business questions. In the first day, teams map out the challenge by defining a long-term goal and target audience. On the second day, teams sketch rapid ideas and variations. The third day has teams vote on the best ideas to prototype. A prototype is created on the fourth day for user testing on the fifth day. This process gives teams a fast way to learn from users without fully building and launching a product.
This deck describes the key learnings from a coaching engagement I did in early 2009 for VersionOne. . Might be called... how to do Scrum and deliver nothing ;-)
Scrumagilean: Understanding Lean and Forgetting Scrum vs KanbanJon Terry
The document discusses the shared heritage and principles of modern management methods like Lean, Agile, Scrum, and Kanban. It explains that while these methods may have different terminology and practices, they are all based on the same timeless Lean principles of eliminating waste, building quality in, creating knowledge, optimizing the whole process, and more. The document advocates understanding the shared principles between methods in order to broaden learning and improve communication. It also presents that Scrum and Kanban are not competing frameworks but rather complementary, with teams able to benefit from elements of both.
Este documento presenta el Business Coaching como una herramienta poderosa para los líderes y gerentes de las PYMES. Resume los resultados de encuestas que muestran bajos niveles de compromiso de los empleados y la importancia de que los gerentes adopten un enfoque de coaching. Explica conceptos clave del coaching, sus beneficios y autores destacados. También describe certificaciones y programas de entrenamiento en coaching ofrecidos por la empresa Ontology Training.
Getting a grip on your agile maturity using the ambition chartDerk-Jan de Grood
This document discusses using an Ambition Chart to measure and improve agile maturity over time. The Ambition Chart identifies key maturity areas and allows teams to assess their current status, set incremental goals, and track progress. Examples are provided of Ambition Charts used for testing maturity and Scrum implementation. Guidance is given on identifying areas, dreaming of an ideal future state, defining small steps, using descriptive statements, and focusing on continuous improvement rather than end goals.
Bryan Berger on Distraction Free Design Sprints at Design Driven NYCBryan Berger
I lead a team of 5 Product Designers. We build platforms and solutions for online and in-person learning experiences.
I talk about wow we paused all work for 2 weeks across all teams to get back to the basics.
Why we needed to do it, what we did, and what we learned as a design team.
Close the Loop - Simplifying A3 Thinking for Team RetrospectivesCara Turner
The document discusses using A3 Thinking and the scientific method to structure team retrospectives. It presents a process for defining a goal as a hypothesis to test in the next sprint, then reviewing the results to see if assumptions were correct and how close the team is to the target state. The goal is to close the loop on continuous improvement by experimenting with changes and reviewing outcomes to guide future adaptations.
Lessons learned from managing a distributed agile teamAgileDenver
The document discusses lessons learned from managing a distributed agile team. It summarizes that distributed agile teams face additional complications like different time zones and a lack of in-person collaboration, but these challenges can be overcome. Key lessons are that everyone must follow the same processes, artifacts must be accessible remotely, strong scrum masters and business analysts are needed, and in-person meetings are still valuable when possible. Remote agile is difficult but not impossible with the right team and practices.
Mile High Agile 2016 conference is posting materials from our speakers so attendees can familiarize themselves and deepen their research and understanding.
First Speaker : Bob Galen
The document discusses three key things needed to transform an organization into an agile enterprise: backlogs, teams, and working tested software. It explains that properly formatted backlogs provide clarity, accountability, and measurable progress. Cross-functional teams allow for autonomy, mastery, and a sense of purpose. And emphasis on continually delivering working, tested software is important at scale through governance, structure, and metrics. The document also identifies common barriers such as organizational dependencies, technical debt, and improperly managed requirements.
This document outlines an agenda for a workshop on A3 thinking and problem solving. The workshop objectives are to explore lessons from Managing to Learn using A3s. The agenda covers defining an A3, working through examples, applying A3 thinking to problems, and discussing uses of A3s for proposals and reports. Time is allotted to introduce A3 concepts, examine example A3s, have participants apply the process to their own work, and reflect on learning. The workshop aims to help participants recognize effective A3 stories and create different sections of an A3 through practice and discussion.
A guide to creating a quality project schedule it-toolkitsIT-Toolkits.org
Successful projects start with a good quality project schedule. Creating a schedule is one of the first tasks you should do when given a project to manage. There is often a temptation to get on with the work and worry about the schedule later, but this is a mistake. You will be left exposed and if challenged, will have no evidence of whether your project is on time or running late.
Roles of Project Managers in Agile TeamsAaron Medina
Roles of Project Managers in Agile Teams
[Traditional] Perspective of PMs
Scrum Team Roles
Servant Leadership
When will need our PMs?
A Question of Scale and Complexity
PM Roles and Responsibilities
La quasi totalità degli sviluppi software è basata su un approccio per progetto. Un progetto, per definizione, è qualcosa di effimero. Ha un inizio, e soprattutto una fine, qualcosa di temporaneo. Il software non è temporaneo. Un software sopravvive fino a quando esiste almeno una persona che lo utilizza. A volte sopravvive anche più a lungo.
Perché continuiamo ad usare qualcosa di effimero per gestire qualcosa che effimero non è? Quali alternative abbiamo? Possiamo fare veramente a meno dei progetti?
A design sprint is a 5-phase framework that helps teams answer critical business questions through rapid prototyping and user testing. The phases are: Map (understand the problem), Sketch (generate ideas), Decide (select the best concept), Prototype (build something testable), and Test (get user feedback). This process helps spark innovation, encourage user-centered design, align teams, and launch products faster. A key benefit is that it provides validated direction and user input to inform product development. Design sprints are best for when a team needs clarity on a new opportunity or is stuck on an issue.
#noprojects: Live happily ever after without projectsDimitri Favre
This document discusses the concept of #noprojects, which advocates switching from a project mindset to a product mindset when developing software. It presents #noprojects as a deliberate act of continuous product management. The document outlines #noprojects in 4 stages: 1) experiments over projects, 2) stable teams over temporary endeavors, 3) products over software, and 4) outcomes over execution. It also provides 10 principles for guiding a #noprojects approach, such as funding capacity not scope, bringing work to stable teams, and ensuring roadmaps are driven by needs not features. The overall message is that organizations should stop viewing software development as projects and instead focus on continuous product management and development.
Henny Portman "Will the Project Manager survive in the Agile world?"Lviv Startup Club
The document discusses how project managers can survive in an agile world. It begins with the speaker's biography and then covers several key topics:
- The differences between project work and ongoing work in organizations
- How agile practices improve predictability compared to traditional approaches
- The roles of product owners, scrum masters, and how they differ from traditional project roles
- Frameworks for scaling agile such as SAFe and LeSS across multiple teams
- How organizations can implement a hybrid project management approach using both agile and traditional methods
- The changing role of the PMO in supporting agile teams and programs
Many Agile practitioners are comfortable working iteratively in small slices once there’s a basic foundation, but struggle with where to start on a new project, product, or other big idea. Participants in this session will learn how to use Richard’s Feature Mining technique to find early slices of any big idea that provide value, learning, and risk-mitigation.
Agile For All clients have used this successfully for all kinds of software products, for combined software and hardware systems, and even beyond software in such areas as park construction and office remodeling. In some cases, projects with apparent significant up-front infrastructure requirements were able to ship a valuable slice to customers after just one or two sprints.
The document discusses how to become agile through 5 questions:
1) What does agility mean and what are its key characteristics?
2) What values do agile workers have such as simplicity, openness, learning?
3) What is the purpose of a company's work?
4) How do agile workers work with and obtain feedback from users?
5) How do agile workers communicate and learn from each other through open communication?
Methodology Madness: The Origins, Issues and Advantages of AGILELou Russell
Over the years, methods for buildin solutions have gone from Top Down, to Rapidly Development, to Agile, to Design Thinking... and on and on. The Best method depends on your problem.
Agile Anywhere in the 21st Century: Setting up distributed teams to be effectiveAgileDenver
This presentation will focus on the topic of working in a distributed agile team. We’ll go over terminology (remote vs near shore vs offshore vs distributed vs satellite etc) and I will share three different examples of distributed teams I’ve worked on and how we managed to be agile with our practices around pairing, knowledge sharing, and minimizing upfront design.
We will discuss why the notion of distributed teams is becoming more and more relevant for modern organizations, what advantages and drawbacks exist, and what leadership needs to carefully evaluate when asking if distributed is right for their teams.
The 5-day Design Sprint process provides teams a structured approach to answering critical business questions. In the first day, teams map out the challenge by defining a long-term goal and target audience. On the second day, teams sketch rapid ideas and variations. The third day has teams vote on the best ideas to prototype. A prototype is created on the fourth day for user testing on the fifth day. This process gives teams a fast way to learn from users without fully building and launching a product.
This deck describes the key learnings from a coaching engagement I did in early 2009 for VersionOne. . Might be called... how to do Scrum and deliver nothing ;-)
Scrumagilean: Understanding Lean and Forgetting Scrum vs KanbanJon Terry
The document discusses the shared heritage and principles of modern management methods like Lean, Agile, Scrum, and Kanban. It explains that while these methods may have different terminology and practices, they are all based on the same timeless Lean principles of eliminating waste, building quality in, creating knowledge, optimizing the whole process, and more. The document advocates understanding the shared principles between methods in order to broaden learning and improve communication. It also presents that Scrum and Kanban are not competing frameworks but rather complementary, with teams able to benefit from elements of both.
Este documento presenta el Business Coaching como una herramienta poderosa para los líderes y gerentes de las PYMES. Resume los resultados de encuestas que muestran bajos niveles de compromiso de los empleados y la importancia de que los gerentes adopten un enfoque de coaching. Explica conceptos clave del coaching, sus beneficios y autores destacados. También describe certificaciones y programas de entrenamiento en coaching ofrecidos por la empresa Ontology Training.
Polar Bear Pithing Ice Breaker Day 2016
Short description how to integrate b2b sales process to b2b buying process.
Ice Breaker Day was event, where startups got the right tools to break through the ice with global investors and media. Hands on workshops sparred by top experts, networking and matchmaking!
This document discusses the emerging trend of "Sales 2.0", which refers to new business practices that leverage online collaboration and Web 2.0 tools to improve sales and marketing efforts. It notes that one of the central pillars of Web 2.0 and Sales 2.0 is collaboration, as online tools now allow companies to better understand customers and market/sell products. A survey found that smaller companies are early adopters of these tools, with LinkedIn and Facebook being the most commonly used. While adoption is still growing, most respondents believe collaborative online tools are having a positive impact on their work. The document concludes that Sales 2.0 remains in its early stages.
This Workshop is remarkable. Brian K McNeill [The Most Fun Professional Speaker] delivers a complete sales strategy and a step by step process that guarantees new customers. This is an outstanding value, and it is delivered with energy, enthusiasm and a true love of the sales process.
Este documento describe varias herramientas digitales para la creación y publicación de contenidos educativos. Explica que estas herramientas facilitan la transmisión de ideas y el intercambio de conocimiento de manera digital. Luego, menciona ventajas como su accesibilidad y uso gratuito, y desventajas como la posible dispersión de la información. Finalmente, describe las características de 10 herramientas populares como Ardora, Constructor y eXeLearning.
Este documento presenta información sobre carpetas virtuales y sistemas operativos. Incluye secciones sobre sistemas numéricos, investigaciones sobre sistemas operativos y sus clasificaciones, software de aplicación y conectividad, y software de utilidad. También contiene ejemplos de pruebas, tareas y reportes de revisión de carpetas. El documento provee una introducción amplia sobre diferentes temas relacionados a sistemas operativos y software.
Freelance webmarketing spécialisé en Acquisition & Performance, j'aide les entreprises à acquérir de nouveaux clients et à mettre en place des indicateurs de performance. "Mesurer pour mieux acquérir !" Je suis également spécialiste certifié Adwords.
Los Animales Domésticos y Salvajes por Cintya CalvacheCintyaCalvache
Este documento describe los animales domésticos y salvajes, incluyendo perros, gatos, vacas, caballos, gallinas, patos y más que viven en hogares y granjas. También describe animales salvajes como leones, tigres, elefantes, jirafas, osos y cocodrilos que viven en la selva y se alimentan de otros animales. Explica brevemente las características y hábitos alimenticios de cada animal.
Qualities To Look For In A Recruitment AgencyT & A Solutions
Over the past few years, we have seen the increasing rate of recruitment agencies which are doing their best to provide jobs to the candidates. There are many recruitment agencies which are fake. So, how people would know which recruitment agency is good for them. In this infographic, we have discussed the qualities which we have to look at before hiring a recruitment agency.
Презентация к уроку «Захват власти большевиками в октябре 1917 г.»yrasskazova
Презентация к уроку «Захват власти большевиками в октябре 1917 г.». Автор - учитель истории ГБОУ гимназии № 155 Центрального района Санкт-Петербурга
Субботина Н. И.
This document discusses violence against women and provides information about International Day for the Elimination of Violence against Women on November 25th. It notes that 40-50% of women in the European Union experience physical abuse. It describes different types of violence including physical, psychological, and domestic abuse. It outlines some of the consequences of violence against women like silence, guilt, loss of faith in oneself, and dependency. It also discusses Bulgaria signing the Istanbul Convention to prevent and combat violence against women. Finally, it provides some tips on how to prevent violence and calls for raising awareness of the problems women face worldwide.
This document discusses the future of work and alternatives to traditional management structures. It provides three examples of organizations that operate successfully without hierarchies through self-management. Key points:
- The future of work may involve replacing traditional management styles that leave most employees feeling unmotivated and replace them with more humane, purpose-driven organizations.
- Case studies show organizations like FAVI (metal manufacturer) and Buurtzorg (healthcare provider) that engage employees and use self-managing principles are consistently more successful.
- These organizations function without managers, budgets, or traditional business functions through self-management, transparency, and intrinsic motivation instead of external controls.
- Rather than big transformation initiatives, successful
Using Top-Producer Analysis to Improve Sales ResultsMike Kunkle
This is a presentation about my methodology for conducting a top-producer analysis. I'm presenting this at the ATD's 2016 annual conference in Denver on Tue 5/24/2016.
Conducting a Top-Producer Analysis:
- Allows you to use the data to construct content and curricula that, when implemented within an effective learning system, will increase organizational sales results and provide payback and return on investment.
- Is the epitome of talent development. It takes best practices to a new level, by using your own, internal top sales talent to help others improve, which accounts for the context and nuances that best practices do not.
- Allows you to isolate the true exemplary performers (some top-producers earn their results, others get lucky or are handed big accounts), determine the differentiating practices between these producers and others, and replicate the behaviors that will drive sales results and lift your middle producers to new levels.
Content startegy Applied - Februar 2017 - Babak Zand, Helen SchraderHelen Schrader
This document discusses developing and implementing an agile content strategy with limited resources. It recommends using agile project management methods like Scrum within a pilot project. Key aspects include:
1) Developing a content strategy framework with preparation, research, and strategy phases to gather data and draft content plans.
2) Implementing an agile approach using Scrum methods like backlogs, sprints, and reviews to iteratively work on content.
3) Measuring performance with OKRs and a balanced scorecard to continuously control the content strategy.
Agile Content Strategy: developing and implementing a content strategy with f...Babak Zand
This document discusses developing and implementing an agile content strategy with limited resources. It recommends using agile project management methods like Scrum within a pilot project. Key aspects include:
1) Developing a content strategy framework with preparation, research, and strategy phases to define goals and collect data.
2) Implementing an iterative approach using Scrum methods like backlogs, sprints, and reviews to develop the strategy.
3) Measuring performance with OKRs and a balanced scorecard to control the strategy.
The document discusses lean innovation and increasing the success rate of startups. It proposes using an agile lean innovation framework that iterates through problem/solution fit, product/market fit, and customer creation stages using a build-measure-learn feedback loop to test hypotheses. The goal is to validate a profitable, repeatable, and scalable business model or pivot the startup in new directions based on lessons learned. It emphasizes testing value and growth hypotheses through experiments and MVPs that address real customer needs over building elaborate products with no market validation.
A Simple Sales Coaching Methodology That Moves the NeedleMike Kunkle
Watch the webinar at: https://www.brighttalk.com/webcast/14877/237023
Everyone knows that sales coaching is needed. Unfortunately, even when sales managers try to coach, they often focus on the wrong things and don't get the results they hoped for. The solution is ROAM, a coaching diagnostic approach, that when combined with simple models for field training and sales coaching, can help sales managers move the needle on the metrics that really matter.
This document discusses the evolving role of the project manager (PM) in lean and agile environments. It introduces three PM roles: lagging PM, leading PM, and strategic PM. The lagging PM responds to changes by applying corrective actions. The leading PM charts the future, anticipates issues, and leads organizational change. The strategic PM enables innovations and facilitates organizational alignment. Workshops are provided for each role to identify valuable activities. The document concludes that the PM role has adapted through frameworks like SAFe and that PM skills are applicable beyond specific roles.
This is a presentation about the latest changes in the PMP Exam, based on the new PMBOK 6th Edition released by PMI.
Authored by
Ahmad Al-Musallami, MSc, PMP, PMI-SP, PMI-ACP & CPT
This document provides the syllabus for the MS&E 297 Hacking for Defense (H4D) course. The course aims to give students hands-on experience solving national security issues using the Lean Startup methodology. It will be taught in Stanford's Thornton Hall from March 29th to May 31st. Students will work in teams to develop solutions to defense problems, conducting customer interviews, building prototypes, and presenting progress weekly. The syllabus outlines weekly readings, assignments, and team presentation requirements to guide students through the customer development process.
Agile conferences, blogs, twitter – wherever lean and agile people come together it is easy to stir up a tumult with emotions running high just by mentioning Jira. But why is there always such a strong reaction? Is it the quality of the tool? Not in my experience. The problem lies in the actual adoption in many organizations and – to be fair –similar points could be made about other tools as well. This talk will look into the systemic, sociological and organizational issues that make (some) of us wince each time we hear that our clients use Jira. And it will show how to deal with these issues!
This is not meant to be a Jira bashing session, but a talk that aims to provide actual guidance for all agile initiatives challenged with centrally administered systems. After this talk participants will know (more) about
- A better –and more objective– understanding on why so many people in the lean and agile communities object the usage of Jira
- Some Approaches to succeeding with lean and agile initiatives despite centrally administered ticketing systems like the one mentioned in the title
6 Steps To An Advanced Competitor Analysis For Digital MarketersHanapin Marketing
In this presentation, Hanapin’s Jacob Fairclough and SEMrush’s Paul Klebanov will direct you through the process of analyzing your own account, comparing it to your competition, and taking the steps to put your brand above the rest.
The document discusses the Lean Innovation framework for startups. It proposes using an iterative Build-Measure-Learn feedback loop to validate assumptions and hypotheses through minimum viable product (MVP) experiments. This allows startups to improve the problem/solution fit and product/market fit faster by learning what customers want rather than assuming. The goal is to find a repeatable and scalable business model or pivot the startup to a new idea if unsuccessful. Key aspects of the framework include the Lean Canvas for idea validation, running low-risk MVP experiments, quantifying goals and learning from each experiment.
Product interviews can be nerve-wrecking and stressful, especially if you aren’t properly prepared. However, if you know exactly how to get ready, the experience can be incredibly rewarding. We cover what research you should do before the interview, how to craft the best possible answers, ways to distinguish yourself from other candidates and discuss what's required to get the job offer you really want.
- An overview of the types of questions to expect
- Best ways to prep for a Product Manager interview
- Do's and Don'ts for the actual interview
- A comprehensive list of books, online training, and other online resources related to product interviews
The talk provides a new perspective on leadership in the digital age. Key topics include:
1. Organisational development: changing from a top-down, military-style organisation towards a supportive, adaptive and open organisation. Led by a leader who supports those in contact with the customers as opposed to a director / dictator who dictates from the top.
2. How to lead: Leadership involves setting a direction which people can follow. The author proposes to use the OKR framework (objective and key results), introduced by google, as a basis. The key steps in implementing the same are laid out as follows:
#1 Start defining OKRs to set an example.
#2 Publish immediately, visible for everyone.
#3 Get everyone involved.
#4 OKRs are set jointly only. There is no top-down.
#5 Discussion happens in the team(s) only.
#6 There is no punishment, it is a joint experience.
#7 Ensure everyone is walking in the same direction.
3. Setting a direction & vision: leadership further involves setting a direction. This is ultimately the duty of both the customer and the organisation. Only jointly can a correct vision and direction be determined, else we miss the market requirements.
4. What is strategy in this context: strategy, at it's simplest, is a direction and a verified path how to get there (the later typically referred to as a roadmap). Most strategies are superb in painting a vision, but lack the roadmap aspects of it, so they ultimately fall short of explaining how to realise the vision.
5. How to execute: execution can only be agile. Over waterfall, it has several key advantages:
#1 Customer testing & fast market feedback!
#2 Product doesn‘t need to be fixed for the next 2 years
#3 Limited risk
#4 Significantly faster (if well executed)
#5 Attention: agile doesn‘t mean without a goal
We prefer to step on board when your company is looking to define its long-term strategies. Because that's when we can use the complete playing field - for developing strategies which result in a measurable improvement of your key indicators.
We've developed our own method for reorienting / relaunching digital projects. It takes a holistic approach to all the component parts: right from the business case, user experience and business requirements to the process design, technology and content.
Which is why we work intensively within interdisciplinary teams, make use of our frameworks, draw on our wide range of experience and lead workshops - until we've seen to it that you reach your goals. This process is typically followed by the development of a digital concept.
Navigating the Employee Lifecycle: The Secret Formula for a Successful InterviewAggregage
When it comes to interviewing, the best method is to have a standardized approach which is more impartial, more cost-effective, and faster. However, only a small percentage of HR and recruiters use this method despite its many benefits. Join TalentLyft's Recruitment Marketing Specialist and Head of Marketing Anja Zojceska to learn why, and how, you should be using this interviewing approach.
Optimizing the function of Product Management will reap huge benefits for a company. By up-leveling the process, people and tools in a holistic manner an organization can boost revenues and profits greatly. In fact, the 280 Group's Product Management Team Challenges survey showed that Product Managers believe that the profitability at their company would increase an average of 34% if Product Management were fully optimized. Yet 66% of respondents had no optimization plan to make this happen.
In this webcast you'll learn what the key factors are to optimize, how to measure and benchmark them and how to create a plan for doing so. Included will be a plan outline for Product Management optimization as well as strategies and tips based on the experiences of the 280 Group, who has transformed hundreds of Product Management organizations over the past 18 years.
Join Brian Lawley, CEO and Founder of the 280 Group, the world's leading Product Management and Product Marketing consulting and training firm, for this webinar. Brian is a Certified Product Manager, Certified Product Marketing Manager and an Agile Certified Product Manager. He is the author of five bestselling Product Management books, former President of the Silicon Valley Product Management Association and is the recipient of the AIPMM Excellence in Product Management Thought Leadership Award.
Business model examples and pitch (vers. 2014)Frieda Brioschi
Example of wellknown companies business model: Coca Cola (glass bottle!), Financial Times, LinkedIn, Groupon, Twitter, Facebook, Blockbuster and Google.
Community business model (geographically based, professional and online communities) and what is a business plan and how is diverse from a business model.
Info e tips about pitching, some questions that could be used as a track.
With this presentation I share my experience as a lean investor and lean startup trainer, a subject that I thoroughly believe in.
However, this approach is not a cure-all. This means that an overwhelming majority of ideas for startups or corporates will fail regardless of how you approach it. My goal is to show you how to find this out as fast as possible and with the least effort. I point out the many pitfalls when working with Lean Startup/Lean Innovation and how to avoid them.
The focus is on how to find out whether you have targeted the right customer segment and if not, how to iterate with problem & solution interviews between the Problem, Solution and the Customer Segment Fields of the Lean Canvas until you have reached the Problem/Solution Fit.
This webinar discussed developing new business models to address changing market landscapes. It introduced the business model lifecycle and explained that organizations can transform their business models to jump to new lifecycle curves. Various business model frameworks and patterns were presented, including the Business Model Canvas. The webinar emphasized validating new business models through experiments to test desirability, feasibility, and viability before full execution. Examples of business model transformations were provided.
Similar to What coaching stances can do for you in Kanban settings... (20)
Heavyweight agile Processes? Let's make them leaner!Michael Mahlberg
Heavyweight agile processes were discussed. The document explores lean principles from Toyota such as one-piece flow, pull systems, built-in quality, and visual management. It examines how these lean concepts can provide guidance for modern agile frameworks like Scrum and SAFe. Implementing ideas like limiting work-in-progress, emphasizing quality, and making processes visible can help agile practices become truly lean.
Wir schreiben das Jahr 2022 - die gesamte Enterprise-Welt wird von den großen Modellen agiler Skalierung beherrscht.
Die ganze Welt? Nein!
Als alternativer Weg zur "Skalierung" verfolgt die Kanban-Methode den
Ansatz, Organisationen als ein Netzwerk "lebender und atmender"
Services zu betrachten. Durch die Visualisierung des realen Flusses der
Arbeit und Wertschöpfung durch dieses Netzwerk kann die
Gesamtorganisation adaptiv und agil mit den Geschehnissen der
Außenwelt umgehen. So kann in großer Wettbewerbsvorteil erlangt
werden, gänzlich ohne Modelle, die für Teams gedacht waren,
künstlich zu "skalieren".
Ihr fragt euch nun vielleicht, wie solch in "Network of interconnected,
interdependent services" in der Praxis aussieht?
Genau das zeigten Markus
Wissekal und Michael Mahlberg in diesem Vortrag.
Agile Tuesday München: Was ist eigentlich aus Lean geworden?Michael Mahlberg
Als Agile anfing war Lean noch eng damit verwoben – mittlerweile liest man kaum noch davon.
Sollten wir jetzt nicht mehr auf Lean gucken? Wir meinen: Doch, gerade… und gucken uns das am Beispiel Kanban konkret an.
Die Wurzeln der Kanban Methode mit ihrem starken Fokus auf Change-Management und Empowerment liegen in der Arbeit von W. Edwards Deming und Tahichi Ohno – vielfach bekannt als TPS (Toyota Produktion System) oder ‚Lean‘.
Will man die Kanban Methode wirklich für mehr benutzen, als nur Zettel über die Wand zu schieben, ist ein Blick auf auf Lean nicht nur hilfreich, sondern eigentlich unvermeidlich. Gerade aus ‚dem Lean‘ kommen viele der Ansätze wie
das Visual Management (als Ansatz zum Empowerment ),
die Improvement Kata (als Führungsmethode),
das Jidoka Konzept (als Ansatz zum Umgang mit Automatisierung),
und viele andere Ideen für Change und Organisation, die wir in diesem Talk vorstellen und in den Kontext aktueller Change Ansätze (wie der Kanban-Methode, Scrum, SAFe, etc :-p ) bringen.
Process-Tinder – Wenn ich mich nur nach den schönen Bildern entscheide…Michael Mahlberg
Was, wenn der Prozess, in den man sich verliebt hat, nicht zur Organisation passt? Unternehmen umbauen? Prozess zurechtbiegen? Vernunftehe führen? Unreflektierte Nutzung des “bildhübschen Scrum” führt oft zu Kündigungswellen, Unzufriedenheit und Burn-out, ohne die erhoffte Glückseligkeit. Muss das so sein?
Scrum ist manchmal die “passende Lösung” – aber kaum jemand beschreibt die Bedingungen dazu und es gibt wenig Aussagen darüber, wie man handeln könnte, wenn die Bedingungen nicht passen. Deswegen versuchen wir das mal.
Was ist aus dem L-Wort (in Lean Kanban) geworden?Michael Mahlberg
Dürfen wir jetzt nicht mehr auf Lean gucken, nur weil die Kanban University den Begriff gestrichen hat? Wir meinen: Doch, gerade…
Gerade die Wurzeln der Kanban Methode mit ihrem starken Fokus auf Change-Management und Empowerment liegen in der Arbeit von W. Edwards Deming und Tahichi Ohno – vielfach bekannt als TPS (Toyota Produktion System) oder ‚Lean‘.
Will man die Kanban Methode wirklich für mehr benutzen, als nur Zettel über die Wand zu schieben, ist ein Blick auf auf Lean nicht nur hilfreich, sondern eigentlich unvermeidlich. Gerade aus ‚dem Lean‘ kommen viele der Ansätze wie
- das Visual Management (als Ansatz zum Empowerment ),
- die Improvement Kata (als Führungsmethode),
- das Jidoka Konzept (das den Menschen über die Maschine stellt),
und viele andere Change-Ideen, die wir in diesem Talk vorstellen und in den Kontext aktueller Change Ansätze (wie der Kanban-Methode, Scrum, SAFe, etc :-p ) bringen.
Jira ist für viele Kanbanista und Agilisten ein rotes Tuch – aber ist wirklich Jira das Problem? Und wie kann man Leiden mindern?
Agile Konferenzen, Blogs, Twitter - wo auch immer Lean- und Agile-Leute zusammenkommen, ist es ein Leichtes, einen Tumult bei dem die Emotionen hochgehen zu entfachen, wenn man Jira auch nur erwähnt. Aber warum gibt es immer eine so starke Reaktion? Liegt es an der Qualität des Tools? Michael Mahlbergs Erfahrung nach nicht. Das Problem liegt in der tatsächlichen Umsetzung in vielen Organisationen und - um fair zu sein - ähnliche Punkte könnte man auch bei anderen Tools anführen. Dieser Vortrag wird sich mit den systemischen, soziologischen und organisatorischen Problemen befassen, die (einige) von uns jedes Mal zusammenzucken lassen, wenn wir hören, dass unsere Kunden Jira verwenden. Und er wird zeigen, wie man mit diesen Problemen umgehen kann!
Der “Lean Decision Filter” von Kanban sagt eher “Value creation vor Flow” (und Flow vor der Eliminierung von Verschwendung). In Summe ermöglichen die sechs Prinzipien und sechs Praktiken weitaus mehr als nur Flow-Optimierung. Vor allem Change!
“Der primäre Grund, Kanban –oder besser: die Kanban Methode– anzuwenden ist Change Management. Alles andere ist dem untergeordnet.“ Wenn man diesem Zitat aus David Andersons 2010er Buch folgt, wird deutlich, dass Kanban für viel mehr eingesetzt werden kann, als nur für das Auffinden von Bottlenecks und Flussoptimierung. Gerade wenn man noch mal auf die Ursprünge im Lean Manufacturing guckt und die “6 x 6” (6 Praktiken und 6 Prinzipien) mit dem Filter “Was würde das aus einer ‘Lean’ Sicht bedeuten” zeigt sich deutlich, das Change-Management und kultureller Wandel zentrale Themen der Kanban Methode sind. So ist es auch nicht verwunderlich, dass die Regel “Value > Flow > Waste Elimination” jetzt mit dem Kanban Maturity Model und dem erneuten Fokus auf die Kanban Linsen nach vielen Jahren als “Lean Decision Filter” wieder einen prominenten Platz auf dem KMM-Culture-Poster gefunden hat. In diesem Talk gucken wir uns ein bisschen mehr von den Aspekten an, die die Kanban-Methode von einem einfachen Anwenden der Theory of Constraints aus den 1980ern mit dem reinen Fokus auf Flussoptimierung unterscheidet und den Change-Gedanken in den Fokus rücken.
What's in a Story? Drei Ansätze, um mit Anforderungen gemeinsam erfolgreich z...Michael Mahlberg
"Anforderung = Story", stimmt das? Das Konzept der User Story scheint fest etabliert – als Anforderungsdokument, als Schätzgrundlage und als oft einzige Möglichkeit mit Anforderungen umzugehen. Der Ursprung des Konzepts Story hat viel mehr mit dem Vorgehen als mit dem Format einer Anforderung zu tun. Die noch in XP-Zeiten beschriebenen Phasen Card, Conversation und Confirmation (kurz CCC) beschreiben dabei viel mehr als nur die Entstehung einer Anforderung. In dieser Session werden die ursprünglichen Ideen hinter dem Konzept "Story" deutlich und wir durchleben verschiedene Ansätze, auch heute wieder gemeinsam sinnvoll(er) – im agilen Sinn – mit Anforderungen umzugehen.
Als das 'Manifest für agile Softwareentwicklung' 2001 geschrieben wurde, war es ein Zeitzeuge für eine Aufbruchsstimmung hin zu mehr Entscheidungskompetenz and den Stellen, an denen die Entscheidungen auch umgesetzt werden. Für die Aussenwelt wurde damit ein Wandel sichtbar, der schon Jahre vorher begonnen hatte und erfolgreiche Projekte gekennzeichnet hat. Mittlerweile aber hat sich ein stark vereinfachtes 'Agile' gerade im Umfeld großer Unternehmen zu einem Treiber für Stress und Frustration bis hin zur inneren Kündigung und zum Burnout entwickelt. Besonders trifft dies Funktionen, die Teamübergreifend agieren sollen und mit den (scheinbaren?) Widersprüche zwischen Selbstorganisation und Wohl der ganzen Unternehmung konfrontiert werden.
In diesem Vortrag werden persönliche und organisatorische Ansätze gezeigt um diese Situation anzugehen und differenziert mit den Thema Agilität und Selbstorganisation im Konzern umzugehen.
Michael Mahlberg - Leichtgewichtige Kanban-Metriken auf der LKCE 2018Michael Mahlberg
Slides zum Vortrag auf der LKCE 2018 (auf Deutsch) - siehe auch https://www.slideshare.net/lkce/ bzw. http://lkce18.leankanbance.com/schedule/#session-7 für eine vollständige Beschreibung.
[Originally held at Topconf Düsseldorf October 2017]
Your agile process has become boring or ineffective?
Those discussions about user stories have become old? That burn down chart that once provided guidance has become dull? We could go on about things that might have taken a turn for worse in some agile projects and will do so in this short talk. We will not only shed some light on those practices and their place in Agile environments, but also – and more importantly – introduce some alternatives that are still absolutely in line with agile processes (e.g. Scrum) and the agile mindset.
Why the title? Well, that is a hat-tip to Scrum. One of the things that changed in the 2016 edition of the Scrum Guide was that the term "ceremony" has been replaced with "event" – reflecting a significant mind-shift and subtly hinting at the issues with cargo-cult agile.
https://www.topconf.com/conference//duesseldorf-2017/talk/from-ceremonies-to-events-reducing-cargo-cult-and-improving-efficiency/
The Product Owner's Survival Kit - ein Überblick [DE]Michael Mahlberg
Seit die Product Owner zu den Rettern des Projektes geworden sind, verlangt „die ganze Welt“ von ihnen, dass sie ohne genaue Aufgabendefinition (längst wird der Begriff ja auch außerhalb der Scrum-Welt benutzt) aufgrund diffus beschriebener Fähigkeiten Anforderungen auf magische Art mit allen Stakeholdern friedlich abgestimmt bekommen, sie den Umsetzern wie mit dem Nürnberger Trichter verständlich machen und nebenbei noch das Releasemanagement mit erledigen. Aber wo ist der Werkzeugkasten dafür?
Ein Survival-Toolkit, das links und rechts der reinen Software-Welt Tools vom Morphologischen Kasten über Systemisches Konsensieren bis hin zur Deckungsbeitragsrechnung beleuchtet, wird in dieser Session feil geboten. Dass Kernthemen wie Story-Mapping, Backlog-Pflege, Buy-a-Feature, CCC dabei ebenfalls einsortiert werden, versteht sich von selber.
This document discusses the A3 problem solving approach and provides examples of different types of A3 reports. The A3 approach uses a logical, evidence-based process based on the PDCA cycle to drive continuous improvement. It emphasizes brevity, objectivity, and visualization. Different types of A3 reports are used for problem solving, proposals, and status updates. Problem solving reports focus on root cause analysis, proposals on planning, and status reports on results and follow up actions.
1) The document discusses team dynamics models beyond Tuckman's classic forming, storming, norming, performing model. It presents Drexler and Sibbet's model of team phases focused on creating and sustaining teams.
2) Drexler and Sibbet's model includes phases focused on why the team exists, building trust among members, clarifying goals, committing to how the team will operate, implementing work, achieving high performance, and renewing the team.
3) The document facilitates a group discussion mapping properties of successful teams to Drexler and Sibbet's model and identifying indicators and actions for progressing from one phase to the next.
Je häufiger und länger IT-Systeme geändert oder erweitert werden, desto teurer und riskanter wird ihre Wartung und Weiterentwicklung – weil ihre Architektur immer mehr degradiert. Der Grund: Wartungsprojekte investieren zu wenig in architekturelle Verbesserung. Als Abhilfe stellen wir Ihnen einige praxistaugliche methodische Werkzeuge aus Ökonomie und Software-Engineering vor, mit denen Sie Manager vom ökonomischen Sinn kontinuierlicher Architekturverbesserung überzeugen können – und Techniker in die Lage versetzen, diese erfolgreich durchzuführen.
The [German] Slides from a presentation where Personal Kanban, The Kanban Method (Anderson), gtd and other techniques for organizing your work are put into context – both generally as with respect to each other..
Michael mahlberg exploratory-testing-the_missing_half_of_bddMichael Mahlberg
"We should just call it testing - when it's not exploratory testing it's not real testing anyway" -Twitter, Summer 2011 Lately many professional testers have started to make a clear distinctions between thing that we call testing (like TDD and BDD) and what they consider testing - referring to TDD and BDD mostly as checking. And actually I – and I would think many of you as well – have seen projects with a test coverage of 80% and more that still fail to meet the clients' needs. Even though they meet the specifications perfectly. This points to some value that could be added to techniques like BDD and TDD by embracing the ideas from people like James Marcus Bach, Paul Carvalho and Michael Bolton. After giving an overview of current trends in the testing community like ET (exploratory testing) and ATDD (Acceptance Test Driven Development) this session will try to do exactly that: discuss the - often missing - intersection between BDD and exploratory testing and suggest ways to fill it.
Here are a few ways the UsersController could be refactored to better follow the Interface Segregation Principle:
1. Extract authentication/authorization logic into a separate AuthenticationController concern.
2. Extract user profile/account management logic into an AccountsController.
3. Extract activation/registration logic into a separate RegistrationController.
4. Create separate interfaces/controllers for different user roles like AdminUsersController vs RegularUsersController.
This avoids forcing all user-related actions onto a single controller, allowing each controller to focus on specific user workflows and responsibilities. Clients like regular users and admins would interact with specialized interfaces rather than depending on a monolithic UsersController.
Sethurathnam Ravi: A Legacy in Finance and LeadershipAnjana Josie
Sethurathnam Ravi, also known as S Ravi, is a distinguished Chartered Accountant and former Chairman of the Bombay Stock Exchange (BSE). As the Founder and Managing Partner of Ravi Rajan & Co. LLP, he has made significant contributions to the fields of finance, banking, and corporate governance. His extensive career includes directorships in over 45 major organizations, including LIC, BHEL, and ONGC. With a passion for financial consulting and social issues, S Ravi continues to influence the industry and inspire future leaders.
A presentation on mastering key management concepts across projects, products, programs, and portfolios. Whether you're an aspiring manager or looking to enhance your skills, this session will provide you with the knowledge and tools to succeed in various management roles. Learn about the distinct lifecycles, methodologies, and essential skillsets needed to thrive in today's dynamic business environment.
Employment PracticesRegulation and Multinational CorporationsRoopaTemkar
Employment PracticesRegulation and Multinational Corporations
Strategic decision making within MNCs constrained or determined by the implementation of laws and codes of practice and by pressure from political actors. Managers in MNCs have to make choices that are shaped by gvmt. intervention and the local economy.
Enriching engagement with ethical review processesstrikingabalance
New ethics review processes at the University of Bath. Presented at the 8th World Conference on Research Integrity by Filipa Vance, Head of Research Governance and Compliance at the University of Bath. June 2024, Athens
Originally presented at XP2024 Bolzano
While agile has entered the post-mainstream age, possibly losing its mojo along the way, the rise of remote working is dealing a more severe blow than its industrialization.
In this talk we'll have a look to the cumulative effect of the constraints of a remote working environment and of the common countermeasures.
A team is a group of individuals, all working together for a common purpose. This Ppt derives a detail information on team building process and ats type with effective example by Tuckmans Model. it also describes about team issues and effective team work. Unclear Roles and Responsibilities of teams as well as individuals.
Ganpati Kumar Choudhary Indian Ethos PPT.pptx, The Dilemma of Green Energy Corporation
Green Energy Corporation, a leading renewable energy company, faces a dilemma: balancing profitability and sustainability. Pressure to scale rapidly has led to ethical concerns, as the company's commitment to sustainable practices is tested by the need to satisfy shareholders and maintain a competitive edge.
Public Speaking Tips to Help You Be A Strong Leader.pdfPinta Partners
In the realm of effective leadership, a multitude of skills come into play, but one stands out as both crucial and challenging: public speaking.
Public speaking transcends mere eloquence; it serves as the medium through which leaders articulate their vision, inspire action, and foster engagement. For leaders, refining public speaking skills is essential, elevating their ability to influence, persuade, and lead with resolute conviction. Here are some key tips to consider: https://joellandau.com/the-public-speaking-tips-to-help-you-be-a-stronger-leader/
Impact of Effective Performance Appraisal Systems on Employee Motivation and ...Dr. Nazrul Islam
Healthy economic development requires properly managing the banking industry of any
country. Along with state-owned banks, private banks play a critical role in the country's economy.
Managers in all types of banks now confront the same challenge: how to get the utmost output from
their employees. Therefore, Performance appraisal appears to be inevitable since it set the
standard for comparing actual performance to established objectives and recommending practical
solutions that help the organization achieve sustainable growth. Therefore, the purpose of this
research is to determine the effect of performance appraisal on employee motivation and retention.
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.
3. Slide #2016 Michael Mahlberg 3
Slide #2016 Michael Mahlberg
Michael Mahlberg
2 Slide #2016 Michael Mahlberg 4
Photo Credit:
Some rights reserved by Bernd Thaller
https://flic.kr/p/DZmSqm
Photo Credit:
Some rights reserved by Marcus Rahm
https://flic.kr/p/gQZqR4
Vienna
Slide #2016 Michael Mahlberg 5
Photo Credit:
Some rights reserved by Bernd Thaller
https://flic.kr/p/DZmSqm
Photo Credit:Some rights reserved by mae noelle
https://flic.kr/p/5dJW2C
Photo Credit:
Some rights reserved by Jason Scragz
https://flic.kr/p/DYivH 1967
Slide #2016 Michael Mahlberg 6
Photo Credit:
Some rights reserved by StaffanVilcans
https://flic.kr/p/76kd2M
1982
Slide #2016 Michael Mahlberg 7
1985
Photo Credit:
Some rights reserved by Sam valadi
https://flic.kr/p/s2T93f
Slide #2016 Michael Mahlberg 8
1989
Slide #2016 Michael Mahlberg 9
Photo Credit:
Some rights reserved by Lothar Monshausen
https://flic.kr/p/9Ykjpq
1990ies
Slide #2016 Michael Mahlberg 10
Photo Credit:
Some rights reserved by Stefan Leijon
https://flic.kr/p/nADSqk
1990ies
Slide #2016 Michael Mahlberg 11
Photo Credit:
Some rights reserved by Tony Hisgett
https://flic.kr/p/bfsi6Z
1990ies
4. Slide #2016 Michael Mahlberg 4
Slide #2016 Michael Mahlberg 12
1990ies
Function
Process
Process
Elementary Process
Elementary Process
Elementary Process
Elementary Process
SUBJECT AREA 1
NTT1
NTT2
NTT-A
NTT-B
NTT-D
NTT-C
Slide #2016 Michael Mahlberg 13
Photo Credit:
Some rights reserved by David Blaikie
https://flic.kr/p/cYWvfA
~2000
Slide #2016 Michael Mahlberg 14
Photo Credit:
Some rights reserved by Bob Bob
https://flic.kr/p/82CsnK ~2003
Slide #2016 Michael Mahlberg 15
~2008
Slide #2016 Michael Mahlberg 17
~2011
Slide #2016 Michael Mahlberg 20
2008
Slide #2016 Michael Mahlberg 21
Slide #2016 Michael Mahlberg 22
P
olving
eadership
roblem
S
L
Slide #2016 Michael Mahlberg 23
6. Slide #2016 Michael Mahlberg
Coaching Stances
How they can make a difference in Kanban settings
LKBX 2016
6
7. Slide #2016 Michael Mahlberg
Caveat:
“All Models Are Wrong –
But Some Are Useful”
— George E. P. Box
7
8. Slide #2016 Michael Mahlberg
What Kind Of Coach?
8
Photo Credit:
Some rights reserved by Emslichter
https://pixabay.com/en/setra-s6-50-years-coach-collect-1762942/
Photo Credit:Some rights reserved by Airviews Photography
https://flic.kr/p/eaeHLY
Photo Credit:
Some rights reserved by keijj44
https://pixabay.com/en/baseball-runner-coach-little-
Photo Credit:
Some rights reserved by dankueck
https://flic.kr/p/bg7ita
9. Slide #2016 Michael Mahlberg 9
XP-Coach
Agile-Coach
Kanban-Coach
Photo Credit:
Some rights reserved by MIKIYoshihito
https://flic.kr/p/7hNsQ9
10. Slide #2016 Michael Mahlberg 10
Photo Credit:
Some rights reserved by dankueck
https://flic.kr/p/bg7ita
…partnering with clients in a
thought-provoking and creative
process that inspires them to
maximize their personal and
professional potential.
Professional
Coaching
11. Slide #2016 Michael Mahlberg
THE COACHING STANCE
• The solution lies within the
client
• Coach and client are at an
equal level (peers)
• The coach is not the one to
find the solution
• The client is the expert for
them self
• The coach offers a container
without judgement
• Coach and client work with
with an open outcome
11
12. Slide #2016 Michael Mahlberg
WHAT OTHER
STANCES?
12
Photo Credit:
Some rights reserved by Adrian Scottow
https://flic.kr/p/8fqtzE
13. Slide #2016 Michael Mahlberg
Photo Credit:
Some rights reserved by keijj44
https://pixabay.com/en/baseball-runner-coach-little-league-1536097/
THE STANCES OF THE
SPORTS COACH
13
14. Slide #2016 Michael Mahlberg
Photo Credit:
Some rights reserved by keijj44
https://pixabay.com/en/baseball-runner-coach-little-league-1536097/
14
Sports analogies Inspired
by discussions with
Dan Brown
at the #KLR16
15. Slide #2016 Michael Mahlberg
Photo Credit:
Some rights reserved by keijj44
https://pixabay.com/en/baseball-runner-coach-little-league-1536097/
STANCES OF THE SPORTS-COACH
Tell
Show
Teach
Sell
Train
Coach
15
(!)
16. Slide #2016 Michael Mahlberg
TELL
16
Photo Credit:
Some rights reserved by suc
https://pixabay.com/en/talk-shout-megaphone-tell-say-man-457540/
17. Slide #2016 Michael Mahlberg
SHOW
17
Photo Credit:
Some rights reserved by Mojpe
https://pixabay.com/en/mother-son-pointing-ship-sea-1613726/
18. Slide #2016 Michael Mahlberg
TEACH
18
Photo Credit:
Some rights reserved by geralt
https://pixabay.com/en/board-classroom-education-school-1523537/
19. Slide #2016 Michael Mahlberg
TRAIN
19
Photo Credit:
Some rights reserved by Faldrian.
https://flic.kr/p/eCKtiv
20. Slide #2016 Michael Mahlberg
SELL
20
Photo Credit:
Some rights reserved by Herry Lawford
https://flic.kr/p/nUnyWz
21. Slide #2016 Michael Mahlberg
Photo Credit:
Some rights reserved by dankueck
https://flic.kr/p/bg7ita
COACH (!)
21
24. Slide #2016 Michael Mahlberg
COACHING STANCES
• Coaching ⩯ Professional Coaching
• THE coaching stance (solution lies within the client etc.)
• Coaching ⩯ Sports Coaching
• Several stances for the coach – One of them is similar to the
stance the coach assumes in Professional Coaching
24
25. Slide #2016 Michael Mahlberg
∆
INTERACTION STANCES
(INCLUDING COACHING)
25
Consulting
Mentoring
Coaching
➙ Delta in knowledge
➙ Delta in experience
➙ Delta in process-mastery
(coaching-process)
26. Slide #2016 Michael Mahlberg
Coaching Stances
How can they make a difference in
Kanban settings?
26
✓
28. Slide #2016 Michael Mahlberg 28
Introducing Sustaining
A personal point of view
29. Slide #2016 Michael Mahlberg 29
Introducing Sustaining
A personal point of view
30. Slide #2016 Michael Mahlberg
STATIK
Systems
Thinking
Approach
To
Introducing
Kanban
30
https://www.linkedin.com/pulse/statik-systems-thinking-approach-implementing-kanban-david-anderson
31. Slide #2016 Michael Mahlberg
STATIK
• Understand what makes the service fit for purpose for the customer
• Understand sources of dissatisfaction with the current system
• Analyze demand
• Analyze capability
• Model workflow
• Discover classes of service
• Design the Kanban system
• Socialize the design and negotiate implementation
31
https://www.linkedin.com/pulse/statik-systems-thinking-approach-implementing-kanban-david-anderson
32. Slide #2016 Michael Mahlberg
KANBAN PRACTICES
• Visualize
• Limit work in progress
• Manage flow
• Make policies explicit
• Implement feedback loops
• Improve collaboratively, evolve experimentally
32
33. Slide #2016 Michael Mahlberg 33
Introducing Sustaining
A personal point of view
38. Slide #2016 Michael Mahlberg 38
Introducing Sustaining
Evolution
[of the underlying system(s)]
39. Slide #2016 Michael Mahlberg
Photo Credit:
Some rights reserved by keijj44
https://pixabay.com/en/baseball-runner-coach-little-league-1536097/
STANCES OF THE SPORTS-COACH
Tell
Show
Teach
Sell
Train
Coach
39
(!)
40. Slide #2013 Michael Mahlberg
EVOLVING KANBAN SYSTEMS
40
Tell Show Teach Sell Train Coach
Visualize X X X X X
Limit WIP X X X
Manage flow X X X
Explicit policies X X X X
Feedback loops – X X X
Scientific method – X X X X
41. Slide #2016 Michael Mahlberg
INTERNAL STANCE OF THE COACH
• For example:
• Co-active coaching (e.g. H. Kimsey-House et.al)
• Systemic coaching (e.g. P.W. Gester)
• Solution focused coaching (e.g. Steve de Shazer)
• Provocative coaching (e.g. Frank Farelly)
41
42. Slide #2016 Michael Mahlberg
AN EXAMPLE…
• What’s the optimal WIP-Limit?
• For what purpose (aka why) do you want to know the
optimal WIP-limit?
• How does the optimal WIP-limit affect the system?
• How would you recognize that you have found the optimal
WIP-limit
• Why should you need a WIP-limit at all?
42
43. Slide #2016 Michael Mahlberg
INTERNAL STANCE OF THE COACH
TECHNIQUE OF THE COACH
• For example:
• Co-active coaching (e.g. H. Kimsey-House et.al.)
• Systemic coaching (e.g. P.W. Gester)
• Solution focused coaching (e.g. Steve de Shazer)
• Provocative coaching (e.g. Frank Farelly)
43
45. Slide #2016 Michael Mahlberg
It’s not the coach who
gets the gold medal!
45
Photo Credit:
Some rights reserved by Michael (a.k.a. moik) McCulloughhttps://flic.kr/p/9ECRw3
46. Slide #2016 Michael Mahlberg
COACHING AGREEMENT
46
Photo Credit:
Some rights reserved by jarmoluk
https://pixabay.com/en/document-agreement-documents-sign-428335/
47. Slide #2016 Michael Mahlberg 47
“It is only possible to coach a
client who wants to be coached”
Part of the coaching agreement is
the client’s commitment to work
on their defined goals
Photo Credit:
Some rights reserved by Broad Bean Media
https://flic.kr/p/dm7ZQ1
48. Slide #2016 Michael Mahlberg
What Kind Of Coach?
48
Photo Credit:
Some rights reserved by Emslichter
https://pixabay.com/en/setra-s6-50-years-coach-collect-1762942/
Photo Credit:Some rights reserved by Airviews Photography
https://flic.kr/p/eaeHLY
Photo Credit:
Some rights reserved by keijj44
https://pixabay.com/en/baseball-runner-coach-little-
Photo Credit:
Some rights reserved by dankueck
https://flic.kr/p/bg7ita
49. Slide #2016 Michael Mahlberg
AGILE COACHING COMPETENCY
49
Agile-Lean Practitioner Professional
Coaching
Teaching
Mentoring
Technical
Mastery
Business
Mastery
Transformation
Mastery
Applies Agile practices,
lives Agile values Partnering with clients in a
creative process that inspires their
personal and professional potential (from ICF)
Facilitating
Source:
Agile Coaching Competency Model
http://agilecoachinginstitute.com/agile-coaching-resources/
Instructing others in
specific knowledge,
skills and perspective
Sharing knowledge, skills &
perspectives that foster the
personal and professional
growth of someone else
Technical expertise
as a software
craftsperson
Expert at
business-value-
driven innovation
and product
development
Expertise as an
organizational development
and change catalyst
A neutral process holder who guides groups
through processes that help them come
to solutions and make decisions
50. Slide #2016 Michael Mahlberg
COACHING STANCES
Tell
Show
Teach
Sell
Train
Coach
50
(!)
The solution lies within
the client
The client is the expert
for them self
Coach and client work
together on an open
outcome
∆Consulting
Mentoring
Coaching
➙ Delta in knowledge
➙ Delta in experience
➙ Delta in process-mastery
(coaching-process)
53. Slide #2013 Michael Mahlberg
CONTACT INFORMATION
53
• If you have questions, don’t hesitate to contact me via e-mail
at: mm@michaelmahlberg.com
• You can also find me onTwitter as MMahlberg
• I sometimes blog on http://agile-aspects.michaelmahlberg.com
• My homepage is http://www.michaelmahlberg.de