This document outlines an agenda for a workshop on prioritizing product backlogs in a fun and game-like format. The workshop includes introductions, exercises to generate new ideas for a fictional city and prioritize its issues, breaks for discussion, and lessons on prioritization techniques like MVP, MAP, and MoSCoW. The goal is to give participants hands-on experience planning and ranking potential features and improvements for a simulated product.
Mature product backlog and how to deal with it - workshop - main slide deckBartek Gatz
The document discusses strategies for managing a mature product backlog, including incubating new ideas before adding them to the backlog, prioritizing ideas based on impact and cost, and using exercises to demonstrate prioritizing a city's backlog of issues and new ideas. Teams are asked to generate new ideas for improving a fictional city, prioritize the ideas, then reprioritize after new issues arose. The goal is to introduce techniques for maintaining a healthy backlog focused on the most important work.
The values from the Agile Manifesto don’t seem to say much about the craft of software engineering. In fact, they don’t say anything about engineering at all. However, digging a little bit deeper, one quickly realizes that the benefits of Agile methods and practices cannot be realized with low quality software. Agile depends on engineering excellence.
So forget about Agile for a moment, at least the process side of things, and pay attention to the craft of software engineering; or in other words pay attention to building software the right way. Because only then you will be able to rapidly and continuously build the right software.
This document discusses continuous delivery practices. It begins by highlighting benefits from reports such as higher IT performance, organizational performance, and throughput/stability. It then discusses concepts like delivering value to customers through early and continuous delivery, reducing risk through small frequent changes, and tracking real progress. The rest of the document details practices like automation, version control, continuous integration, deployment pipelines, and mindsets like being lean and agile. It provides examples of deployment pipelines and automation of testing, infrastructure, and deployments. It emphasizes automating as much as possible and not ignoring data.
What is Agile & Agile Project Management?. Introduction to Plan-based vs value-driven development; Scrum framework and roles and ceremonies; self-organised team, agile values. and leadership
What is wrong with projects? Projects don't work in a VUCA world anymore, particulary not in IT & digital business! And "Agile" isn't the solution either... Is it #noprojects?
The Product Management Vacuum and the 3 V'sDon McGreal
In between the larger organizational goals and the day-to-day work of Development Teams, exists a vacuum. The thing about any vacuum is that it has an innate need to be filled. If we are not careful, this 'Product Management Vacuum' will get filled with meaningless busy work and extensive task management. Being busy without clear direction.
This session introduces the 3 V's -- Vision, Value, Validation -- as a way to get out in front of this problem.
Mature product backlog and how to deal with it - workshop - main slide deckBartek Gatz
The document discusses strategies for managing a mature product backlog, including incubating new ideas before adding them to the backlog, prioritizing ideas based on impact and cost, and using exercises to demonstrate prioritizing a city's backlog of issues and new ideas. Teams are asked to generate new ideas for improving a fictional city, prioritize the ideas, then reprioritize after new issues arose. The goal is to introduce techniques for maintaining a healthy backlog focused on the most important work.
The values from the Agile Manifesto don’t seem to say much about the craft of software engineering. In fact, they don’t say anything about engineering at all. However, digging a little bit deeper, one quickly realizes that the benefits of Agile methods and practices cannot be realized with low quality software. Agile depends on engineering excellence.
So forget about Agile for a moment, at least the process side of things, and pay attention to the craft of software engineering; or in other words pay attention to building software the right way. Because only then you will be able to rapidly and continuously build the right software.
This document discusses continuous delivery practices. It begins by highlighting benefits from reports such as higher IT performance, organizational performance, and throughput/stability. It then discusses concepts like delivering value to customers through early and continuous delivery, reducing risk through small frequent changes, and tracking real progress. The rest of the document details practices like automation, version control, continuous integration, deployment pipelines, and mindsets like being lean and agile. It provides examples of deployment pipelines and automation of testing, infrastructure, and deployments. It emphasizes automating as much as possible and not ignoring data.
What is Agile & Agile Project Management?. Introduction to Plan-based vs value-driven development; Scrum framework and roles and ceremonies; self-organised team, agile values. and leadership
What is wrong with projects? Projects don't work in a VUCA world anymore, particulary not in IT & digital business! And "Agile" isn't the solution either... Is it #noprojects?
The Product Management Vacuum and the 3 V'sDon McGreal
In between the larger organizational goals and the day-to-day work of Development Teams, exists a vacuum. The thing about any vacuum is that it has an innate need to be filled. If we are not careful, this 'Product Management Vacuum' will get filled with meaningless busy work and extensive task management. Being busy without clear direction.
This session introduces the 3 V's -- Vision, Value, Validation -- as a way to get out in front of this problem.
Increasing Business Impact - Focusing on value deliveryNarek Alaverdyan
This document discusses shifting from an IT to a product mindset. It emphasizes focusing on customers and delivering value over cost and schedule. This involves adopting a profit center mentality and continuously improving products. DevOps is presented as a culture of collaboration, not a role or department. It involves developers understanding infrastructure and operations understanding code. Validated learning is discussed as focusing on minimum viable products, testing and learning through experiments and A/B testing to reduce waste and improve conversions. The goal is a team that loves finding better ways to delight customers and increase market share through cultural evolution.
Fix-Price Projects And Agile – PyCon SettePeter Bittner
You are a digital agency struggling with your Django projects. You’re over budget and you’ve run out of time, that’s the norm not the exception. And of course you promise to deliver all features on time for a fixed budget, don’t you? – And nobody told you this is a problem?
See the original presentation at http://slides.com/bittner/pycon7-fix-price-projects-and-agile
The document summarizes Gene Kim's presentation on breaking the chronic conflict between operations and development teams through a DevOps transformation. It outlines the downward spiral caused by the conflict, including fragile applications, long fix times, and frustrated customers. It then presents the philosophies of DevOps, including systems thinking to increase flow, amplifying feedback loops, and creating a culture of experimentation. Finally, it provides prescriptive phases for implementing DevOps, such as extending agile processes and creating environments, improving release processes, and prioritizing continuous improvement.
This document discusses various iterative software development models, including the spiral model, win-win spiral model, and cleanroom methodology. The spiral model is risk-driven and involves iterating through phases of planning, risk assessment, engineering, and evaluation. The win-win spiral model seeks to reconcile stakeholder objectives through negotiation. Cleanroom methodology emphasizes technical reviews, incremental development, and testing to reduce defects. Alternative models like hacking are also discussed for low-risk or disposable projects. Overall, the iterative models attempt to address limitations of the traditional waterfall model by incorporating feedback loops, prototyping, and incremental delivery.
This document discusses various aspects of managing software development projects, including:
- Developing a software development plan that defines the project scope, requirements, schedule and budget.
- Estimating project size, effort and costs using metrics from past projects and estimation models like COCOMO.
- Identifying and planning for risks that could impact the project.
- Choosing an appropriate development environment and tools.
- Defining deliverables for the customer and development process.
This document discusses user experience (UX), agile product management, and delivering software that meets user needs. It advocates for an iterative development process that incorporates UX research and testing. Product managers are advised to work closely with UX designers to validate assumptions through usability testing, measure outcomes, and prioritize addressing UX issues. An agile, lean approach that rapidly builds and learns from user feedback is presented as the best way to deliver innovative products that customers want and provide a competitive advantage.
The document discusses how to create fast software development cycles without breaking systems by adopting a DevOps approach using systems thinking, amplifying feedback loops, and fostering a culture of experimentation and learning to break down silos between development and operations teams and continuously improve processes. It also outlines some initial steps like forming a DevOps leadership team to help coordinate the transformation.
Project management in the age of accelerating change - IT/Tech specificLuca Minudel
This document provides an overview of agile project management practices for traditional project managers. It discusses how the context for management has changed in an age of accelerating change, rendering traditional management tools and mindsets less effective. Agile principles emphasize problem-solution co-evolution, solution co-creation, and simplicity. Common agile practices like iterations in sprints and emphasis on working software aim to increase learning and reduce the cost of change. The roles of product owner, scrum master, and self-organizing teams are described. Information radiators like burn-up charts and team boards promote transparency.
What's Agile ? Introduction to Agile methodsBruno Sbille
The document provides an introduction to Agile methods. It discusses that many IT projects do not succeed due to being over budget and schedule. Agile aims to deliver working software frequently through iterative development and valuing individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan. The document then covers Scrum and user stories which are part of the Agile methodology.
This document discusses alternatives to traditional software estimation approaches, such as the #NoEstimates concept. It outlines ideas from thinkers like Thomas Edison and Lean principles as the basis for considering "crazy ideas" in software development. The #NoEstimates approach focuses on prioritizing work, slicing stories finely, measuring throughput and lead times rather than velocity, and delivering value continuously with trust and transparency.
This document provides an overview and agenda for a webinar on continuous delivery in the enterprise. The webinar will define continuous delivery and differentiate it from continuous integration, Agile, quality and DevOps practices. It will explore the continuous delivery pipeline and key aspects like continuous development, integration and the ability to continuously release software. Attendees will learn about their role in continuous delivery and why it is important. The webinar will also discuss tools, products and solutions for continuous delivery and include case studies. It aims to explain how organizations can adopt continuous delivery practices.
Maximizing the impact of UX in an agile environment: Mixing agile and lean UXBrilliant Experience
When companies adopt an agile development environment, UX teams often feel like they just lost their seat at the table. It’s never easy to change, but by adapting your UX practices to accommodate agile, you can have the impact on design you always wanted.
Maximizing the impact of UX in an agile environment: Mixing agile and Lean UXJohn Whalen
When companies adopt an agile development environment, UX teams often feel like they just lost their seat at the table. It’s never easy to change, but by adapting your UX practices to accommodate agile, you can have the impact on design you always wanted.
PR-272: Accelerating Large-Scale Inference with Anisotropic Vector QuantizationSunghoon Joo
PR-272: Accelerating Large-Scale Inference with Anisotropic Vector Quantization
[Guo et al., ICML 2020]
Paper link: https://arxiv.org/abs/1908.10396
Video presentation link: https://youtu.be/cU46yR-A0cs
reviewed by Sunghoon Joo
Data science is not Software Development and how Experiment Management can ma...Jakub Czakon
Working on data science projects that are run as if they were software development can sometimes feel like trying to fit a square peg in a round hole. In this talk, I will explain why that happens and what people do to try and fix it. Lately, in the context of machine learning, the concept of experiment management, which treats ml experiments as first-class citizens, has been gaining a lot of traction. I will discuss what it is, what are the benefits of using it, and how you can apply it in your work to make run your projects more efficiently.
DevOpsDays Baltimore 2017.
Product owners are under pressure from Marketing and Leadership to focus on features, while operability (availability, performance, monitoring, etc) are an afterthought to be bolted on later. Deployments fail, customers complain, and work isn't fun. How can DevOps reach out to Product?
People from a "Product background" often have zero technical experience, but find themselves needing to dictate the deliverables. Product owners are under great pressure from Marketing and Leadership to focus on "features" from a customer perspective; the so-called "non-functional requirements" often fall by the wayside. Operability - monitorabilty, recoverability, availability, performance, among other aspects - is difficult to bake into an application that was developed without such consideration.
This talk will present practical approaches to bridge-building between Ops and Product. Focusing especially on cross-functional Agile teams with leadership with little or no Ops background, we will explore whether "planning the work will result in the planned work being the work that is done." When working with a mixed team, doing development, deployment, incident response, and everything in support of that, such plans go off the rails. Methods of championing Ops needs while avoiding "the sky is falling" perceptions will be presented. What kinds of unplanned work exist? Are there steps we can take to convert unplanned work into planned work? How does work flow through the team? How does unplanned work disrupt the flow?
Product owners are under pressure from Marketing and Leadership to focus on features, while operability (availability, performance, monitoring, etc) are an afterthought to be bolted on later. Deployments fail, customers complain, and work isn't fun. How can DevOps reach out to Product?
People from a "Product background" often have zero technical experience, but find themselves needing to dictate the deliverables. Product owners are under great pressure from Marketing and Leadership to focus on "features" from a customer perspective; the so-called "non-functional requirements" often fall by the wayside. Operability - monitorabilty, recoverability, availability, performance, among other aspects - is difficult to bake into an application that was developed without such consideration.
This talk will present practical approaches to bridge-building between Ops and Product. Focusing especially on cross-functional Agile teams with leadership with little or no Ops background, we will explore whether "planning the work will result in the planned work being the work that is done." When working with a mixed team, doing development, deployment, incident response, and everything in support of that, such plans go off the rails. Methods of championing Ops needs while avoiding "the sky is falling" perceptions will be presented. What kinds of unplanned work exist? Are there steps we can take to convert unplanned work into planned work? How does work flow through the team? How does unplanned work disrupt the flow?
This document proposes several models for measuring individual productivity of knowledge workers or technologists. It discusses challenges in measuring productivity in knowledge-based roles and industries. It then outlines 5 potential simple solutions that use tools, peer reviews, surveys and third-party evaluations. The models aim to provide objective and comprehensive productivity measurement while accounting for complexity factors like project size and technical difficulty. The document concludes by stating that determining the best approach requires further discussion.
Backlog City workshop - task description (updated Dec'19)Bartek Gatz
- The document provides background information on Backlog City, which is divided into 4 districts with varying incomes, infrastructure, crime rates, and access to transportation.
- District A has the largest population of 1.5 million with the lowest median income of $300. It has old infrastructure and high crime.
- District B has a population of 0.3 million with a median income of $800. It contains the mayor's office and tourist attractions but also pickpockets.
- District C has 0.7 million inhabitants with a median income of $1000. It is an upper middle-class area with light industry and shopping centers.
- District D is the wealthiest with a median income of $5000
Product Management - pitfalls of Data Driven DevelopmentBartek Gatz
The document discusses various pitfalls of data-driven development from a product management perspective, focusing on agile software development. It outlines five main pitfalls: 1) having the wrong mindset for failure when conducting experiments, 2) difficulties perceiving progress, 3) overreliance on collecting more data when facing deadlocks, 4) unexpected downsides of democracy in decision making, and 5) lack of domain experts. It emphasizes embracing failures, setting clear success criteria, allowing for random changes, empowering domain experts, and the product manager making the final call.
Más contenido relacionado
Similar a Hypothesis Incubator workshop (updated Dec'19)
Increasing Business Impact - Focusing on value deliveryNarek Alaverdyan
This document discusses shifting from an IT to a product mindset. It emphasizes focusing on customers and delivering value over cost and schedule. This involves adopting a profit center mentality and continuously improving products. DevOps is presented as a culture of collaboration, not a role or department. It involves developers understanding infrastructure and operations understanding code. Validated learning is discussed as focusing on minimum viable products, testing and learning through experiments and A/B testing to reduce waste and improve conversions. The goal is a team that loves finding better ways to delight customers and increase market share through cultural evolution.
Fix-Price Projects And Agile – PyCon SettePeter Bittner
You are a digital agency struggling with your Django projects. You’re over budget and you’ve run out of time, that’s the norm not the exception. And of course you promise to deliver all features on time for a fixed budget, don’t you? – And nobody told you this is a problem?
See the original presentation at http://slides.com/bittner/pycon7-fix-price-projects-and-agile
The document summarizes Gene Kim's presentation on breaking the chronic conflict between operations and development teams through a DevOps transformation. It outlines the downward spiral caused by the conflict, including fragile applications, long fix times, and frustrated customers. It then presents the philosophies of DevOps, including systems thinking to increase flow, amplifying feedback loops, and creating a culture of experimentation. Finally, it provides prescriptive phases for implementing DevOps, such as extending agile processes and creating environments, improving release processes, and prioritizing continuous improvement.
This document discusses various iterative software development models, including the spiral model, win-win spiral model, and cleanroom methodology. The spiral model is risk-driven and involves iterating through phases of planning, risk assessment, engineering, and evaluation. The win-win spiral model seeks to reconcile stakeholder objectives through negotiation. Cleanroom methodology emphasizes technical reviews, incremental development, and testing to reduce defects. Alternative models like hacking are also discussed for low-risk or disposable projects. Overall, the iterative models attempt to address limitations of the traditional waterfall model by incorporating feedback loops, prototyping, and incremental delivery.
This document discusses various aspects of managing software development projects, including:
- Developing a software development plan that defines the project scope, requirements, schedule and budget.
- Estimating project size, effort and costs using metrics from past projects and estimation models like COCOMO.
- Identifying and planning for risks that could impact the project.
- Choosing an appropriate development environment and tools.
- Defining deliverables for the customer and development process.
This document discusses user experience (UX), agile product management, and delivering software that meets user needs. It advocates for an iterative development process that incorporates UX research and testing. Product managers are advised to work closely with UX designers to validate assumptions through usability testing, measure outcomes, and prioritize addressing UX issues. An agile, lean approach that rapidly builds and learns from user feedback is presented as the best way to deliver innovative products that customers want and provide a competitive advantage.
The document discusses how to create fast software development cycles without breaking systems by adopting a DevOps approach using systems thinking, amplifying feedback loops, and fostering a culture of experimentation and learning to break down silos between development and operations teams and continuously improve processes. It also outlines some initial steps like forming a DevOps leadership team to help coordinate the transformation.
Project management in the age of accelerating change - IT/Tech specificLuca Minudel
This document provides an overview of agile project management practices for traditional project managers. It discusses how the context for management has changed in an age of accelerating change, rendering traditional management tools and mindsets less effective. Agile principles emphasize problem-solution co-evolution, solution co-creation, and simplicity. Common agile practices like iterations in sprints and emphasis on working software aim to increase learning and reduce the cost of change. The roles of product owner, scrum master, and self-organizing teams are described. Information radiators like burn-up charts and team boards promote transparency.
What's Agile ? Introduction to Agile methodsBruno Sbille
The document provides an introduction to Agile methods. It discusses that many IT projects do not succeed due to being over budget and schedule. Agile aims to deliver working software frequently through iterative development and valuing individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan. The document then covers Scrum and user stories which are part of the Agile methodology.
This document discusses alternatives to traditional software estimation approaches, such as the #NoEstimates concept. It outlines ideas from thinkers like Thomas Edison and Lean principles as the basis for considering "crazy ideas" in software development. The #NoEstimates approach focuses on prioritizing work, slicing stories finely, measuring throughput and lead times rather than velocity, and delivering value continuously with trust and transparency.
This document provides an overview and agenda for a webinar on continuous delivery in the enterprise. The webinar will define continuous delivery and differentiate it from continuous integration, Agile, quality and DevOps practices. It will explore the continuous delivery pipeline and key aspects like continuous development, integration and the ability to continuously release software. Attendees will learn about their role in continuous delivery and why it is important. The webinar will also discuss tools, products and solutions for continuous delivery and include case studies. It aims to explain how organizations can adopt continuous delivery practices.
Maximizing the impact of UX in an agile environment: Mixing agile and lean UXBrilliant Experience
When companies adopt an agile development environment, UX teams often feel like they just lost their seat at the table. It’s never easy to change, but by adapting your UX practices to accommodate agile, you can have the impact on design you always wanted.
Maximizing the impact of UX in an agile environment: Mixing agile and Lean UXJohn Whalen
When companies adopt an agile development environment, UX teams often feel like they just lost their seat at the table. It’s never easy to change, but by adapting your UX practices to accommodate agile, you can have the impact on design you always wanted.
PR-272: Accelerating Large-Scale Inference with Anisotropic Vector QuantizationSunghoon Joo
PR-272: Accelerating Large-Scale Inference with Anisotropic Vector Quantization
[Guo et al., ICML 2020]
Paper link: https://arxiv.org/abs/1908.10396
Video presentation link: https://youtu.be/cU46yR-A0cs
reviewed by Sunghoon Joo
Data science is not Software Development and how Experiment Management can ma...Jakub Czakon
Working on data science projects that are run as if they were software development can sometimes feel like trying to fit a square peg in a round hole. In this talk, I will explain why that happens and what people do to try and fix it. Lately, in the context of machine learning, the concept of experiment management, which treats ml experiments as first-class citizens, has been gaining a lot of traction. I will discuss what it is, what are the benefits of using it, and how you can apply it in your work to make run your projects more efficiently.
DevOpsDays Baltimore 2017.
Product owners are under pressure from Marketing and Leadership to focus on features, while operability (availability, performance, monitoring, etc) are an afterthought to be bolted on later. Deployments fail, customers complain, and work isn't fun. How can DevOps reach out to Product?
People from a "Product background" often have zero technical experience, but find themselves needing to dictate the deliverables. Product owners are under great pressure from Marketing and Leadership to focus on "features" from a customer perspective; the so-called "non-functional requirements" often fall by the wayside. Operability - monitorabilty, recoverability, availability, performance, among other aspects - is difficult to bake into an application that was developed without such consideration.
This talk will present practical approaches to bridge-building between Ops and Product. Focusing especially on cross-functional Agile teams with leadership with little or no Ops background, we will explore whether "planning the work will result in the planned work being the work that is done." When working with a mixed team, doing development, deployment, incident response, and everything in support of that, such plans go off the rails. Methods of championing Ops needs while avoiding "the sky is falling" perceptions will be presented. What kinds of unplanned work exist? Are there steps we can take to convert unplanned work into planned work? How does work flow through the team? How does unplanned work disrupt the flow?
Product owners are under pressure from Marketing and Leadership to focus on features, while operability (availability, performance, monitoring, etc) are an afterthought to be bolted on later. Deployments fail, customers complain, and work isn't fun. How can DevOps reach out to Product?
People from a "Product background" often have zero technical experience, but find themselves needing to dictate the deliverables. Product owners are under great pressure from Marketing and Leadership to focus on "features" from a customer perspective; the so-called "non-functional requirements" often fall by the wayside. Operability - monitorabilty, recoverability, availability, performance, among other aspects - is difficult to bake into an application that was developed without such consideration.
This talk will present practical approaches to bridge-building between Ops and Product. Focusing especially on cross-functional Agile teams with leadership with little or no Ops background, we will explore whether "planning the work will result in the planned work being the work that is done." When working with a mixed team, doing development, deployment, incident response, and everything in support of that, such plans go off the rails. Methods of championing Ops needs while avoiding "the sky is falling" perceptions will be presented. What kinds of unplanned work exist? Are there steps we can take to convert unplanned work into planned work? How does work flow through the team? How does unplanned work disrupt the flow?
This document proposes several models for measuring individual productivity of knowledge workers or technologists. It discusses challenges in measuring productivity in knowledge-based roles and industries. It then outlines 5 potential simple solutions that use tools, peer reviews, surveys and third-party evaluations. The models aim to provide objective and comprehensive productivity measurement while accounting for complexity factors like project size and technical difficulty. The document concludes by stating that determining the best approach requires further discussion.
Similar a Hypothesis Incubator workshop (updated Dec'19) (20)
Backlog City workshop - task description (updated Dec'19)Bartek Gatz
- The document provides background information on Backlog City, which is divided into 4 districts with varying incomes, infrastructure, crime rates, and access to transportation.
- District A has the largest population of 1.5 million with the lowest median income of $300. It has old infrastructure and high crime.
- District B has a population of 0.3 million with a median income of $800. It contains the mayor's office and tourist attractions but also pickpockets.
- District C has 0.7 million inhabitants with a median income of $1000. It is an upper middle-class area with light industry and shopping centers.
- District D is the wealthiest with a median income of $5000
Product Management - pitfalls of Data Driven DevelopmentBartek Gatz
The document discusses various pitfalls of data-driven development from a product management perspective, focusing on agile software development. It outlines five main pitfalls: 1) having the wrong mindset for failure when conducting experiments, 2) difficulties perceiving progress, 3) overreliance on collecting more data when facing deadlocks, 4) unexpected downsides of democracy in decision making, and 5) lack of domain experts. It emphasizes embracing failures, setting clear success criteria, allowing for random changes, empowering domain experts, and the product manager making the final call.
How to be a good IT Product Manager - part 2 - talking to DevelopersBartek Gatz
This is a second part of the presentation about good practices in IT Product Management. This time I focus on collaboration with The Lab.
The presentation was delivered during Tech3Camp conference in October 2014.
How to be a good IT Product Manager - part 1 - talking to CustomersBartek Gatz
This is a presentation where I talk about good Product management practices with focus on communication with Customers.
The presentation was delivered during NetVision conference in April 2014.
Mature product backlog and how to deal with it - workshop - Backlog cityBartek Gatz
You have been elected mayor of Backlog City, which is located on the shores of Safe Sea and surrounded by the Kanban River delta and woods. The city has 4 districts with varying populations, salary medians, infrastructure, crime rates, and access to the river and sea. Your primary goal is to get re-elected by making the citizens happy through improvements to their districts.
This presentation, "The Morale Killers: 9 Ways Managers Unintentionally Demotivate Employees (and How to Fix It)," is a deep dive into the critical factors that can negatively impact employee morale and engagement. Based on extensive research and real-world experiences, this presentation reveals the nine most common mistakes managers make, often without even realizing it.
The presentation begins by highlighting the alarming statistic that 70% of employees report feeling disengaged at work, underscoring the urgency of addressing this issue. It then delves into each of the nine "morale killers," providing clear explanations and illustrative examples.
1. Ignoring Achievements: The presentation emphasizes the importance of recognizing and rewarding employees' efforts, tailored to their individual preferences.
2. Bad Hiring/Promotions & Broken Promises: It reveals the detrimental effects of poor hiring and promotion decisions, along with the erosion of trust that results from broken promises.
3. Treating Everyone Equally & Tolerating Poor Performance: This section stresses the need for fair treatment while acknowledging that employees have different needs. It also emphasizes the importance of addressing poor performance promptly.
4. Stifling Growth & Lack of Interest: The presentation highlights the importance of providing opportunities for learning and growth, as well as showing genuine care for employees' well-being.
5. Unclear Communication & Micromanaging: It exposes the frustration and resentment caused by vague expectations and excessive control, advocating for clear communication and employee empowerment.
The presentation then shifts its focus to the power of recognition and empowerment, highlighting how a culture of appreciation can fuel engagement and motivation. It provides actionable takeaways for managers, emphasizing the need to stop demotivating behaviors and start actively fostering a positive workplace culture.
The presentation concludes with a strong call to action, encouraging viewers to explore the accompanying blog post, "9 Proven Ways to Crush Employee Morale (and How to Avoid Them)," for a more in-depth analysis and practical solutions.
m249-saw PMI To familiarize the soldier with the M249 Squad Automatic Weapon ...LinghuaKong2
M249 Saw marksman PMIThe Squad Automatic Weapon (SAW), or 5.56mm M249 is an individually portable, gas operated, magazine or disintegrating metallic link-belt fed, light machine gun with fixed headspace and quick change barrel feature. The M249 engages point targets out to 800 meters, firing the improved NATO standard 5.56mm cartridge.The SAW forms the basis of firepower for the fire team. The gunner has the option of using 30-round M16 magazines or linked ammunition from pre-loaded 200-round plastic magazines. The gunner's basic load is 600 rounds of linked ammunition.The SAW was developed through an initially Army-led research and development effort and eventually a Joint NDO program in the late 1970s/early 1980s to restore sustained and accurate automatic weapons fire to the fire team and squad. When actually fielded in the mid-1980s, the SAW was issued as a one-for-one replacement for the designated "automatic rifle" (M16A1) in the Fire Team. In this regard, the SAW filled the void created by the retirement of the Browning Automatic Rifle (BAR) during the 1950s because interim automatic weapons (e.g. M-14E2/M16A1) had failed as viable "base of fire" weapons.
Early in the SAW's fielding, the Army identified the need for a Product Improvement Program (PIP) to enhance the weapon. This effort resulted in a "PIP kit" which modifies the barrel, handguard, stock, pistol grip, buffer, and sights.
The M249 machine gun is an ideal complementary weapon system for the infantry squad platoon. It is light enough to be carried and operated by one man, and can be fired from the hip in an assault, even when loaded with a 200-round ammunition box. The barrel change facility ensures that it can continue to fire for long periods. The US Army has conducted strenuous trials on the M249 MG, showing that this weapon has a reliability factor that is well above that of most other small arms weapon systems. Today, the US Army and Marine Corps utilize the license-produced M249 SAW.
Neal Elbaum Shares Top 5 Trends Shaping the Logistics Industry in 2024Neal Elbaum
In the ever-evolving world of logistics, staying ahead of the curve is crucial. Industry expert Neal Elbaum highlights the top five trends shaping the logistics industry in 2024, offering valuable insights into the future of supply chain management.
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd tes...ssuserf63bd7
Small Business Management An Entrepreneur’s Guidebook 8th edition by Byrd test bank.docx
https://qidiantiku.com/test-bank-for-small-business-management-an-entrepreneurs-guidebook-8th-edition-by-mary-jane-byrd.shtml
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.
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.
From Concept to reality : Implementing Lean Managements DMAIC Methodology for...Rokibul Hasan
The Ready-Made Garments (RMG) industry in Bangladesh is a cornerstone of the economy, but increasing costs and stagnant productivity pose significant challenges to profitability. This study explores the implementation of Lean Management in the Sampling Section of RMG factories to enhance productivity. Drawing from a comprehensive literature review, theoretical framework, and action research methodology, the study identifies key areas for improvement and proposes solutions.
Through the DMAIC approach (Define, Measure, Analyze, Improve, Control), the research identifies low productivity as the primary problem in the Sampling Section, with a PPH (Productivity per head) of only 4.0. Using Lean Management techniques such as 5S, Standardized work, PDCA/Kaizen, KANBAN, and Quick Changeover, the study addresses issues such as pre and post Quick Changeover (QCO) time, improper line balancing, and sudden plan changes.
The research employs regression analysis to test hypotheses, revealing a significant correlation between reducing QCO time and increasing productivity. With a regression equation of Y = -0.000501X + 6.72 and an R-squared value of 0.98, the study demonstrates a strong relationship between the independent variables (QCO downtime and improper line balancing downtime) and the dependent variable (productivity per head).
The findings suggest that by implementing Lean Management practices and addressing key productivity inhibitors, RMG factories can achieve substantial improvements in efficiency and profitability. The study provides valuable insights for practitioners, policymakers, and researchers seeking to enhance productivity in the RMG industry and similar manufacturing sectors.
A comprehensive-study-of-biparjoy-cyclone-disaster-management-in-gujarat-a-ca...Samirsinh Parmar
Disaster management;
Cyclone Disaster Management;;
Biparjoy Cyclone Case Study;
Meteorological Observations;
Best practices in Disaster Management;
Synchronization of Agencies;
GSDMA in Cyclone disaster Management;
History of Cyclone in Arabian ocean;
Intensity of Cyclone in Gujarat;
Cyclone preparedness;
Miscellaneous observations - Biparjoy cyclone;
Role of social Media in Disaster Management;
Unique features of Biparjoy cyclone;
Role of IMD in Biparjoy Prediction;
Lessons Learned; Disaster Preparedness; published paper;
Case study; for disaster management agencies; for guideline to manage cyclone disaster; cyclone management; cyclone risks; rescue and rehabilitation for cyclone; timely evacuation during cyclone; port closure; tourism closure etc.
Maximize Your Efficiency with This Comprehensive Project Management Platform ...SOFTTECHHUB
In today's work environment, staying organized and productive can be a daunting challenge. With multiple tasks, projects, and tools to juggle, it's easy to feel overwhelmed and lose focus. Fortunately, liftOS offers a comprehensive solution to streamline your workflow and boost your productivity. This innovative platform brings together all your essential tools, files, and tasks into a single, centralized workspace, allowing you to work smarter and more efficiently.
9. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
10. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
12. TYPES OF PROJECTS
• PoC - Proof of Concept
• purpose: to verify some technical assumptions,
lowers risk of failure, can we do it?
• covers just a small part of system (not the entire
system)
• model of a one product’s aspect, bugs
13. • Prototype
• purpose: to test product design & usability &
functionality. To reduce number of mistakes by
discovering errors in system, how to do it?
• working, but not perfect model of several aspects
of product, bugs
TYPES OF PROJECTS
14. • MVP - Minimum Viable Product
• purpose: to get minimum version of product to the
market
• just core functionality, no bugs
TYPES OF PROJECTS
15. • MAP - Minimum Awesome Product
• purpose: to create more reliable and more
attractive product for user and customer
• best product experience possible with the given
resources
TYPES OF PROJECTS
20. • Enterprise
• purpose: to give big business an ability to solve
enterprise problems
• complex application or environment of
applications
TYPES OF PROJECTS
21. TYPES OF PROJECTS
Enterprise Systems examples
• Payment Processing
• CRM (Customer Relationship Management)
• ERP (Enterprise Resource Planning)
• BI (Business Intelligence)
• Data Engineering
23. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
30. • existing “backlog”
• mix of new ideas and known problems
• continued work on earlier “version”
• but now it is your problem
BACKLOG CITY
31. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
36. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
40. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
53. sprint in progress
backlog: max two sprints of
prioritized issues in the backlog
"OPERATIONAL" PRODUCT BACKLOG
54. nothing gets to the backlog, unless:
• it is a technical task
• it is a bug
• it has hatched from Incubator
"OPERATIONAL" PRODUCT BACKLOG
55. separate project in JIRA
issue type = IDEA
workflow = INCUBATION
LAID
LAID
LAID
INSPECTED
INSPECTED
HEATED UP
PRIORITISED
PRIORITISED
PRIORITISED
PRIORITISED
INFERTILE
GONE BAD
GONE BAD
GONE BAD
GONE BAD
HATCHED
HATCHED
HATCHED
COMPLETED
only HATCHED ideas go to
"operational" backlog
IDEA INCUBATOR
56. PROBLEM DESCRIPTION (TEXT)
KPI IMPACT HYPOTHESIS (TEXT)
SOLUTION HYPOTHESIS (TEXT)
SUCCESS CRITERIA (TEXT)
LAY TIME STAMP (DATE)
IDEA
PRIORITY (2x VALUE)
IMPACT COST
57. what problem we are trying to solve:
in-product problem
user problem
IDEA
PROBLEM DESCRIPTION (TEXT)
58. what primary metric we think
this problem relates to:
KPIs only, so this must be focused
strategic alignment
IDEA
KPI IMPACT HYPOTHESIS (TEXT)
59. super short high level description
of the potential solution
this is a large user story (epic)
no technical discussions allowed here
IDEA
SOLUTION HYPOTHESIS (TEXT)
60. how are we going to measure
whether the solution worked
measurement technique applied
description of experiments if required
quantifiable thresholds for selected metrics
IDEA
SUCCESS CRITERIA (TEXT)
61. fields required for prioritization exercise
IMPACT defines the strength
of movement of KPI needle
COST of delivery is a guesstimation
IDEA
PRIORITY (2x VALUE)
IMPACT COST
62. IMPACT defines the strength of movement of KPI needle
URGENCY defines the consequences if not addressed soon
COST of delivery combines guesstimation of all costs:
development marketing support technology
RISK specifies the risk associated with a given hypothesis
fields required for prioritization exercise
IDEA
PRIORITY (4x VALUE)
IMPACT COSTURGENCY RISK
70. impossible to prioritize just yet:
•more data required to validate
HEATED UP
•not right TTM
•unclear impact on KPI
INCUBATION WORKFLOW
•this is where the Design Sprint happens
72. not worth the investment:
•no strategic alignment
•science fiction
INFERTILE
INCUBATION WORKFLOW
73. idea potentially worth it, but:
•fell a victim of prioritization for too long
•most likely outdated
GONE BAD
INCUBATION WORKFLOW
74. idea of high overall priority:
•at this stage it goes to "operational" product backlog
•transforms into an epic / user story
HATCHED
INCUBATION WORKFLOW
75. idea implementation completed:
•developed and released
•validated to have met success criteria
COMPLETED
•source of truth for:
release notes
marketing materials
experiment validation
INCUBATION WORKFLOW
84. clean primary product backlog
controlled inflow of requirements
controlled rollout of ideas / improvements / simplifications
no changes without a good reason - working on things that matter
measurements for validation
deprecation of bad ideas before they hurt us
TO SUM UP…..
85. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
89. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
95. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
98. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
106. MoSCoW prioritization technique
It’s important to keep all stories in the backlog,
including the ones with the lowest priority as well =
Won’t haves
113. project types
introduction
exercise #1
exercise #2
break
some theory
exercise #3
exercise #4
break
some more theory
exercise #5
- 15 min
- 10 min
- 15 min
- 15 min
- 10 min
- 20 min
- 15 min
- 10 min
- 10 min
- 15 min
- 25 min
115. •select 3 top epics from your list
•break them into 3-7 user stories
•estimate story points for each
•define MOSCOW factor for each story
•sort your backlog
•run 3 sprints
TIME: 25 MINUTES
BACKLOG CITY
EXERCISE #5
121. BACKLOG CITY
EXERCISE #5
PART 5 -
define MOSCOW factor for each
story
MSF
M - Must have = highest = 8
S - Should have = high = 5
C - Could have = low = 2
W - Won’t have = lowest = 0