BA World Boston: Evening the Odds with Monte Carlo Project ForecastingWm. Hunter Tammaro
This document discusses using Monte Carlo forecasting to predict project completion dates. It explains that Monte Carlo forecasting acknowledges variability and uncertainty by running multiple simulations of random task durations to predict a range of possible completion dates. The document provides instructions for creating a Monte Carlo forecast, discusses how the technique was used on a project, and notes some limitations and variations of the approach.
This session will review the concept of WIP and explore in-depth the reasons for limiting WIP: enhancing focus, reducing cycle time, optimizing flow and making bottlenecks visible. We will give strategies for starting out with WIP limits and suggestions for what to do when a limit is reached. Finally, we'll put theory to practice by running a short, virtual simulation that all attendees can participate in.
Limiting WIP: Doing Less to Do More @ Big Apple Scrum Day_5.11.18Julie Wyman
The document discusses limiting work-in-progress (WIP) to improve productivity. It explains that limiting WIP leads to better quality, faster delivery, and less stress by improving flow. Too much WIP results in long wait times and slow response to changes, while just enough WIP keeps work moving with some idle time used for improvements. The document advocates starting with small WIP limits and using slack time as a signal to address bottlenecks. An exercise demonstrates teams completing a paper airplane assembly task faster with limited WIP by reducing waste and improving flow.
BASD 2019 - Measuring Flow: Metrics that MatterJulie Wyman
The document discusses various metrics that can be used to measure workflow and identify bottlenecks, including throughput, cycle time, lead time, and cumulative flow diagrams. It explains that prioritizing flow over utilization results in more rapid workflow and shorter response times. Various flow metrics are defined and examples are provided to illustrate how they can be collected and used to visualize trends, predict delivery times, and identify areas for improvement.
This document outlines an 8-phase project timeline with 8 milestones from January 15 to December 28. It is divided into 4 phases ranging from 8.4 to 26.4 weeks. Key milestones include Milestone 1 on January 15, Milestone 2 on February 20, and the final Milestone 8 on December 28. The timeline is created with Office Timeline, a free PowerPoint add-in that allows users to easily make timelines and Gantt charts within PowerPoint.
The federal government loves modernizing software systems and it isn't wrong: stale, decaying software leads to major headaches and eventual catastrophe. Modernization efforts, however, have big risks and big failures.
There is an alternative: software renovation. That is improving, updating, and upgrading the software system one piece at a time while it continues to operate.
Dane has participated deeply in three US government modernization projects. Each project followed a pattern of pitfalls, scary "go-live" transitions, and unpleasant trade-offs.
Renovating legacy software is frequently a better option. The software system continues to gain functionality at the same time that its design and performance are improved.
This document outlines a project timeline with 5 milestones from August 29 to October 3. It is divided into two phases, with phase 1 spanning 11 days and containing 4 sub-tasks of varying durations, and phase 2 spanning 12 days and containing 4 sub-tasks. The timeline also advertises a free PowerPoint add-in called Office Timeline that allows users to easily create and edit Gantt charts directly within PowerPoint.
BA World Boston: Evening the Odds with Monte Carlo Project ForecastingWm. Hunter Tammaro
This document discusses using Monte Carlo forecasting to predict project completion dates. It explains that Monte Carlo forecasting acknowledges variability and uncertainty by running multiple simulations of random task durations to predict a range of possible completion dates. The document provides instructions for creating a Monte Carlo forecast, discusses how the technique was used on a project, and notes some limitations and variations of the approach.
This session will review the concept of WIP and explore in-depth the reasons for limiting WIP: enhancing focus, reducing cycle time, optimizing flow and making bottlenecks visible. We will give strategies for starting out with WIP limits and suggestions for what to do when a limit is reached. Finally, we'll put theory to practice by running a short, virtual simulation that all attendees can participate in.
Limiting WIP: Doing Less to Do More @ Big Apple Scrum Day_5.11.18Julie Wyman
The document discusses limiting work-in-progress (WIP) to improve productivity. It explains that limiting WIP leads to better quality, faster delivery, and less stress by improving flow. Too much WIP results in long wait times and slow response to changes, while just enough WIP keeps work moving with some idle time used for improvements. The document advocates starting with small WIP limits and using slack time as a signal to address bottlenecks. An exercise demonstrates teams completing a paper airplane assembly task faster with limited WIP by reducing waste and improving flow.
BASD 2019 - Measuring Flow: Metrics that MatterJulie Wyman
The document discusses various metrics that can be used to measure workflow and identify bottlenecks, including throughput, cycle time, lead time, and cumulative flow diagrams. It explains that prioritizing flow over utilization results in more rapid workflow and shorter response times. Various flow metrics are defined and examples are provided to illustrate how they can be collected and used to visualize trends, predict delivery times, and identify areas for improvement.
This document outlines an 8-phase project timeline with 8 milestones from January 15 to December 28. It is divided into 4 phases ranging from 8.4 to 26.4 weeks. Key milestones include Milestone 1 on January 15, Milestone 2 on February 20, and the final Milestone 8 on December 28. The timeline is created with Office Timeline, a free PowerPoint add-in that allows users to easily make timelines and Gantt charts within PowerPoint.
The federal government loves modernizing software systems and it isn't wrong: stale, decaying software leads to major headaches and eventual catastrophe. Modernization efforts, however, have big risks and big failures.
There is an alternative: software renovation. That is improving, updating, and upgrading the software system one piece at a time while it continues to operate.
Dane has participated deeply in three US government modernization projects. Each project followed a pattern of pitfalls, scary "go-live" transitions, and unpleasant trade-offs.
Renovating legacy software is frequently a better option. The software system continues to gain functionality at the same time that its design and performance are improved.
This document outlines a project timeline with 5 milestones from August 29 to October 3. It is divided into two phases, with phase 1 spanning 11 days and containing 4 sub-tasks of varying durations, and phase 2 spanning 12 days and containing 4 sub-tasks. The timeline also advertises a free PowerPoint add-in called Office Timeline that allows users to easily create and edit Gantt charts directly within PowerPoint.
Bootstrapping your startup & building it lean: stop wasting timeJoel Gascoigne
This document summarizes techniques for bootstrapping a startup on a lean budget with no outside investment. It discusses methodologies promoted by thought leaders like Eric Ries (Lean Startup), Steve Blank (Customer Development), Sean Ellis (Product/Market Fit), and Dave McClure (Pirate Metrics). Key recommendations include developing a minimum viable product, continuously testing and iterating based on customer feedback, using metrics over opinions, and leveraging cloud services to reduce costs and focus on the core product.
A talk I gave internally at Wotif about using Rally, from RallyDev, for managing iterations. Generally good advice on how to run a team using Rally as a project-management tool (at least I think so)
Editable PowerPoint project plan template - wide screenOffice Timeline
This document provides a timeline for a project with 6 milestones and 6 tasks from January 2015 through December 2015. It shows the dates for each milestone and task period. It also includes an advertisement for an Office Timeline PowerPoint add-in that allows automatically updating timelines and creating Gantt charts within PowerPoint.
Kanban is a lean methodology for managing workflow. Its core practices include visualizing workflow using a kanban board with columns for different states, limiting work-in-progress to avoid bottlenecks, making policies explicit, and implementing feedback loops to continuously improve. Kanban focuses on managing flow rather than fixed processes, and emphasizes finishing work rather than starting new work. Kanban stand-ups differ from Scrum in that the focus is on identifying impediments rather than commitments.
This document discusses making changes in large organizations and lessons learned from trying to implement improvements. It notes that change normally comes from the top down and cultures are focused on getting things done despite obstacles. Several approaches are mentioned, including value stream mapping, Kanban, and Lean Coffee. The document emphasizes that change happens gradually through baby steps and with executive support. It also provides tips for handling uncertain requirements on projects and reporting on progress using Kanban under more generic high-level plans. The overall message is that small, incremental changes can enable improvement through understanding value and empowering teams.
This document outlines a project timeline from May 2015 to December 2015. It details two phases - a mechanical phase from May to September and an electrical phase from May to December. Key milestones for each phase include material availability, testing completion, certification, production, and conditional release. The timeline provides visual representation of schedule and dependencies between tasks in the two project phases.
Breakout session at MERL Tech 2018.
Agile - commonly used in the tech community - offers a number of sticky ideas and principles we can adapt in international development and MERL to improve how we work and support adaptive management.
In this breakout, we focus on three sticky ideas: creating and being guided by user stories, prioritization, and limiting WIP.
This document outlines a project timeline with 5 milestones from August 29 to October 3. It is divided into two phases, with phase 1 spanning 11 days and containing 3 sub-tasks ranging from 2 to 5 days, and phase 2 spanning 12 days and containing 4 sub-tasks from 3 to 5 days. The timeline template can be automatically updated and customized using the free Office Timeline PowerPoint add-in.
Being productive is a great advantage. So, today, we will give you some tips on how to work faster and be productive with great results. Keep checking our blog for more tips & tricks at http://kanbantool.com/blog.
Agile Patterns: Estimation - Stephen Forte | FalafelCON 2014FalafelSoftware
The document discusses agile estimation techniques. It defines estimation as "the calculated approximation of a result which is usable even if input data may be incomplete or uncertain." Traditionally, estimates become an unbreakable schedule where any deviation is seen as bad. However, agile estimation throws this logic away and always re-estimates a project after each iteration. Using techniques like user stories, story points, planning poker, and velocity, agile estimation embraces the uncertainty in estimates and sees deviations not as failures but as opportunities for more accurate estimations.
Project planning template editable in PowerPoint - wide screenOffice Timeline
The document outlines a project timeline that spans from August 2015 to March 2016. It is divided into several phases including project sourcing, readiness, development, testing and reviews, documentation, and adjustment. Key milestones and dates are provided for securing the budget, identifying a project manager, setting up certification, production beginning, analyzing results, and wrapping up the audit.
TuleapCon 2019. STMicroelectronics- Monitoring Activity and Deliverables of l...Tuleap
IT Programs at ST are worldwide large projects composed of multiples teams and leaders to coordinate. To manage large programs, how avoid hundreds of non-tracked emails and over-complex tools?
Pierre-Yves COLLE shares how he designed and adapted workspaces with Tuleap to perfectly suit his needs: get at the same time, an helicopter view for his top management and an analysis detailed view for monitoring progress at project level.
This document outlines an 8 milestone project plan from September to November 2015, including the dates for each milestone and 5 tasks with their duration. Milestones 1 through 8 are scheduled on specific dates from September 8 to November 30. Five tasks are also listed with their start and end dates, ranging in duration from 17 to 44 days. The document promotes downloading a free Office Timeline PowerPoint add-in to easily edit timelines and create Gantt charts within PowerPoint.
An introduction to Reactive applications, Reactive Streams, and options for t...Steve Pember
This document provides an overview of reactive applications and Reactive Streams. It discusses the need for reactive approaches to address increasing performance demands and microservices. Reactive applications are responsive, resilient, elastic and asynchronous. Reactive Streams provide a common abstraction for data streams and asynchronous data sources using an observer pattern. The document also summarizes several Reactive Streams implementations for the JVM like RxJava and frameworks like Spring WebFlux, Play and Vert.x that support reactive programming.
This document outlines a project timeline from May 2015 to December 2015. It details two phases - a mechanical phase from May to September and an electrical phase from May to December. Key milestones for each phase include material availability, testing completion, certification, production, and conditional release. The timeline provides specific target dates to track progress.
Editable PowerPoint Gantt chart timeline template for project managementOffice Timeline
This document contains a Gantt chart timeline showing 12 tasks of varying durations between June 2015 and February 2016. Key milestones are indicated at the start and end of the timeline as well as after tasks 3, 4, and 5. The timeline can be automatically updated and edited using the free Office Timeline PowerPoint add-in.
As scrum masters, agile coaches and facilitators we spend a lot of time and energy to come up with new and ever-changing retrospective formats. Our goals are noble- we want to get people engaged, build trust within the team, change the perspective, reframe the conversation, and keep everyone coming back for more. What we are really trying to achieve in varied retrospective formats isn’t more data, its better data. Learn the five types of retrospective data your team needs for targeted improvements that guarantee more than a bi-weekly "airing of grievances." We will focus on how to solicit all five types of data while gathering feedback continuously so you can maximize your retrospective conversations on improving and not remembering.
The document discusses limiting work in progress (WIP) to improve productivity. Some key points:
1. Limiting WIP to 1-3 items leads to faster delivery, better quality, and less stress by avoiding multitasking. It also makes bottlenecks more visible.
2. Studies show multitasking is inefficient and can reduce productivity by 40% due to switching costs. Limiting WIP reduces context switching.
3. With too much WIP, teams spend most time waiting rather than working. Limiting WIP improves flow and enables faster response to changes.
Limiting work-in-progress, or WIP, is a core principle of Kanban, and is a common recommendation to teams using Scrum or other frameworks as well. Yet the idea that working on less can lead you to get more done seems to defy common sense. Even those who understand the reasons for limiting WIP can struggle with resistance from team members or leaders when putting the theory to practice.
This session will review the concept of WIP and explore in depth the reasons for limiting WIP: enhancing focus, reducing cycle time, optimizing flow and making bottlenecks visible. We will give strategies for starting out with WIP limits and suggestions for what to do when a limit is reached. Attendees will also participate in a short simulation that will illustrate the concepts in practice, and that attendees can use on their own projects to help overcome skepticism of WIP limits in their organizations.
Bootstrapping your startup & building it lean: stop wasting timeJoel Gascoigne
This document summarizes techniques for bootstrapping a startup on a lean budget with no outside investment. It discusses methodologies promoted by thought leaders like Eric Ries (Lean Startup), Steve Blank (Customer Development), Sean Ellis (Product/Market Fit), and Dave McClure (Pirate Metrics). Key recommendations include developing a minimum viable product, continuously testing and iterating based on customer feedback, using metrics over opinions, and leveraging cloud services to reduce costs and focus on the core product.
A talk I gave internally at Wotif about using Rally, from RallyDev, for managing iterations. Generally good advice on how to run a team using Rally as a project-management tool (at least I think so)
Editable PowerPoint project plan template - wide screenOffice Timeline
This document provides a timeline for a project with 6 milestones and 6 tasks from January 2015 through December 2015. It shows the dates for each milestone and task period. It also includes an advertisement for an Office Timeline PowerPoint add-in that allows automatically updating timelines and creating Gantt charts within PowerPoint.
Kanban is a lean methodology for managing workflow. Its core practices include visualizing workflow using a kanban board with columns for different states, limiting work-in-progress to avoid bottlenecks, making policies explicit, and implementing feedback loops to continuously improve. Kanban focuses on managing flow rather than fixed processes, and emphasizes finishing work rather than starting new work. Kanban stand-ups differ from Scrum in that the focus is on identifying impediments rather than commitments.
This document discusses making changes in large organizations and lessons learned from trying to implement improvements. It notes that change normally comes from the top down and cultures are focused on getting things done despite obstacles. Several approaches are mentioned, including value stream mapping, Kanban, and Lean Coffee. The document emphasizes that change happens gradually through baby steps and with executive support. It also provides tips for handling uncertain requirements on projects and reporting on progress using Kanban under more generic high-level plans. The overall message is that small, incremental changes can enable improvement through understanding value and empowering teams.
This document outlines a project timeline from May 2015 to December 2015. It details two phases - a mechanical phase from May to September and an electrical phase from May to December. Key milestones for each phase include material availability, testing completion, certification, production, and conditional release. The timeline provides visual representation of schedule and dependencies between tasks in the two project phases.
Breakout session at MERL Tech 2018.
Agile - commonly used in the tech community - offers a number of sticky ideas and principles we can adapt in international development and MERL to improve how we work and support adaptive management.
In this breakout, we focus on three sticky ideas: creating and being guided by user stories, prioritization, and limiting WIP.
This document outlines a project timeline with 5 milestones from August 29 to October 3. It is divided into two phases, with phase 1 spanning 11 days and containing 3 sub-tasks ranging from 2 to 5 days, and phase 2 spanning 12 days and containing 4 sub-tasks from 3 to 5 days. The timeline template can be automatically updated and customized using the free Office Timeline PowerPoint add-in.
Being productive is a great advantage. So, today, we will give you some tips on how to work faster and be productive with great results. Keep checking our blog for more tips & tricks at http://kanbantool.com/blog.
Agile Patterns: Estimation - Stephen Forte | FalafelCON 2014FalafelSoftware
The document discusses agile estimation techniques. It defines estimation as "the calculated approximation of a result which is usable even if input data may be incomplete or uncertain." Traditionally, estimates become an unbreakable schedule where any deviation is seen as bad. However, agile estimation throws this logic away and always re-estimates a project after each iteration. Using techniques like user stories, story points, planning poker, and velocity, agile estimation embraces the uncertainty in estimates and sees deviations not as failures but as opportunities for more accurate estimations.
Project planning template editable in PowerPoint - wide screenOffice Timeline
The document outlines a project timeline that spans from August 2015 to March 2016. It is divided into several phases including project sourcing, readiness, development, testing and reviews, documentation, and adjustment. Key milestones and dates are provided for securing the budget, identifying a project manager, setting up certification, production beginning, analyzing results, and wrapping up the audit.
TuleapCon 2019. STMicroelectronics- Monitoring Activity and Deliverables of l...Tuleap
IT Programs at ST are worldwide large projects composed of multiples teams and leaders to coordinate. To manage large programs, how avoid hundreds of non-tracked emails and over-complex tools?
Pierre-Yves COLLE shares how he designed and adapted workspaces with Tuleap to perfectly suit his needs: get at the same time, an helicopter view for his top management and an analysis detailed view for monitoring progress at project level.
This document outlines an 8 milestone project plan from September to November 2015, including the dates for each milestone and 5 tasks with their duration. Milestones 1 through 8 are scheduled on specific dates from September 8 to November 30. Five tasks are also listed with their start and end dates, ranging in duration from 17 to 44 days. The document promotes downloading a free Office Timeline PowerPoint add-in to easily edit timelines and create Gantt charts within PowerPoint.
An introduction to Reactive applications, Reactive Streams, and options for t...Steve Pember
This document provides an overview of reactive applications and Reactive Streams. It discusses the need for reactive approaches to address increasing performance demands and microservices. Reactive applications are responsive, resilient, elastic and asynchronous. Reactive Streams provide a common abstraction for data streams and asynchronous data sources using an observer pattern. The document also summarizes several Reactive Streams implementations for the JVM like RxJava and frameworks like Spring WebFlux, Play and Vert.x that support reactive programming.
This document outlines a project timeline from May 2015 to December 2015. It details two phases - a mechanical phase from May to September and an electrical phase from May to December. Key milestones for each phase include material availability, testing completion, certification, production, and conditional release. The timeline provides specific target dates to track progress.
Editable PowerPoint Gantt chart timeline template for project managementOffice Timeline
This document contains a Gantt chart timeline showing 12 tasks of varying durations between June 2015 and February 2016. Key milestones are indicated at the start and end of the timeline as well as after tasks 3, 4, and 5. The timeline can be automatically updated and edited using the free Office Timeline PowerPoint add-in.
As scrum masters, agile coaches and facilitators we spend a lot of time and energy to come up with new and ever-changing retrospective formats. Our goals are noble- we want to get people engaged, build trust within the team, change the perspective, reframe the conversation, and keep everyone coming back for more. What we are really trying to achieve in varied retrospective formats isn’t more data, its better data. Learn the five types of retrospective data your team needs for targeted improvements that guarantee more than a bi-weekly "airing of grievances." We will focus on how to solicit all five types of data while gathering feedback continuously so you can maximize your retrospective conversations on improving and not remembering.
The document discusses limiting work in progress (WIP) to improve productivity. Some key points:
1. Limiting WIP to 1-3 items leads to faster delivery, better quality, and less stress by avoiding multitasking. It also makes bottlenecks more visible.
2. Studies show multitasking is inefficient and can reduce productivity by 40% due to switching costs. Limiting WIP reduces context switching.
3. With too much WIP, teams spend most time waiting rather than working. Limiting WIP improves flow and enables faster response to changes.
Limiting work-in-progress, or WIP, is a core principle of Kanban, and is a common recommendation to teams using Scrum or other frameworks as well. Yet the idea that working on less can lead you to get more done seems to defy common sense. Even those who understand the reasons for limiting WIP can struggle with resistance from team members or leaders when putting the theory to practice.
This session will review the concept of WIP and explore in depth the reasons for limiting WIP: enhancing focus, reducing cycle time, optimizing flow and making bottlenecks visible. We will give strategies for starting out with WIP limits and suggestions for what to do when a limit is reached. Attendees will also participate in a short simulation that will illustrate the concepts in practice, and that attendees can use on their own projects to help overcome skepticism of WIP limits in their organizations.
Pair programming involves two programmers working together at one computer. One person acts as the driver who types code while the other navigates and reviews. It has benefits like catching mistakes earlier, improving design quality, transferring knowledge between partners, and creating a stronger sense of team. While there is initially a 15% overhead in time, studies show this is outweighed by fewer defects and a more flexible system in the long run. Effective pair programming requires collaboration, respect, communication and regularly alternating roles.
"Multitasking is Evil" & Other Games to Convince You (or your manager!) to Li...Julie Wyman
For a long time multitasking was considered a must-have skill when, in fact, multitasking makes us less productive and more prone to error. But even with plenty of studies and papers supporting that idea, it can be hard to convince managers and stakeholders that we should be taking on less at a time. In this session, we'll run through 3 short simulations (Multitasking is Evil, Name Game, & Featureban) you can use to help make that case and show that lowering our work in progress is the way to go!
I'm a BA Girl in an Agile World @AgileDC 20190923Mindy Bohannon
Presented at AgileDC conference on Sept 23, 2019. Described how a Business Analyst fits into Product Development when the team is using the Agile Methodology
HOnza Koudelka erklärt an der FileMaker Konferenz 2016 in Salzburg wie man mit FileMaker eine Audit Lösung machen und die Geschwindigkeit verbessern kann.
Agile Dev West 2018_Measuring Flow: Metrics that MatterJulie Wyman
The document discusses different metrics for measuring workflow, including lead time, cycle time, throughput, and cumulative flow diagrams (CFDs). It explains that lead time is the total time from start to finish of a work item, while cycle time does not include wait time. Throughput measures the number of work items completed within a time period. CFDs visualize the number of work items in different workflow stages over time to identify bottlenecks. The document provides examples of charts for these different metrics and discusses how teams can use metrics to understand their workflow and improve predictability.
This document provides an overview of various topics related to developing a NodeJS application with a database. It discusses mindsets for developers, resources for learning to code like online courses and communities, and technologies involved in web development like front-end versus back-end programming. It also introduces NodeJS, databases like MongoDB and Cloudant, and provides instructions for an example app using Cloudant on Bluemix. Students are assigned homework to deploy this example app and modify it for their own purposes.
This document outlines traits of a good engineer according to a talk given by N.R. Rajagopal. It discusses seven key traits: 1) Curiosity - having an insatiable desire to understand how things work beyond surface level issues. 2) Finding ways to break things - looking at boundary conditions and edge cases. 3) Ability to get up to speed quickly on new large codebases. 4) Making tradeoffs between competing factors like time, cost and quality. 5) Designing for long-term maintainability rather than short-term goals. 6) Commitment to lifelong learning as technology continually changes. 7) Taking pride in one's work and enjoying challenges.
Are you currently running Oracle Forms and are you thinking about beginning an Oracle ADF project, or are you about to start Oracle Forms modernization to Oracle ADF?
As a consulting company we have been involved in dozens of modernization projects.
There are valuable tips and tricks that you can learn from.
From teams setup to technical best practices, and from automated migration to manual rebuild.
What is the best way to setup a team ?
Where to start ?
What to do, and more important, what not to do ?
Can you reuse existing Business Rules ?
What about layout and user interaction ?
What do you need to know ?
In this session you will see a top 10 of lessons learned when going from Oracle Forms to Oracle ADF.
This document provides an overview of Scrum and agile software development. It defines Scrum as an agile, lightweight process that uses iterative, incremental practices to manage software development. Key aspects of Scrum covered include its origins, framework, roles, ceremonies, artifacts like product and sprint backlogs, and how it compares to other models. Scaling Scrum to larger teams using a "Scrum of Scrums" approach is also discussed.
The document discusses the origins and key principles of DevOps. It originates from a 2009 Velocity Conference talk about Flickr's deployment practices of 10+ deploys per day through automation, shared version control, and one-step builds. The main principles discussed are CAMS - Culture, Automation, Measurement, and Sharing. Culture focuses on respect, trust, and avoiding blame. Automation, measurement, and sharing are also emphasized as important aspects of DevOps.
This document provides tips and advice for new electronic resources librarians (ERLs). It discusses the challenges ERLs face in defining their roles, dealing with inconsistent daily routines and high expectations. It offers suggestions for improving efficiency through documenting workflows, effective communication and information management. The document also addresses managing vendors, promoting resources, analyzing usage statistics and getting involved in the library community.
This document provides an overview of Scrum and agile software development. It defines Scrum as an agile, lightweight process that uses iterative, incremental practices to manage software development. Key aspects of Scrum covered include its origins, framework, roles, ceremonies, artifacts like product and sprint backlogs, and how it compares to other models. Scaling Scrum to larger teams using a "Scrum of Scrums" approach is also discussed.
"Startups, comment gérer une équipe de développeurs" par Laurent CerveauTheFamily
The document discusses various topics related to developing a technology product, including hiring an engineering team, creating a product, technical development challenges, and setting up processes. It provides advice on tuning your setup by considering human resources, available technologies, tools, and processes. It discusses common pitfalls and emphasizes focusing on users and testing. Technical concepts discussed include infrastructure, programming languages, servers, APIs, storage, desktop development, and mobile development.
This document outlines how a scrum team conducts various scrum activities including:
- Using a wall-based task board to track sprint backlog items and update tasks during daily stand-ups.
- Arranging their team room with the product owner and managers at a remove to allow for self-organization.
- Conducting daily 15 minute stand-ups to synchronize work and raise impediments.
- Communicating sprint information through a sprint info page and demo reminders.
- Dealing with issues like latecomers to stand-ups or team members not knowing what to work on through techniques like peer pressure.
When going into the development of a software product, a possible source of mistake is the incorrect evaluation of the complexity that lies behind an idea , as well as a clutter coming from the massive amounts of technologies enabled. This presentation explains a possible way to deal with such issues.
Similar to Limiting WIP - Music City Tech 2021 (20)
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
AI 101: An Introduction to the Basics and Impact of Artificial IntelligenceIndexBug
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
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
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.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
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
UiPath Test Automation using UiPath Test Suite series, part 6
Limiting WIP - Music City Tech 2021
1. excella.com | @excellaco
Limiting WIP:
Doing Less to Do More
Hunter Tammaro & Julie Wyman
While we wait to get started: Answer a question on Menti!
1. Go to www.menti.com on your computer or phone
2. Enter code 1834 5533
3. Submit your answer
2. excella.com | @excellaco
Julie Wyman
• 12 years in Agile environments –
Scrum, Kanban, scaled approaches
• Commercial, federal, non-profit
• Local Meetup, regional, and national
conference speaker
• Frequent traveler, Green Bay Packers
fan, and Great British Bake-Off watcher
Agile Coach & Fellow
3. excella.com | @excellaco
Hunter
Tammaro
• 9 years working with Agile –
Scrum, Kanban, scaled approaches
• Federal and non-profit
• Local Meetup, regional and national
conference speaker
• Fan of the great outdoors, coffee,
sandwiches and King of the Hill
Agile Coach & Xpert
4. excella.com | @excellaco
Work in Progress
(WIP)
Any partly finished product
or materials in an
incomplete step of a process
Completed work in one
process may be WIP to a
higher-order process
WIP does not provide any
value to a customer
7. excella.com | @excellaco
Faster Delivery & Feedback
Value
Returned
4 Parallel Efforts
WIP = 4
Time
1 Parallel Effort
WIP = 1
Time
Value
Returned
8. excella.com | @excellaco
Switching Costs
Studying costs associated with multitasking, defined as:
• Two tasks simultaneously
• Switching from one task to another
• Perform two or more tasks in rapid succession
Findings:
• “…mind and brain were not designed for heavy-duty multitasking”
• Switching time increases as complexity increases and familiarity decreases
• “…complexities involved in understanding the cognitive load imposed by real-life
multi-tasking, when in addition to reconfiguring control settings for a new task,
there is often the need to remember where you got to in the task to which you are
returning and to decide which task to change to, when.”
https://www.apa.org/research/action/multitask
9. excella.com | @excellaco
“Although switch costs may be relatively small, sometimes just a
few tenths of a second per switch, they can add up…when
people switch repeatedly back and forth between tasks.
Thus, multitasking may seem efficient on the surface but may
actually take more time in the end and involve more error.
…even brief mental blocks created by shifting between tasks can
cost as much as 40 percent of someone's productive time.”
https://www.apa.org/research/action/multitask
11. excella.com | @excellaco
Too much
WIP
Fully utilized, but spend
most of the time waiting
Slow flow through
the system
Slow to respond to change
12. excella.com | @excellaco
On a software team
Total Active
Time:
Total Waiting
Time:
Analysis
(2 days)
Development
(5 days)
Testing
(1 day)
Deploy
(1 day)
Waiting for
development (3 days)
Waiting for
testing (6 days)
Waiting to
deploy (4 days)
13. excella.com | @excellaco
On a software team
Total Active
Time:
9 days
Total Waiting
Time:
13 days
Analysis
(2 days)
Waiting for
development (3 days)
Development
(5 days)
Waiting for
testing (6 days)
Testing
(1 day)
Waiting to
deploy (4 days)
Deploy
(1 day)
14. excella.com | @excellaco
Just enough
WIP
Team members sometimes idle,
but work almost always moving
Rapid flow through the system
Short response time reduces
effect of impediments
15. excella.com | @excellaco
If you had a "free" hour of
time during the day,
what would you do?
Menti: 1834 5533
16. excella.com | @excellaco
Idle team members?!
• Remove blockers
• Help other team members
• Process improvement
• Address technical debt
• Improve your craft
17. excella.com | @excellaco
Slack time as a signal
WIP limits help individuals find ways
to improve the flow of the entire team
Are there issues upstream in the process that can
be resolved?
Are there issues downstream in the process?
Adjust WIP or team composition until
flow is optimized
18. excella.com | @excellaco
Slack as a
requirement
WIP limits prevent burnout
and support creative work
Downtime activates the brain’s
default mode network
Take a walk or coffee break!
19. excella.com | @excellaco
“…during rest, the default mode network can open
connections between brain regions that are normally too
busy … to talk to each other. This is when true creativity and
insight can happen.”
Andrew Smart, Autopilot
“For all creativity measures, a positive correlation was found
between creative performance and gray matter volume of the
default mode network.”
https://onlinelibrary.wiley.com/doi/abs/10.1002/jocb.45
20. excella.com | @excellaco
Setting WIP limits
Requirements Ready Analysis Development Validate Done
3 5 3
4
Doing Done Doing Done
Just start…
Observe
Adjust from
there
Cycle Time
22. excella.com | @excellaco
Round 1
You are assigned three projects.
You will work on the projects one at a time.
• Project 1: Write the numbers 1 -> 15
• Project 2: Write the letters Z -> N
• Project 3: Write the Roman numerals IV -> XVII
23. excella.com | @excellaco
Round 1
Project 1 Project 2 Project 3
1 - 15 Z - N IV - XVII
1 Z IV
2 Y …
… …
Once we say start:
• Work column-by-
column until you
complete all 3 projects
• Write down the time
you finish your first
and last projects
Set up: On a blank piece
of paper, create column
headers for each project
24. excella.com | @excellaco
Round 2
You are assigned three projects.
You will work on the projects all at once.
• Project 1: Write the numbers 20 -> 35
• Project 2: Write the letters Q -> E
• Project 3: Write the Roman numerals V -> XVIII
25. excella.com | @excellaco
Round 2
Project 1 Project 2 Project 3
20 - 35 Q - E V - XVIII
20 Q V
21 P …
… …
Once we say start:
• Work row-by-row
until you complete all
3 projects
• Write down the time
you finish your first
and last projects
Set up: On a blank piece
of paper, create column
headers for each project
27. excella.com | @excellaco
Key Takeaways
Limiting WIP…
• Creates a better-quality
product faster
• Leads to quicker realization of
value and better feedback
• Improves the functioning of the
team by making bottlenecks visible
Remember to…
focus on flow, not utilization
28. excella.com | @excellaco
How to
connect
Julie Wyman
julie.wyman@excella.com
https://www.linkedin.com/in/julie-wyman/
Hunter Tammaro
hunter.tammaro@excella.com
@htammaro
https://www.linkedin.com/in/wmhunter/
Excella
@excellaconsulting
@excellaco
30. excella.com | @excellaco
Links
• Info on switching costs studies from the American Psychological Association
• Huffington Post article with link to multitasking infographic
• Blog posts:
• How to set initial WIP limits
• How Scrum and Kanban approach WIP differently
• Constraints in Scrum and Kanban
• Importance of slack time for creativity
• Books:
• Lean from the Trenches – Henrik Kniberg
32. excella.com | @excellaco
The Name Game
Concept: “Project managers”
compete to have a “developer” write
their name, one letter at a time
• All at once: Direct competition
• Round robin: Developer splits
their time across projects
• One project at a time: Developer
sticks to a WIP limit
See it in action: Video of the game
33. excella.com | @excellaco
Discussion
• In which round did you complete your
first project faster?
• Which round took you more time to
complete all three projects?
• In which round did the developer make
more mistakes?
• In which round did the developer feel
more stressed? The project managers?
• Which round felt more like how you work
in real life?
34. excella.com | @excellaco
Experiment with
another variation!
• From Henrik Kniberg
• Includes a detailed
facilitation guide:
https://www.dropbox.com/s/y
76t4nh8hoq63o3/Multitasking
-Name-Game.docx?dl=0
36. excella.com | @excellaco
Practice Round
Compete to make paper airplanes in
teams of six
One team member at each station
One team member times the construction
of the colored plane
One team member times the entire round
37. excella.com | @excellaco
Round 1
Work as fast as you can,
in a first-in-first-out basis
After 10 planes are completed and tested,
use the worksheet to record:
• The time to make all 10 planes
• The time to make the colored plane
• The number of incomplete planes
• in progress
38. excella.com | @excellaco
Round 2
This time, work with a
WIP limit of 1 per station
E.g., Station 1 can’t start on the next plane
until Station 2 takes their sheet
After 10 planes are completed and tested, use
the worksheet to record:
• The time to make all 10 planes
• The time to make the colored plane
• The number of incomplete planes
in progress
39. excella.com | @excellaco
• In which round did you
complete all 10 planes faster?
• Which round took your team
more time to make the
colored plane?
• In which round was there
more waste?
Discussion
• In which round did you feel
more stressed?
• Which round felt more like
how you work in real life?
41. W e transform your bold ideas
into elegant technology solutions
We are Agilists at our core. We embrace flexibility and collaboration to accelerate
delivery, respond to change, and develop technology that enables people to do
their jobs more easily and solve unsolvable problems.
18 Years
in Business
270+
Employees
20+ Industry
Groups/ Meetups
Award-Winning
Company
42. Our
Solutions
From incremental advances to leaps of
innovation, we make your tech work
for you. Our partners are becoming
more Agile, modernizing their
technology, harnessing data to gain a
competitive advantage, and building
more engaging websites and apps to
win over their customers.
Agile
Transformation
Artificial
Intelligence (AI)
Digital Service
Delivery
Modernization