Small Business Innovation doesn't need to be rocket science. Start with creative thinking and apply the actions in your business to see the results. Presented by Rod Hattch - Managing Director Wisdom.
Combatting unconscious bias with virtual reality (VR). Learn how Red Hat University joined forces with Lucid Dream to develop an immersive learning environment and bring the subtleties of unconscious bias to life. See how VR helps learners not only recognize unconscious bias but act in the moment to address it. Live demos will be conducted at the conclusion of the session.
The Innovation Engine, Andrew Breen, American ExpressLean Startup Co.
Large, established organizations fear disruption from big tech and startups. In trying to thwart that they have resorted to several approaches to innovation to scale such as labs, acquisitions and spin-outs. Most have not succeed often due to the impediments that corporate culture and organizational design bring. The Innovation Engine is a framework developed by Andrew Breen which addresses these issues. Andrew has built this not only from his experience building eight tech startups but also in his current role building a Lean startup at American Express.
Design System as a Product - Maria Elena Duenias, Esther Butcher
Design systems are a great example where web development and design meet. You can find innumerable resources on the internet, books and conferences on how to build them, and how they are exactly what your organization needs. But, building one requires a lot more than following a recipe. In this talk we are going to discuss how to build a design system as an internal product, and how it evolves to become what the users need.
The document discusses management without authority and provides tips for leading effectively without a formal leadership title. It suggests building relationships, earning trust through domain expertise, rolling up your sleeves to help, communicating frequently, and focusing on incremental improvements rather than trying to change too many things at once. The document also lists sources of unofficial power for managers like networks, communication skills, and helping remove obstacles.
The document discusses thredUP's engineering culture and practices. It emphasizes building a culture of learning, speed, and scaling quickly. Key aspects of thredUP's engineering culture include favoring people over processes, generalist full-stack engineers over specialists, overcommunication in small asynchronous teams, dynamic teams without hierarchy, and prioritizing tempo over quality. The goal is for full-cycle product development engineers to work in small teams with a mindset of speed.
This document provides an overview of techniques for product management tasks like estimation, prioritization, and backlog management. It discusses 10 estimation techniques like planning poker, affinity mapping, and three-point estimation. It also covers 10 prioritization techniques including MoSCoW, Kano model, and value vs cost. Finally, it outlines different backlog item types and approaches to maintain an effective product backlog through refinement and funneling ideas.
Build your Product Backlog. Wish lists and task listsShiftup
Discover in this deck various types of product backlogs, various product backlog visualizations and discover a backlog maintenance game.
Want to attend our next webinar? Become a Shiftup Explorer: https://shiftup.work/product/explorer-agility-innovation-qualification-program/
Small Business Innovation doesn't need to be rocket science. Start with creative thinking and apply the actions in your business to see the results. Presented by Rod Hattch - Managing Director Wisdom.
Combatting unconscious bias with virtual reality (VR). Learn how Red Hat University joined forces with Lucid Dream to develop an immersive learning environment and bring the subtleties of unconscious bias to life. See how VR helps learners not only recognize unconscious bias but act in the moment to address it. Live demos will be conducted at the conclusion of the session.
The Innovation Engine, Andrew Breen, American ExpressLean Startup Co.
Large, established organizations fear disruption from big tech and startups. In trying to thwart that they have resorted to several approaches to innovation to scale such as labs, acquisitions and spin-outs. Most have not succeed often due to the impediments that corporate culture and organizational design bring. The Innovation Engine is a framework developed by Andrew Breen which addresses these issues. Andrew has built this not only from his experience building eight tech startups but also in his current role building a Lean startup at American Express.
Design System as a Product - Maria Elena Duenias, Esther Butcher
Design systems are a great example where web development and design meet. You can find innumerable resources on the internet, books and conferences on how to build them, and how they are exactly what your organization needs. But, building one requires a lot more than following a recipe. In this talk we are going to discuss how to build a design system as an internal product, and how it evolves to become what the users need.
The document discusses management without authority and provides tips for leading effectively without a formal leadership title. It suggests building relationships, earning trust through domain expertise, rolling up your sleeves to help, communicating frequently, and focusing on incremental improvements rather than trying to change too many things at once. The document also lists sources of unofficial power for managers like networks, communication skills, and helping remove obstacles.
The document discusses thredUP's engineering culture and practices. It emphasizes building a culture of learning, speed, and scaling quickly. Key aspects of thredUP's engineering culture include favoring people over processes, generalist full-stack engineers over specialists, overcommunication in small asynchronous teams, dynamic teams without hierarchy, and prioritizing tempo over quality. The goal is for full-cycle product development engineers to work in small teams with a mindset of speed.
This document provides an overview of techniques for product management tasks like estimation, prioritization, and backlog management. It discusses 10 estimation techniques like planning poker, affinity mapping, and three-point estimation. It also covers 10 prioritization techniques including MoSCoW, Kano model, and value vs cost. Finally, it outlines different backlog item types and approaches to maintain an effective product backlog through refinement and funneling ideas.
Build your Product Backlog. Wish lists and task listsShiftup
Discover in this deck various types of product backlogs, various product backlog visualizations and discover a backlog maintenance game.
Want to attend our next webinar? Become a Shiftup Explorer: https://shiftup.work/product/explorer-agility-innovation-qualification-program/
As an analyst, the start of a problem is a wonderful place. All your time is focussed on discovering what drives the business you work in, or what causes it the most pain. Then you build something that helps to fix the problem. That’s when your life becomes less exciting.
Every problem you solve comes with a reduction in your capacity for the new and exciting, and your time is filled with monitoring, reporting and tweaking.
We want to talk to you about how you can build a team, tools and a culture to allow your analysts the opportunity to focus on the things they do best and enjoy the most – resulting in them being able to fix more problems (and spend some time trying to work out what AI actually is).
The Challenge of Sustaining Disruptive Innovation When You Meet SuccessRobert Fan
This document discusses the challenges of sustaining disruptive innovation when a company meets success. It shows how a startup called Sharethrough grew rapidly but then found it harder to innovate and disrupt as resources were allocated to supporting existing success over disruptive innovations. The document outlines the steps Sharethrough took to balance success and disruption, including creating the right isolated environment for innovation, setting goals and boundaries through customer development, and using milestones and progress checks separated from existing workflows. The author notes innovation is hard and it's easy to fall back into old habits, so they iterated differently and had transition plans ready when projects "finished".
How can you adopt innovation at your company ? Why should you bother ? How can you do it ? What matters and why ?
Here I share my learning from starting and running a startup and building data science products in thomson reuters and other organizations
Catalign Innovation Consulting is a firm that helps clients foster a culture of innovation. They offer programs to help build innovation capabilities, including developing innovation pipelines and leadership. Their approach includes design thinking, tools like idea management processes, and benchmarking innovation metrics. Case studies demonstrate how they have helped companies increase ideas, participation, prototypes and influenced customer roadmaps.
Coming Together: integrating industrial design and interaction designJoannes Vandermeulen
The document discusses integrating user-centered design (UCD) into industrial design and interaction design practices by drawing inspiration from lean manufacturing and agile software development approaches which emphasize eliminating waste, empowering teams, continuous improvement, and deciding design elements as late as possible to incorporate more user feedback. It proposes several strategies to enhance collaboration between disciplines like offering co-located design studios, delaying design decisions, and using high-impact but lightweight representations to incorporate user input earlier in the design process. Case studies of products that employed UCD practices showed successes in meeting user needs within tight development timelines.
The document outlines an 8-step process for effective problem solving: 1) Identify the problem, 2) Understand the current situation, 3) Identify the root causes, 4) Plan improvements, 5) Execute the improvements, 6) Confirm the results, 7) Standardize the improvements, and 8) Plan for the future. Key aspects of the process include using tools like fishbone diagrams, Pareto charts, and goal setting to thoroughly analyze problems and select effective solutions. The process advocates for containing root causes, prioritizing high impact improvements with low effort, monitoring solutions, and documenting standardized practices to maintain results over time.
Tathagat Varma discusses challenges with traditional new product development processes and proposes more agile alternatives inspired by design thinking principles. He advocates getting customer feedback early through minimum viable products and rapid experimentation. Continuous learning is emphasized over rigid stage-gate models by embracing failure and making mid-flight adjustments. Getting outside the building to directly observe customers is presented as key to developing successful innovations in a changing world.
Discover in this deck why experience beats product, learn about a motivational framework and get a better view on iterations and increments.
Want to attend our next webinar? Become a Shiftup Explorer: https://shiftup.work/product/explorer-agility-innovation-qualification-program/
Offshoring software development in Switzerland: You can do itAlexandre Masselot
If offshoring is often driven by short term considerations and economical drivers, there are better reasons to externalize software development. And why not coming to Switzerland?. Over the past two years, we have reversed the offshoring flow, pursuing ambitious IT projects for US companies, from the Swiss mountains.
The Agile Tour conference in Lausanne is the occasion of the lessons learned during adventures and to reflect on how we can improve the development of inhouse digital products.
The document discusses building new ideas and businesses through fast learning cycles. It recommends establishing weekly innovation sprints over 10 weeks to generate new product ideas, with goals of 80 ideas total, killing 60, merging 10, and progressing 10. Each Monday would involve presenting key learnings and asking for help. Brainstorming sessions on Fridays would involve new external people. Death threats to ideas would be identified and systems put in place to work on threats and decide what to kill through daily stand-up meetings and rotating leadership. Repeating this process removes risks and allows businesses to scale once the foundations are solidified.
This document discusses agile software development principles and a regional Scrum gathering. It outlines goals of delivering value incrementally through early delivery, limiting batch sizes, building quality in, and continuous feedback and replanning. Diagrams illustrate Scrum processes and emphasize collaboration, ownership, and creating a professional yet cheerful open environment. The document concludes by providing contact information for the curator of the presentation.
This document outlines 10 steps for successfully setting up an agency innovation lab: 1) Determine a clear vision and mission, 2) Plan long-term goals and strategies over 3-5 years, 3) Define metrics for measuring success, 4) Gain executive buy-in and support, 5) Start small with early achievable projects, 6) Operate with an entrepreneurial and startup mindset, 7) Allocate an appropriate budget, 8) Empower lab leadership with autonomy, 9) Teach others the innovation process, 10) Accept that most experiments will fail and focus on learning.
Nine Methods and Tools 4 of them well known and effective. Five more...extended and innovated ...
Innovation is NOT a rapid sure-fire process though it may appear to be so.
The process and methods to be used are explained. Details will be given when we start working on an Innovation Project....START
How can you innovate in large organisations? How can you handle the fuzzy front end of innovation without resorting to (grit teeth) project management? That's all in our latest slide deck. All illustrations from Thomas Hartland.
CTO in a Small Startup Bryan Helmig - ZapierWebrazzi
The document discusses the role of a CTO in a small startup. It begins by acknowledging that the definition of a CTO is unclear. It then provides some context, noting the CTO would lead a tech organization of up to 12 engineers during the initial growth stage of a business where software is core. The document presents an "upgrade tree" showing how a founder's role may evolve from solo hacker to taking on more managerial responsibilities as CTO as the team grows larger. It suggests CTOs at small startups still do significant coding while taking on leadership duties and deals with breaking points as the role changes during growth.
Transformation. Continuous transformation, systems thinkingShiftup
The document discusses change management and transformation. It provides an overview of the Innovation Vortex model and how it can be applied to change management. It discusses different models for leadership in change, including the differences between change leadership and change management. It then walks through each step of the Innovation Vortex model - from empathizing and defining problems to ideating solutions, building prototypes, testing ideas, and learning from the process. Key aspects of evaluating and improving change initiatives are also summarized.
Thinking Inside The Box - Systematic Inventive ThinkingNguyen Trung Tuyen
The document provides an introduction to systematic inventive thinking and innovation tools. It discusses how innovation has transformed from an optional activity in 1995 to a necessity in 2014. The document then covers various innovation tools including systematic inventive thinking, breaking functional fixedness, subtraction, multiplication, and function follows form. It provides examples of how these tools have been applied by companies to develop new products and services that better meet customer needs.
The document discusses transferring a team to a new distributed setup within 3 months. It describes holding initial meetings in Xi'an, Sydney, and Melbourne to bring the new team together and establish practices. It notes the challenges of building an effective team remotely but emphasizes focusing on delivering software through pairing, storytelling and other techniques.
Despite Lithuania producing a significant amount of energy, citizens still face rapidly increasing prices due to a stubborn monopoly and poor government regulation. Lithuanian energy costs per kWh are among the highest in Europe despite a lower GDP per capita than comparable countries. Several reforms have been proposed to introduce competition, such as splitting the largest energy producers into smaller companies, opening the Baltic energy market to foreign competitors, or setting maximum prices for energy transportation while allowing competition in production. However, the government is reluctant to take steps that would reduce its stake in major energy companies.
As an analyst, the start of a problem is a wonderful place. All your time is focussed on discovering what drives the business you work in, or what causes it the most pain. Then you build something that helps to fix the problem. That’s when your life becomes less exciting.
Every problem you solve comes with a reduction in your capacity for the new and exciting, and your time is filled with monitoring, reporting and tweaking.
We want to talk to you about how you can build a team, tools and a culture to allow your analysts the opportunity to focus on the things they do best and enjoy the most – resulting in them being able to fix more problems (and spend some time trying to work out what AI actually is).
The Challenge of Sustaining Disruptive Innovation When You Meet SuccessRobert Fan
This document discusses the challenges of sustaining disruptive innovation when a company meets success. It shows how a startup called Sharethrough grew rapidly but then found it harder to innovate and disrupt as resources were allocated to supporting existing success over disruptive innovations. The document outlines the steps Sharethrough took to balance success and disruption, including creating the right isolated environment for innovation, setting goals and boundaries through customer development, and using milestones and progress checks separated from existing workflows. The author notes innovation is hard and it's easy to fall back into old habits, so they iterated differently and had transition plans ready when projects "finished".
How can you adopt innovation at your company ? Why should you bother ? How can you do it ? What matters and why ?
Here I share my learning from starting and running a startup and building data science products in thomson reuters and other organizations
Catalign Innovation Consulting is a firm that helps clients foster a culture of innovation. They offer programs to help build innovation capabilities, including developing innovation pipelines and leadership. Their approach includes design thinking, tools like idea management processes, and benchmarking innovation metrics. Case studies demonstrate how they have helped companies increase ideas, participation, prototypes and influenced customer roadmaps.
Coming Together: integrating industrial design and interaction designJoannes Vandermeulen
The document discusses integrating user-centered design (UCD) into industrial design and interaction design practices by drawing inspiration from lean manufacturing and agile software development approaches which emphasize eliminating waste, empowering teams, continuous improvement, and deciding design elements as late as possible to incorporate more user feedback. It proposes several strategies to enhance collaboration between disciplines like offering co-located design studios, delaying design decisions, and using high-impact but lightweight representations to incorporate user input earlier in the design process. Case studies of products that employed UCD practices showed successes in meeting user needs within tight development timelines.
The document outlines an 8-step process for effective problem solving: 1) Identify the problem, 2) Understand the current situation, 3) Identify the root causes, 4) Plan improvements, 5) Execute the improvements, 6) Confirm the results, 7) Standardize the improvements, and 8) Plan for the future. Key aspects of the process include using tools like fishbone diagrams, Pareto charts, and goal setting to thoroughly analyze problems and select effective solutions. The process advocates for containing root causes, prioritizing high impact improvements with low effort, monitoring solutions, and documenting standardized practices to maintain results over time.
Tathagat Varma discusses challenges with traditional new product development processes and proposes more agile alternatives inspired by design thinking principles. He advocates getting customer feedback early through minimum viable products and rapid experimentation. Continuous learning is emphasized over rigid stage-gate models by embracing failure and making mid-flight adjustments. Getting outside the building to directly observe customers is presented as key to developing successful innovations in a changing world.
Discover in this deck why experience beats product, learn about a motivational framework and get a better view on iterations and increments.
Want to attend our next webinar? Become a Shiftup Explorer: https://shiftup.work/product/explorer-agility-innovation-qualification-program/
Offshoring software development in Switzerland: You can do itAlexandre Masselot
If offshoring is often driven by short term considerations and economical drivers, there are better reasons to externalize software development. And why not coming to Switzerland?. Over the past two years, we have reversed the offshoring flow, pursuing ambitious IT projects for US companies, from the Swiss mountains.
The Agile Tour conference in Lausanne is the occasion of the lessons learned during adventures and to reflect on how we can improve the development of inhouse digital products.
The document discusses building new ideas and businesses through fast learning cycles. It recommends establishing weekly innovation sprints over 10 weeks to generate new product ideas, with goals of 80 ideas total, killing 60, merging 10, and progressing 10. Each Monday would involve presenting key learnings and asking for help. Brainstorming sessions on Fridays would involve new external people. Death threats to ideas would be identified and systems put in place to work on threats and decide what to kill through daily stand-up meetings and rotating leadership. Repeating this process removes risks and allows businesses to scale once the foundations are solidified.
This document discusses agile software development principles and a regional Scrum gathering. It outlines goals of delivering value incrementally through early delivery, limiting batch sizes, building quality in, and continuous feedback and replanning. Diagrams illustrate Scrum processes and emphasize collaboration, ownership, and creating a professional yet cheerful open environment. The document concludes by providing contact information for the curator of the presentation.
This document outlines 10 steps for successfully setting up an agency innovation lab: 1) Determine a clear vision and mission, 2) Plan long-term goals and strategies over 3-5 years, 3) Define metrics for measuring success, 4) Gain executive buy-in and support, 5) Start small with early achievable projects, 6) Operate with an entrepreneurial and startup mindset, 7) Allocate an appropriate budget, 8) Empower lab leadership with autonomy, 9) Teach others the innovation process, 10) Accept that most experiments will fail and focus on learning.
Nine Methods and Tools 4 of them well known and effective. Five more...extended and innovated ...
Innovation is NOT a rapid sure-fire process though it may appear to be so.
The process and methods to be used are explained. Details will be given when we start working on an Innovation Project....START
How can you innovate in large organisations? How can you handle the fuzzy front end of innovation without resorting to (grit teeth) project management? That's all in our latest slide deck. All illustrations from Thomas Hartland.
CTO in a Small Startup Bryan Helmig - ZapierWebrazzi
The document discusses the role of a CTO in a small startup. It begins by acknowledging that the definition of a CTO is unclear. It then provides some context, noting the CTO would lead a tech organization of up to 12 engineers during the initial growth stage of a business where software is core. The document presents an "upgrade tree" showing how a founder's role may evolve from solo hacker to taking on more managerial responsibilities as CTO as the team grows larger. It suggests CTOs at small startups still do significant coding while taking on leadership duties and deals with breaking points as the role changes during growth.
Transformation. Continuous transformation, systems thinkingShiftup
The document discusses change management and transformation. It provides an overview of the Innovation Vortex model and how it can be applied to change management. It discusses different models for leadership in change, including the differences between change leadership and change management. It then walks through each step of the Innovation Vortex model - from empathizing and defining problems to ideating solutions, building prototypes, testing ideas, and learning from the process. Key aspects of evaluating and improving change initiatives are also summarized.
Thinking Inside The Box - Systematic Inventive ThinkingNguyen Trung Tuyen
The document provides an introduction to systematic inventive thinking and innovation tools. It discusses how innovation has transformed from an optional activity in 1995 to a necessity in 2014. The document then covers various innovation tools including systematic inventive thinking, breaking functional fixedness, subtraction, multiplication, and function follows form. It provides examples of how these tools have been applied by companies to develop new products and services that better meet customer needs.
The document discusses transferring a team to a new distributed setup within 3 months. It describes holding initial meetings in Xi'an, Sydney, and Melbourne to bring the new team together and establish practices. It notes the challenges of building an effective team remotely but emphasizes focusing on delivering software through pairing, storytelling and other techniques.
Despite Lithuania producing a significant amount of energy, citizens still face rapidly increasing prices due to a stubborn monopoly and poor government regulation. Lithuanian energy costs per kWh are among the highest in Europe despite a lower GDP per capita than comparable countries. Several reforms have been proposed to introduce competition, such as splitting the largest energy producers into smaller companies, opening the Baltic energy market to foreign competitors, or setting maximum prices for energy transportation while allowing competition in production. However, the government is reluctant to take steps that would reduce its stake in major energy companies.
The document discusses why most organizations are not learning or adapting enough to change. It argues that organizations implement top-down change programs that promote uniformity and control rather than learning. True change comes from trying new things, learning from others, and having independent teams with decision autonomy, visibility, and knowledge sharing. Organizations need to move away from a focus on execution and control toward openness, flexibility and collaboration if they want to gain the benefits of adaptability, innovation and learning.
The document discusses ramping up a distributed team across multiple locations in 3 weeks. It describes how a company had to ramp down an existing team, create a new distributed team across Melbourne, Sydney, and Xi'an, and transfer knowledge between the locations within 3 months. The process involved 6 weeks of preparation, 3 weeks to form the new distributed team, and 2 weeks of the team performing together. A plan-do-check-act approach was used during the forming process to address issues like interference levels between the locations. In the end, the presenters discuss whether ramping up the distributed team across 3 locations within the short timeframe was successful.
The document discusses how case management systems can help lawyers practice ethically and competently. It notes that a lack of using available case management tools has contributed to breaches of professional conduct rules. Case management systems help by tracking appointments and deadlines, facilitating timely client communication, maintaining accurate records, avoiding conflicts of interest, tracking time and expenses accurately, and ensuring client confidentiality and funds are properly handled. The document recommends finding a system that integrates key functions and works with a firm's existing workflows.
The Streams of Our Lives - Visualizing Listening Histories in ContextDominikus Baur
Slides to the talk I gave at the IEEE InfoVis conference on 29/10/10.
You can download LastHistory here:
http://www.frederikseiffert.de/lasthistory/
Here's the abstract of the paper:
The choices we take when listening to music are expressions of our personal taste and character. Storing and accessing our listening histories is trivial due to services like Last.fm, but learning from them and understanding them is not. Existing solutions operate at a very abstract level and only produce statistics. By applying techniques from information visualization to this problem, we were able to provide average people with a detailed and powerful tool for accessing their own musical past. LastHistory is an interactive visualization for displaying music listening histories, along with contextual information from personal photos and calendar entries. Its two main user tasks are (1) analysis, with an emphasis on temporal patterns and hypotheses related to musical genre and sequences, and (2) reminiscing, where listening histories and context represent part of one's past. In this design study paper we give an overview of the field of music listening histories and explain their unique characteristics as a type of personal data. We then describe the design rationale, data and view transformations of LastHistory and present the results from both a lab- and a large-scale online study. We also put listening histories in contrast to other lifelogging data. The resonant and enthusiastic feedback that we received from average users shows a need for making their personal data accessible. We hope to stimulate such developments through this research.
The document discusses how agile principles and practices can be applied to game development, which differs from traditional software development in having motivated cross-functional teams and not just focusing on software. It analyzes problems found in game development postmortems and finds they are the same as the traditional software industry: budget, scope, quality, and schedule issues. While agile is a good fit, practices need to be adapted as games can't run the same tests as other software. Examples are given of game studios successfully applying agile principles like pair programming and retrospectives to deliver better games more efficiently.
Dominikus Baur is a PhD student at the University of Munich who studies listening histories, which are digital records of all music a person has listened to. He discusses how listening histories can serve as reminders of the past similar to photos. They are a type of lifelogging data that provides benefits like reminiscing, recollecting, retrieving, reflecting on one's life, and remembering future intentions. Baur then outlines potential projects involving visualizing listening histories to make them understandable and useful for people.
This document discusses why most organizations are not learning enough and changing effectively. It argues that true change requires moving away from top-down, uniform change programs towards independent, business-aligned teams with decision autonomy, visibility, knowledge sharing, and an emphasis on learning through trying new things. The key is shifting from a focus on control to one of openness, meritocracy, flexibility and collaboration both within and across teams.
Rush: Repeated Recommendations on Mobile Devices - IUI'10Dominikus Baur
Conference presentation in Intelligent User Interfaces - IUI 2010:
Rush is an interaction technique for mobile touchscreen devices. It combines recommendation with interaction and allows users to create personalized collections from item sets (e.g., music playlists).
El documento describe la rutina diaria y las actividades de un grupo de niños en la escuela infantil. Comienza con las rutinas de la mañana como ponerse la bata, saludarse, pasar lista y limpiar la pizarra. Luego detalla las diferentes actividades educativas y lúdicas que realizan durante el día como trabajos en grupo, ciencias, música, recreo y visitas. Finalmente menciona algunas celebraciones como la Castañada, el día de Reyes y el Carnaval.
The presentation introduces the Lean Lego Game, which uses a hands-on simulation to teach Lean principles. It begins with a quick introduction and then guides participants through several rounds of building toy seals on an simulated production line. This allows them to experience problems with push-based mass production systems like waste and uneven workload. It then introduces Lean concepts like pull systems, kanban, continuous flow, and just-in-time production to resolve these issues. The goal is for participants to learn Lean thinking through an engaging exercise and reflect on how these principles can be applied to software development.
The document summarizes a workshop on introducing Lean concepts using a simulation game called "The Lego Lean Game". The workshop covers Lean principles like push/pull systems, Kanban, flow, and continuous improvement. Participants role-play building houses on an assembly line to experience problems with batched production and long lead times. They then apply Kanban and other Lean tools to smooth workflow. The document emphasizes that Lean is not just a set of tools but a management philosophy for eliminating waste and respecting people.
The document summarizes a presentation titled "The Business of Experience: Hands-On Methods to Increase Your Influence" given by Jess McMullin at DocTrain West 2008. The presentation covered introductory remarks, design, business, influence, and pivot methods. It also provided an overview of different understanding methods like interviews, surveys, usability testing and workshops that can be used to increase design maturity and help with problem solving and framing.
Introduction Challenges In Agile And How To Overcome ThemConSanFrancisco123
The document discusses challenges that can arise when adopting agile practices. It outlines some of the core principles of agile development from the Agile Manifesto. It then explores specific challenges that can occur with agile environments, teams, and adoption in large or distributed organizations. The document lists several speakers at a conference that will address challenges of agile transitions, database refactoring, using agile in mainframe environments, agile at large scale, and dealing with perfectionism.
The document discusses gaps and achievements in culture, processes, people, and systems at an organization. It identifies key cultural gaps like a lack of product culture and technical debt. Process gaps include unrealistic estimates and a lack of accountability. People gaps include prioritizing bodies over skills. System gaps require new business models focused on results rather than time/effort. Achievements include cost savings, performance improvements, and workforce reductions for clients through techniques like code reengineering. The document proposes addressing these issues through consulting support, analyzing gaps, and adopting new technologies.
Collaboration Tools to Create Better ProductsEnthiosys Inc
Luke Hohmann presentation at Insight Forum. Provided concrete tools and concepts for collaborating with internal and external stakeholders to create better products
Effective Product Development Using Agile MethodsNaresh Jain
Effective Product Development Using Agile Methods presentation by Baps for Agile Chennai 2007 conference http://agileindia.org/agilechennai07/index.htm
Michael Krigsman, CEO of Asuret Inc., presented on governance and failure. He discussed how 30-70% of IT projects are late, over budget or don't meet requirements despite methodologies and tools. Governance issues like lack of alignment between business and IT are common causes of failure. Asuret uses a failure analysis simulation to measure 7 key factors of success and gain insights from stakeholders to better understand and prevent failures. Key lessons included the importance of knowledge sharing, early warning signs, and exercising wise judgment.
Defrag Keynote: Social Computing and the Enterprise-Bridging the GapMark Koenig
Slides for Keynote Address at Defrag Conference, Denver CO. November 3, 2008.
Before citing, please review Saugatuck's Citation Policy at http://www.saugatech.com/citationpolicy.htm
IBM Smarter Business 2012 - Innovation på IBMIBM Sverige
Med 5800 godkända US patent förra året passerad inte bara IBM 5000 vallen utan befäste också positionen som världens mest innovativa företag för 18 :e året i rad. Mikael Haglund som tilldagligdags är Chief Technologist och evangelist inom Innovation på IBM i Norden, förklarar vad Innovation är och vad som krävs för att man skall bli framgånsgrik inom Innovation. Ta med dig en del vår erfarenhet och vad som krävs för att lyckas inom Innovation.
Talare: Andreas Lundgren, Corporate Citizenship & Corporate Affairs Manager, IBM
Besök http://smarterbusiness.se för mer information.
The document describes a hands-on simulation game used to teach Lean principles. It discusses how the simulation demonstrates common problems in push-based production systems like overproduction and waiting. It then shows how using Lean concepts like pull systems and work cells improves the production process by reducing waste. Finally, it discusses how Lean principles can be applied to software development despite differences from manufacturing.
The document discusses the challenges of distributed agile development. It argues that agile practices assume co-location of teams, while distributed development involves physical separation. This separation increases communication barriers and misunderstandings. Truly successful distributed agile requires practices like cross-functional teams, frequent demonstrations, shared environments and culture, and regular face-to-face meetings to overcome these challenges.
The Agile Primer: Agile Best Practices, Tips and MethodsThoughtworks
The document discusses the history and principles of agile development methods. It describes how agile methods evolved from software engineering practices to address shortcomings of traditional heavy weight methodologies. The core of agile is the Agile Manifesto which values individuals, interactions, working software over processes, tools, documentation, and comprehensive planning. Common agile practices are discussed like iterations, user stories, daily stand-ups, co-located teams, and code reviews.
This presentaiton on Overall Equipment Effectiveness, Down Time Analytics and Assett Utilization was developed by me and a coleague during my tenure at ISS. Presentation was given to the Chattanooga, TN Chapter of the SME.
The document presents a 10 step model for agile requirements that includes defining the objective, stakeholders, vision, roles, personas, user stories, acceptance tests, development, delivery, and checking the delivered value. It argues that there is more to requirements than just user stories and that projects should either take a "salami slice" or goal-directed agile approach. The model is intended to provide insights and ideas for linking together all aspects of agile requirements.
This document describes an approach called Rapid Project Inception that aims to shorten the project inception phase through collaborative workshops. It discusses the benefits of Agile approaches and how focusing on upstream activities like inception can help deliver quality products more quickly. Rapid Project Inception utilizes time-boxed, workshop-driven sessions with a diverse set of stakeholders to define problems, features, estimates and plans through visual techniques and low-fidelity prototypes. The goal is to build a shared understanding and set the project up for faster delivery while still maintaining quality. Challenges of the approach include availability of participants and effective facilitation.
An update to a presentation I posted months ago, this looks at the relationship between knowledge management and enterprise 2.0. It includes several frameworks and details from the Market IQ on enterprise 2.0
Introductionto Agile Executive Overview Gpi Asia Rev2Benjamin Scherrey
Our training partner, GPIAsia, asked us to produce an executive overview version of our 2-day Introduction to Agile course for an iTAP program intended to introduce Agile concepts to CMMI practitioners. Was an interesting challenge. Should know in a week or two if any of this gets traction from that audience. If it does, I'll take credit. If not - I'll blame my colleague Pam who delivered it with me. :-) As with all my presentations, you really need to hear the talk to get the full benefit but at least you can see the subjects we touch on.
Getting Management Buy In Your Top 7 ActionsAndrewLi
This document provides tips for achieving management buy-in for IT projects. It recommends managing the buy-in process with a dedicated resource. Key factors include identifying stakeholders, assigning a single business owner, getting funding approved, providing regular updates to prevent surprises, measuring return on investment before and after, and leveraging past successes to build confidence. Following these seven steps can help set projects up for success and lower the risk of not achieving necessary buy-in.
This document discusses how to promote innovation within a company by getting ideas from everyone. It proposes having the entire company vote every two weeks on experiment ideas that are aligned with company objectives. Anyone can propose an idea and become the experiment lead if it is prioritized. This approach aims to avoid blockers to ideas, focus on execution, and give decisions to those closest to the ground while maintaining high adaptability. Potential downsides are discussed such as lack of long term roadmaps and added process overhead.
This document discusses why change programs often fail and what can be done to improve them. It argues that traditional top-down, management-driven change approaches face resistance because they do not give employees ownership and control. Alternative approaches that empower employees and encourage bottom-up innovation are explored, including examples from companies like Semco, HCL, and Whole Foods that have decentralized decision-making. The document advocates for new management styles focused on openness, meritocracy, flexibility and collaboration to better enable organizational adaptation and change.
This document describes a Kaizen Lego game used to teach Lean and continuous improvement principles. The game has participants build Lego seals while tracking inventory and cycle time. Over multiple iterations, standards are introduced and improved using tools like 5 Whys, value stream mapping and problem analysis. The goal is to continuously eliminate waste and inefficiencies to deliver seals faster and with less cost. The document emphasizes that improvement is an ongoing, long-term process requiring respect for people and learning.
O documento discute técnicas de coaching para influenciar equipes sem autoridade formal, como observar problemas, sugerir soluções gradualmente, e conquistar respeito mostrando entendimento dos desafios da equipe. Apresenta também estratégias como espalhar ideias lentamente, aproveitar intervalos para conversas informais, e resistir a forçar mudanças sem apoio.
The document discusses whether Agile has become mainstream in a way similar to how Waterfall became institutionalized. While surveys show growing adoption of Agile processes and practices, the authors argue that many organizations have only adopted surface-level aspects of Agile without fully embracing its cultural mindset. As a result, some Agile projects are at risk of failing. True adoption requires not just new processes but changes to organizational culture and a long-term investment in developing expertise.
Este documento discute os desafios de implementar métodos ágeis no mundo real. Apresenta os principais pontos como: 1) métodos ágeis são populares, mas muitas vezes mal compreendidos; 2) na prática, a teoria é diferente e há desafios como equipes burocráticas e backlogs infinitos; 3) os princípios como interações individuais, software funcionando e colaboração com o cliente são mais importantes do que processos e ferramentas.
O documento discute os desafios da adoção de métodos ágeis em larga escala. Afirma que, embora mais projetos estejam adotando métodos ágeis, muitos estão falhando por falta de preparo e entendimento correto desses métodos. Argumenta que métodos ágeis não são uma solução fácil e requerem experiência para serem implementados com sucesso, não sendo apropriados para desenvolvedores iniciantes ou quando aplicados de forma rígida.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.