The document discusses some of the challenges of building web applications and strategies for overcoming them. It notes that web app development can be difficult because details evolve and change, leading to complex and changing requirements. It advocates for having a good team, using version control, automation tools, testing, and managing requirements and work with tools like JIRA and maintaining a story board. The document emphasizes the importance of iterative development, continuous integration, and shipping features regularly.
Learn about how we use ChatOps practices to on the Agile Central release train. Presented at DevOpsDays Rockies 2016. Video at http://confreaks.tv/videos/devopsdaysrox2016-hello-i-m-jarvis-let-s-chatops.
Managing State in Single Page WebApps with Ember.jsMark Mansour
This document provides an overview of managing state in a single page application with Ember.js. It discusses how Ember uses models, controllers and bindings to connect user interfaces and keep data in sync across components. Key aspects covered include Ember objects, computed properties, observers, controllers, bindings and the Ember run loop which handles updating the DOM efficiently.
Is your search relevant? FASTforward Summit Series 3Mark Mansour
Recently Sensis Online Directories has developed an approach to answer the question of “Is our search relevant?”, based on facts rather than by judgement. Companies who have a search component to their systems can be in discussions where statements like the following are made: “We have a problem Y with the results in this area, If we make this change X, the problem of search goes away”. How do you quantify that a simple change in one area solves an issue, in isolation, without causing flow on affects. This presentation talks about the approach Sensis Online Directories have undertaken to quantify the quality of its search and measure improvement and changes.
Do you want to make your next project run more smoothly? Finish faster?
The most popular Agile framework today is Scrum and in these slides you will learn about the Scrum key events. Join us and learn about Agile with the Agile Middle East (ME)
This document provides an overview of Kanban and how it can be used as a process improvement tool. It discusses key Kanban principles like being visual, collaborative and simple. It also provides examples of mapping workflows, tracking work in progress limits, and addressing questions around standups, defects, tools, metrics and expedited items. Visualizations include boards for tracking work through different stages and cumulative flow diagrams for analyzing lead times and throughput.
Handling Non Functional Requirements on an Agile ProjectKen Howard
When adjectives and adverbs appear in User Stories, they can be easily overlooked and seen as simple adornments to the story. There are a couple schools of thought on how to handle non-functional requirements on Agile projects. Mike Cohn recommends writing a User Story for each non-functional requirement, while others recommend creating task cards to drive out specification using Thomas Gilb’s approach. In this session, examples of various techniques for handling non-functional requirements will be demonstrated, with a discussion of pros and cons of each technique.
Learn about how we use ChatOps practices to on the Agile Central release train. Presented at DevOpsDays Rockies 2016. Video at http://confreaks.tv/videos/devopsdaysrox2016-hello-i-m-jarvis-let-s-chatops.
Managing State in Single Page WebApps with Ember.jsMark Mansour
This document provides an overview of managing state in a single page application with Ember.js. It discusses how Ember uses models, controllers and bindings to connect user interfaces and keep data in sync across components. Key aspects covered include Ember objects, computed properties, observers, controllers, bindings and the Ember run loop which handles updating the DOM efficiently.
Is your search relevant? FASTforward Summit Series 3Mark Mansour
Recently Sensis Online Directories has developed an approach to answer the question of “Is our search relevant?”, based on facts rather than by judgement. Companies who have a search component to their systems can be in discussions where statements like the following are made: “We have a problem Y with the results in this area, If we make this change X, the problem of search goes away”. How do you quantify that a simple change in one area solves an issue, in isolation, without causing flow on affects. This presentation talks about the approach Sensis Online Directories have undertaken to quantify the quality of its search and measure improvement and changes.
Do you want to make your next project run more smoothly? Finish faster?
The most popular Agile framework today is Scrum and in these slides you will learn about the Scrum key events. Join us and learn about Agile with the Agile Middle East (ME)
This document provides an overview of Kanban and how it can be used as a process improvement tool. It discusses key Kanban principles like being visual, collaborative and simple. It also provides examples of mapping workflows, tracking work in progress limits, and addressing questions around standups, defects, tools, metrics and expedited items. Visualizations include boards for tracking work through different stages and cumulative flow diagrams for analyzing lead times and throughput.
Handling Non Functional Requirements on an Agile ProjectKen Howard
When adjectives and adverbs appear in User Stories, they can be easily overlooked and seen as simple adornments to the story. There are a couple schools of thought on how to handle non-functional requirements on Agile projects. Mike Cohn recommends writing a User Story for each non-functional requirement, while others recommend creating task cards to drive out specification using Thomas Gilb’s approach. In this session, examples of various techniques for handling non-functional requirements will be demonstrated, with a discussion of pros and cons of each technique.
Devops aims to break down silos between development and operations teams through culture, automation, and continuous integration/delivery. It emphasizes collaboration and automation to allow code to be deployed safely and quickly. Security should be integrated into the devops pipeline through practices like automated security testing on each code change and configuration management to standardize security across environments. Adopting devops and continuous delivery helps improve security by reducing risk through faster issue remediation and increased visibility into systems.
User Story Mapping - mini iad 2014 (Armani, Rodriguez)Fabio Armani
Riteniamo, che non vi sia dubbio sul fatto le User Story (introdotte da eXtreme Programming) e il Product Backlog (definito in Scrum) rappresentino due portentosi strumenti per la gestione agile dei requisiti e delle specifiche sia funzionali che non funzionali. Ma … hanno alcuni limiti.
Ad esempio, nonostante le notevoli caratteristiche del Product Backlog, la sua unidimensionalità non consente di creare un modello dei requisiti adatto a scalare e che consenta di gestire le dipendenze che possono essere presenti tra i vari elementi che lo costituiscono.
In questo workshop presenteremo e utilizzeremo un altro potente strumento che spesso utilizziamo durante gli User Story Workshop sia in fase d’Inception, sia all’inizio di ogni nuova release di un prodotto. Si chiama “User Story Mapping”.
Ci divertiremo con voi ad utilizzarlo in una simulazione che partendo dalla Vision di un prodotto ci consentirà di mappare i bisogni di un numero selezionato di utenti su un insieme di funzionalità organizzate in una mappa.
Inoltre vedremo come sia possibile utilizzare questo strumento per gestire le diverse release di un prodotto a partire dal così detto “Walking Skeleton” fino alle successive MMF (Mininum Markatable Feature)
Sapete cos’è il modello di Kano, FURPS+, o come il nome della capitale della Russia possa essere utilizzato per assegnare priorità alle diverse storie? Se vi abbiamo incuriosito, o se pensate che avere un nuovo strumento mentale da aggiungere alla vostra cassetta degli attrezzi potrebbe esservi utile, partecipate. Sarete certamente i benvenuti.
This document provides an overview of Agile software development. It begins by defining Agile as a project management process that encourages frequent inspection and adaptation. It then discusses some common Agile practices like Scrum and eXtreme Programming. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change. Finally, it provides advice for different roles on how Agile can benefit them and their work.
Growth hacking is the combined efforts of product, engineering, marketing and data science teams to achieve growth goals. The document discusses how a growth team at VivaReal can experiment and validate hypotheses faster by acting more independently from other teams. It proposes injecting code via a third-party JavaScript to run A/B tests without approvals or changing the main codebase. This would allow experiments to be deployed in seconds through an external API and give the growth team freedom to try new ideas.
Andrew Gassen, CEO | Pivotal Software
0 for 3: Edtech Startup Lessons Learned
I’ve been a part of 3 different education technology companies, all focused on the K-12 market. Each of these companies failed, but each for different reasons and in spectacularly different ways. This talk is a bit of a public post-mortem that focuses on 3 key lessons from each company, including a brief discussion on how we might have done things a different way if I knew then what I know now.
Presented by the
Serious Play Conference
seriousplayconf.com
at
Orlando,
University of Central Florida,
UCF,
July 24-26, 2019
Let's Sharpen Your Agile Ax, It's Story Splitting TimeExcella
No, this is not a well-formed acceptance criterion because it is not a present tense indicative statement that can be clearly determined as true or false. It does not provide enough information to determine if the requirement has been met.
This document discusses splitting large user stories into smaller tasks. It begins with an introduction and outline. It then covers topics like the types of issues teams track like user stories and tasks. The document emphasizes that user stories represent value to customers, while tasks represent work. It also discusses other artifacts like epics, technical stories, and information that doesn't belong in user stories. The presentation concludes with a review of key points and the definition of ready.
Can a team with 3 software developers build a “tailored” product in a few months and replace an enterprise solution that no longer fully satisfies business needs?
In this talk I will tell you how we managed to put a first working version of the new product into production in a few months, combining a strong desire for simplicity, good technical practices, and a lean approach.
At the end of the talk, you will understand that collaboration, feedback, and a process to support the product make any kind of goal achievable!
Mobile App Feature Configuration and A/B Experimentslacyrhoades
The document discusses feature configuration and A/B testing in mobile apps. It describes how Etsy uses feature flags and continuous experimentation to iteratively develop and test new features. Features can be enabled or disabled for certain users or groups. Experiments follow a process of setting up a feature flag, determining user eligibility, coding the feature, internal testing, then launching the feature to a percentage of users while collecting analytics. This allows gathering feedback to improve products and user experience.
This document discusses the principles of Lean UX. It begins with an introduction to where Lean UX comes from and its relationship to agile development. The core Lean UX process is then described as a cycle of stating desired outcomes, declaring assumptions, hypothesizing tests, designing experiments, making MVPs, getting feedback, and repeating. Key characteristics of Lean UX like small cross-functional teams and a bias towards making things to learn are also outlined. The document then dives deeper into how to approach continuous learning, writing assumptions and hypotheses, enabling making through MVPs, managing outcomes rather than outputs, and creating an organizational structure to support Lean UX.
We know the world changes and, in order to be competitive, so must your software. That’s why we invented continuous validation.
In this presentation we discuss how we came to the conclusion that continuous validation is urgently needed, where and when it should take place and how it works.
We think there is no need to have a discrepancy between building the right things and doing this the right way at the same time.
The document discusses the three pillars of continuous delivery as culture, practices, and tooling. It states that culture is expressed through practices which are carried out using tools. However, when first starting a continuous delivery program, it is better to focus on practices and tools first before culture in order to get quick wins. Implementing practices and tools can help bootstrap a culture over time through communicating successes. The document provides examples of practices and tools as well as tips for getting started with continuous delivery.
The document discusses the concept of good performance from a customer's perspective. It summarizes that customer perception of application performance is determined by the product's usability, scalability, robustness, and support/supportability. The document then breaks down usability into more specific factors that impact customer experience, such as embarrassment over slow operations, intuitiveness of the user interface, and frustration over simple problems not being addressed. It stresses that performance must be evaluated from the viewpoint of the end user and application administrator.
Devops, The future is here, it's just not evenly distributedKris Buytaert
Devops aims to break down barriers between development and operations teams through principles like continuous integration, automation, shared infrastructure access, and cross-functional teams. It advocates automating processes from building to deploying to testing in order to enable continuous delivery of new features in a secure and reliable manner. This helps improve communication between teams and allows organizations to get features to users faster while increasing stability, security, and customer satisfaction. Achieving devops culture and practices requires patience, improving collaboration, building trust between teams, and automating as many processes as possible.
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...MARRIS Consulting
Webinar by Clarke Ching Agile and ToC expert. Agile: the Good, the Bad and the Ugly. If your Agile is broken then this is how to fix it!
Your Agile teams are busy. Busy delivering. Busy improving. Your quality is amazing. Rework is low. The product looks great. Your users love it. You are a high performing team!
But your internal customers say your teams are slow. This session will teach you how to use the Theory of Constraints to figure out how to speed up, by finding the one thing that’s slowing them down.
This webinar will cover how, in an Agile environment:
- to better control scope creep,
- to reinforce your relationship with the I.T. Development team’s client,
- to be able to make commitments and honour them and
- to decide where your bottleneck should be.
About the speaker
Clarke Ching is a computer scientist with an MBA who discovered Goldratt’s Theory of Constraints (ToC) in 2003 and has been using it ever since to accelerate Agile initiatives. He is fascinated by Agile and obsessed with ToC.
He wrote the amazon best-sellers Rolling Rocks Downhill and The Bottleneck Rules. Rolling Rocks Downhill teaches 3 things: the fundamentals of Agile combined with ToC; how to use those fundamentals to deliver big projects faster and on time; and how to deliver quietly huge transformations. It’s been featured in The Guardian newspaper and The Spectator magazine. It was one of Barbara Oakley’s top 10 books of 2019. It was the #2 best-selling Leadership book on amazon.com, just behind Steven Covey’s 7-habits book.
He has been Agile / Lean / ToC expert in: GE Energy, Dell, Royal London (life insurance & pensions), Gazprom and Standard Life Aberdeen among other organizations. He is the past Chairperson of Agile Scotland. He is a lecturer at Victoria University School Of Management in New Zealand where he now lives.
Today he is the founder and Chief Productivity Officer of Odd Socks Consulting
How To Do Kick-Ass Software Development, by Sven PetersZeroTurnaround
The document discusses how to do kick-ass software development through agile practices like using Java, improving as a team, collaborating well, automating tasks, and building a kick-ass culture. It emphasizes delivering high quality software quickly through a co-located team with simple workflows, chat for communication, continuous integration, handling flaky tests, and deploying with a single button press. The overall message is that focusing on developer happiness, customer satisfaction, and continual improvement will result in kick-ass software development.
OSMC 2015 | Testing in Production by Devdas BhagatNETWAYS
The document discusses various topics related to software testing and development including testing environments vs reality, risk management approaches, monitoring software usage through event processing and generating alerts. It notes that testing environments often differ significantly from production with unstable conditions, humans and latency. Two approaches to risk management are described: narrowly scoping problems and extensive testing vs rapid iteration, testing changes in real world, and only keeping what works. Event processing and monitoring tools can provide real-time insights into software usage and changes.
OSMC 2015: Testing in Production by Devdas BhagatNETWAYS
For most ecommerce companies, software is not the final deliverable product. It is a research tool, to determine what customers will pay for. To be able to get good data from software, monitoring and analytics must be built into the system. Alerting must come from business requirements and be based on application generated data.
In the traditional operations world, we monitor what is easy, and avoid monitoring that which is difficult. This talk is an attempt to show people that monitoring must be driven by metrics from the CxO office, and then potentially involve technical metrics if needed.
This talk explains why functional and business level monitoring is crucial. We also cover the tradeoffs from a DTAP model to continuous deployment. There will be a brief introduction to a couple of useful monitoring tools for functional monitoring. No special technical skills are expected of the audience, but having a general overview of the monitoring world is a good thing. This talk is not limited to ecommerce companies, but is most applicable to that environment.
Collaboration and Productivity: The Missing Links in API DevelopmentPostman
The document discusses collaboration in API development. It notes that APIs are currently developed with limited context and human factors, leading to inefficiencies. The solution proposed is collaboration through Postman workspaces, which allow for shared contexts, visible activity logs, separation of duties, and clear communication to improve API development.
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
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.
More Related Content
Similar to Building a site for people with big imaginations
Devops aims to break down silos between development and operations teams through culture, automation, and continuous integration/delivery. It emphasizes collaboration and automation to allow code to be deployed safely and quickly. Security should be integrated into the devops pipeline through practices like automated security testing on each code change and configuration management to standardize security across environments. Adopting devops and continuous delivery helps improve security by reducing risk through faster issue remediation and increased visibility into systems.
User Story Mapping - mini iad 2014 (Armani, Rodriguez)Fabio Armani
Riteniamo, che non vi sia dubbio sul fatto le User Story (introdotte da eXtreme Programming) e il Product Backlog (definito in Scrum) rappresentino due portentosi strumenti per la gestione agile dei requisiti e delle specifiche sia funzionali che non funzionali. Ma … hanno alcuni limiti.
Ad esempio, nonostante le notevoli caratteristiche del Product Backlog, la sua unidimensionalità non consente di creare un modello dei requisiti adatto a scalare e che consenta di gestire le dipendenze che possono essere presenti tra i vari elementi che lo costituiscono.
In questo workshop presenteremo e utilizzeremo un altro potente strumento che spesso utilizziamo durante gli User Story Workshop sia in fase d’Inception, sia all’inizio di ogni nuova release di un prodotto. Si chiama “User Story Mapping”.
Ci divertiremo con voi ad utilizzarlo in una simulazione che partendo dalla Vision di un prodotto ci consentirà di mappare i bisogni di un numero selezionato di utenti su un insieme di funzionalità organizzate in una mappa.
Inoltre vedremo come sia possibile utilizzare questo strumento per gestire le diverse release di un prodotto a partire dal così detto “Walking Skeleton” fino alle successive MMF (Mininum Markatable Feature)
Sapete cos’è il modello di Kano, FURPS+, o come il nome della capitale della Russia possa essere utilizzato per assegnare priorità alle diverse storie? Se vi abbiamo incuriosito, o se pensate che avere un nuovo strumento mentale da aggiungere alla vostra cassetta degli attrezzi potrebbe esservi utile, partecipate. Sarete certamente i benvenuti.
This document provides an overview of Agile software development. It begins by defining Agile as a project management process that encourages frequent inspection and adaptation. It then discusses some common Agile practices like Scrum and eXtreme Programming. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change. Finally, it provides advice for different roles on how Agile can benefit them and their work.
Growth hacking is the combined efforts of product, engineering, marketing and data science teams to achieve growth goals. The document discusses how a growth team at VivaReal can experiment and validate hypotheses faster by acting more independently from other teams. It proposes injecting code via a third-party JavaScript to run A/B tests without approvals or changing the main codebase. This would allow experiments to be deployed in seconds through an external API and give the growth team freedom to try new ideas.
Andrew Gassen, CEO | Pivotal Software
0 for 3: Edtech Startup Lessons Learned
I’ve been a part of 3 different education technology companies, all focused on the K-12 market. Each of these companies failed, but each for different reasons and in spectacularly different ways. This talk is a bit of a public post-mortem that focuses on 3 key lessons from each company, including a brief discussion on how we might have done things a different way if I knew then what I know now.
Presented by the
Serious Play Conference
seriousplayconf.com
at
Orlando,
University of Central Florida,
UCF,
July 24-26, 2019
Let's Sharpen Your Agile Ax, It's Story Splitting TimeExcella
No, this is not a well-formed acceptance criterion because it is not a present tense indicative statement that can be clearly determined as true or false. It does not provide enough information to determine if the requirement has been met.
This document discusses splitting large user stories into smaller tasks. It begins with an introduction and outline. It then covers topics like the types of issues teams track like user stories and tasks. The document emphasizes that user stories represent value to customers, while tasks represent work. It also discusses other artifacts like epics, technical stories, and information that doesn't belong in user stories. The presentation concludes with a review of key points and the definition of ready.
Can a team with 3 software developers build a “tailored” product in a few months and replace an enterprise solution that no longer fully satisfies business needs?
In this talk I will tell you how we managed to put a first working version of the new product into production in a few months, combining a strong desire for simplicity, good technical practices, and a lean approach.
At the end of the talk, you will understand that collaboration, feedback, and a process to support the product make any kind of goal achievable!
Mobile App Feature Configuration and A/B Experimentslacyrhoades
The document discusses feature configuration and A/B testing in mobile apps. It describes how Etsy uses feature flags and continuous experimentation to iteratively develop and test new features. Features can be enabled or disabled for certain users or groups. Experiments follow a process of setting up a feature flag, determining user eligibility, coding the feature, internal testing, then launching the feature to a percentage of users while collecting analytics. This allows gathering feedback to improve products and user experience.
This document discusses the principles of Lean UX. It begins with an introduction to where Lean UX comes from and its relationship to agile development. The core Lean UX process is then described as a cycle of stating desired outcomes, declaring assumptions, hypothesizing tests, designing experiments, making MVPs, getting feedback, and repeating. Key characteristics of Lean UX like small cross-functional teams and a bias towards making things to learn are also outlined. The document then dives deeper into how to approach continuous learning, writing assumptions and hypotheses, enabling making through MVPs, managing outcomes rather than outputs, and creating an organizational structure to support Lean UX.
We know the world changes and, in order to be competitive, so must your software. That’s why we invented continuous validation.
In this presentation we discuss how we came to the conclusion that continuous validation is urgently needed, where and when it should take place and how it works.
We think there is no need to have a discrepancy between building the right things and doing this the right way at the same time.
The document discusses the three pillars of continuous delivery as culture, practices, and tooling. It states that culture is expressed through practices which are carried out using tools. However, when first starting a continuous delivery program, it is better to focus on practices and tools first before culture in order to get quick wins. Implementing practices and tools can help bootstrap a culture over time through communicating successes. The document provides examples of practices and tools as well as tips for getting started with continuous delivery.
The document discusses the concept of good performance from a customer's perspective. It summarizes that customer perception of application performance is determined by the product's usability, scalability, robustness, and support/supportability. The document then breaks down usability into more specific factors that impact customer experience, such as embarrassment over slow operations, intuitiveness of the user interface, and frustration over simple problems not being addressed. It stresses that performance must be evaluated from the viewpoint of the end user and application administrator.
Devops, The future is here, it's just not evenly distributedKris Buytaert
Devops aims to break down barriers between development and operations teams through principles like continuous integration, automation, shared infrastructure access, and cross-functional teams. It advocates automating processes from building to deploying to testing in order to enable continuous delivery of new features in a secure and reliable manner. This helps improve communication between teams and allows organizations to get features to users faster while increasing stability, security, and customer satisfaction. Achieving devops culture and practices requires patience, improving collaboration, building trust between teams, and automating as many processes as possible.
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...MARRIS Consulting
Webinar by Clarke Ching Agile and ToC expert. Agile: the Good, the Bad and the Ugly. If your Agile is broken then this is how to fix it!
Your Agile teams are busy. Busy delivering. Busy improving. Your quality is amazing. Rework is low. The product looks great. Your users love it. You are a high performing team!
But your internal customers say your teams are slow. This session will teach you how to use the Theory of Constraints to figure out how to speed up, by finding the one thing that’s slowing them down.
This webinar will cover how, in an Agile environment:
- to better control scope creep,
- to reinforce your relationship with the I.T. Development team’s client,
- to be able to make commitments and honour them and
- to decide where your bottleneck should be.
About the speaker
Clarke Ching is a computer scientist with an MBA who discovered Goldratt’s Theory of Constraints (ToC) in 2003 and has been using it ever since to accelerate Agile initiatives. He is fascinated by Agile and obsessed with ToC.
He wrote the amazon best-sellers Rolling Rocks Downhill and The Bottleneck Rules. Rolling Rocks Downhill teaches 3 things: the fundamentals of Agile combined with ToC; how to use those fundamentals to deliver big projects faster and on time; and how to deliver quietly huge transformations. It’s been featured in The Guardian newspaper and The Spectator magazine. It was one of Barbara Oakley’s top 10 books of 2019. It was the #2 best-selling Leadership book on amazon.com, just behind Steven Covey’s 7-habits book.
He has been Agile / Lean / ToC expert in: GE Energy, Dell, Royal London (life insurance & pensions), Gazprom and Standard Life Aberdeen among other organizations. He is the past Chairperson of Agile Scotland. He is a lecturer at Victoria University School Of Management in New Zealand where he now lives.
Today he is the founder and Chief Productivity Officer of Odd Socks Consulting
How To Do Kick-Ass Software Development, by Sven PetersZeroTurnaround
The document discusses how to do kick-ass software development through agile practices like using Java, improving as a team, collaborating well, automating tasks, and building a kick-ass culture. It emphasizes delivering high quality software quickly through a co-located team with simple workflows, chat for communication, continuous integration, handling flaky tests, and deploying with a single button press. The overall message is that focusing on developer happiness, customer satisfaction, and continual improvement will result in kick-ass software development.
OSMC 2015 | Testing in Production by Devdas BhagatNETWAYS
The document discusses various topics related to software testing and development including testing environments vs reality, risk management approaches, monitoring software usage through event processing and generating alerts. It notes that testing environments often differ significantly from production with unstable conditions, humans and latency. Two approaches to risk management are described: narrowly scoping problems and extensive testing vs rapid iteration, testing changes in real world, and only keeping what works. Event processing and monitoring tools can provide real-time insights into software usage and changes.
OSMC 2015: Testing in Production by Devdas BhagatNETWAYS
For most ecommerce companies, software is not the final deliverable product. It is a research tool, to determine what customers will pay for. To be able to get good data from software, monitoring and analytics must be built into the system. Alerting must come from business requirements and be based on application generated data.
In the traditional operations world, we monitor what is easy, and avoid monitoring that which is difficult. This talk is an attempt to show people that monitoring must be driven by metrics from the CxO office, and then potentially involve technical metrics if needed.
This talk explains why functional and business level monitoring is crucial. We also cover the tradeoffs from a DTAP model to continuous deployment. There will be a brief introduction to a couple of useful monitoring tools for functional monitoring. No special technical skills are expected of the audience, but having a general overview of the monitoring world is a good thing. This talk is not limited to ecommerce companies, but is most applicable to that environment.
Collaboration and Productivity: The Missing Links in API DevelopmentPostman
The document discusses collaboration in API development. It notes that APIs are currently developed with limited context and human factors, leading to inefficiencies. The solution proposed is collaboration through Postman workspaces, which allow for shared contexts, visible activity logs, separation of duties, and clear communication to improve API development.
Similar to Building a site for people with big imaginations (20)
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
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.
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
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.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Infrastructure Challenges in Scaling RAG with Custom AI modelsZilliz
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
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.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
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.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdfTechgropse Pvt.Ltd.
In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.
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!
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
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
4. How hard can it be to build
a web app?
Did not have a shippable product
Code was over engineered
Features were over specified
Too much administration
23. Development Tools
Version Control System - Subversion - UNDO + many programmers
Automation tools - rake, shell scripts, make, ant, Capistrano - reduce chances of things
going wrong
Database Refactoring - Rails migrations, LiquidBase
24. Development Tools
Version Control System
Version Control System - Subversion - UNDO + many programmers
Automation tools - rake, shell scripts, make, ant, Capistrano - reduce chances of things
going wrong
Database Refactoring - Rails migrations, LiquidBase
25. Development Tools
Version Control System
Automation tools
Version Control System - Subversion - UNDO + many programmers
Automation tools - rake, shell scripts, make, ant, Capistrano - reduce chances of things
going wrong
Database Refactoring - Rails migrations, LiquidBase
26. Development Tools
Version Control System
Automation tools
Database Refactoring
Version Control System - Subversion - UNDO + many programmers
Automation tools - rake, shell scripts, make, ant, Capistrano - reduce chances of things
going wrong
Database Refactoring - Rails migrations, LiquidBase
27. Testing Tools
Always in maintenance mode
tests automate the vefication process
tests make you brave (to change your code)
Tests must pass before checking in
save embarrasement
28. Testing Tools
Unit testing
Always in maintenance mode
tests automate the vefication process
tests make you brave (to change your code)
Tests must pass before checking in
save embarrasement
29. Testing Tools
Unit testing
Functional testing
Always in maintenance mode
tests automate the vefication process
tests make you brave (to change your code)
Tests must pass before checking in
save embarrasement
30. Testing Tools
Unit testing
Functional testing
Continuous Integration
Always in maintenance mode
tests automate the vefication process
tests make you brave (to change your code)
Tests must pass before checking in
save embarrasement
35. What is a story?
Features, fixes or nonfunctional requirements
As an <actor> <action>
i.e. As a User I can view my account balance
i.e. As an Administrator I can delete a user
Not over specified
Estimated (1 hours -> 16 hours @ RB, but 1-21 days at other places)
36. What is a story?
Features, fixes or nonfunctional requirements
As an <actor> <action>
i.e. As a User I can view my account balance
i.e. As an Administrator I can delete a user
Not over specified
Estimated (1 hours -> 16 hours @ RB, but 1-21 days at other places)
37. What is a story?
Features, fixes or nonfunctional requirements
As an <actor> <action>
i.e. As a User I can view my account balance
i.e. As an Administrator I can delete a user
Not over specified
Estimated (1 hours -> 16 hours @ RB, but 1-21 days at other places)
38. What is a story?
Features, fixes or nonfunctional requirements
As an <actor> <action>
i.e. As a User I can view my account balance
i.e. As an Administrator I can delete a user
Not over specified
Estimated (1 hours -> 16 hours @ RB, but 1-21 days at other places)
39. What is a story?
Features, fixes or nonfunctional requirements
As an <actor> <action>
i.e. As a User I can view my account balance
i.e. As an Administrator I can delete a user
Not over specified
Estimated (1 hours -> 16 hours @ RB, but 1-21 days at other places)
40. Management - Story Board
Story Board - what we are doing this week
•
Purpose: it is a communication tool - not just for the team but for anyone who is
interested.
•
It does not have all the details - see issue tracker or talk to customer
•
3 columns - todo, doing, done
•
all items start in todo and are order, in priority, from top to bottom
•
when someone picks a story, they move it to ‘doing’ and put their avatar next to it
41. Management - Story Board
Story Board - what we are doing this week
•
Purpose: it is a communication tool - not just for the team but for anyone who is
interested.
•
It does not have all the details - see issue tracker or talk to customer
•
3 columns - todo, doing, done
•
all items start in todo and are order, in priority, from top to bottom
•
when someone picks a story, they move it to ‘doing’ and put their avatar next to it
42. Management - Story Board
Story Board - what we are doing this week
•
Purpose: it is a communication tool - not just for the team but for anyone who is
interested.
•
It does not have all the details - see issue tracker or talk to customer
•
3 columns - todo, doing, done
•
all items start in todo and are order, in priority, from top to bottom
•
when someone picks a story, they move it to ‘doing’ and put their avatar next to it
43. Management - Story Board
Story Board - what we are doing this week
•
Purpose: it is a communication tool - not just for the team but for anyone who is
interested.
•
It does not have all the details - see issue tracker or talk to customer
•
3 columns - todo, doing, done
•
all items start in todo and are order, in priority, from top to bottom
•
when someone picks a story, they move it to ‘doing’ and put their avatar next to it
44. Management - Story Board
Story Board - what we are doing this week
•
Purpose: it is a communication tool - not just for the team but for anyone who is
interested.
•
It does not have all the details - see issue tracker or talk to customer
•
3 columns - todo, doing, done
•
all items start in todo and are order, in priority, from top to bottom
•
when someone picks a story, they move it to ‘doing’ and put their avatar next to it
45. Management - Story Board
Story Board - what we are doing this week
•
Purpose: it is a communication tool - not just for the team but for anyone who is
interested.
•
It does not have all the details - see issue tracker or talk to customer
•
3 columns - todo, doing, done
•
all items start in todo and are order, in priority, from top to bottom
•
when someone picks a story, they move it to ‘doing’ and put their avatar next to it
46. Management - Story Board
Story Board - what we are doing this week
•
Purpose: it is a communication tool - not just for the team but for anyone who is
interested.
•
It does not have all the details - see issue tracker or talk to customer
•
3 columns - todo, doing, done
•
all items start in todo and are order, in priority, from top to bottom
•
when someone picks a story, they move it to ‘doing’ and put their avatar next to it
47. Management - Story Board
Story Board - what we are doing this week
•
Purpose: it is a communication tool - not just for the team but for anyone who is
interested.
•
It does not have all the details - see issue tracker or talk to customer
•
3 columns - todo, doing, done
•
all items start in todo and are order, in priority, from top to bottom
•
when someone picks a story, they move it to ‘doing’ and put their avatar next to it
48. 3. Simple Development
Process
KISS
Agile and Iterative - Scrum and XP
Process keeps everyone on the same page
49. 4. Ship it!
If you don’t ship it, it is just an elaborate art project
Ship the simplest thing possible (at first)
*
RB gallery example
*
release early & often - good enough - good enough for your users, for future
maintenance and your piece of mind (PragProg). Like an artist, you need to know when to
stop.
52. RedBubble Practices
1. Good people
There are no rules, there are only guidelines - if it doesn’t help you, then change it!
53. RedBubble Practices
1. Good people
2. Good tools
There are no rules, there are only guidelines - if it doesn’t help you, then change it!
54. RedBubble Practices
1. Good people
2. Good tools
3. Simple Development Process
There are no rules, there are only guidelines - if it doesn’t help you, then change it!
55. RedBubble Practices
1. Good people
2. Good tools
3. Simple Development Process
4. Ship it!
There are no rules, there are only guidelines - if it doesn’t help you, then change it!
56. RedBubble Practices
1. Good people
2. Good tools
3. Simple Development Process
4. Ship it!
5. Have fun
There are no rules, there are only guidelines - if it doesn’t help you, then change it!
57. A week in software
development
An Iteration
Thursday Friday Monday Tuesday Wednesday
Release Standup Standup Standup Early Morning Standup
Kickoff Beverages Code Review Finalize planning Showcase
Start planning next week Close it off
End of iteration Review
Free time
Why do you want a good process?
•
a good process takes the day to day “what do we do now” conversations away so you
can actually get down and do the work
•
Thursday is the start of the week, Wednesday is the end
58. What now?
Try Agile and Iterative Development
Try some new tools
Make a difference
61. Resources
Books
“Pragmatic Programmer” by Hunt and Thomas
“Agile and Iterative Development” by Craig Larman
“A Rational Design Process: How and why to Fake
It.” Clements, P., and Parnas, D
Scrum and XP from the Trenches - Henrik Kniberg
“The Art of the Start” by Guy Kawasaki
“Beautiful Code: Leading Programmers Explain How
They Think”