Agile myth
•
8 likes•4,906 views
Agile methods are often misunderstood to mean no documentation, anarchy, or a simple switch from traditional methods, but Agile in fact emphasizes documentation, collaboration, and iterative improvement to develop software faster while avoiding a "silver bullet" approach.
Report
Share
Report
Share
Download to read offline
Recommended
London Alexa Devs 9th Meetup - Look Who's Talking
The document describes a meetup of the London Alexa Devs group that was held on December 12, 2017. The agenda included discussing recent Alexa news, a talk on enhancing skills for the Echo Show, and networking over drinks. The meetup organizers provided their contact information for anyone interested in giving a future talk. Templates and capabilities for the Echo Show like lists, bodies of text, images, audio/video players were also outlined.
Akka in Action: Heiko Seeburger
Scalable systems make us face challenges like concurrency, distribution, fault tolerance, elasticity, etc. Akka not only steps up to meet these, but it makes writing scalable software particularly easy. We will demo Akka's most important tool, the actor model, using a vivid example and live coding.
Nikki Tirado - the pillars of cloudiness / Unlocked: the Hybrid Cloud 12 May ...
Nikki Tirado is a product trainer at Rackspace Academy. She gave a presentation on the pillars of cloud computing which include:
1. Parallel and modular architecture which allows flexible scaling.
2. Agile development which embraces failure to innovate quickly and reduce time to market.
3. Secure infrastructure to protect customer data and applications.
How to Upgrade Angular 1 to Angular 2 - Piece by Piece
The document discusses upgrading from Angular 1 to Angular 2 incrementally. It covers the basics of Angular 1 and Angular 2, including controllers, directives, scopes, services, dependency injection, components, and more. The presentation provides an overview of best practices for upgrading Angular 1 incrementally to Angular 2 and demonstrates the process. It also notes some potential pitfalls and leaves time for questions.
Arduino Introduction (Blinking LED) Presentation (workshop #5)
This Arduino Introduction presentation are the power point slides - see the PDF version for a step by step screenshots of what we showed live during the online workshops.
A workshop as part of series of online workshops, stemmed from an LSTA grant to educate librarians and library school students on makerspaces, especially in academic libraries. October 15, 2014
Agile foundation and agile myths
The document compares predictive and agile software development approaches. It outlines that predictive approaches rely on upfront planning and strict adherence to plans, which can be unrealistic given the inherent uncertainties in software projects. Agile approaches separate estimates from execution, focus on frequent delivery of working software, and emphasize adapting to changes and feedback. While myths exist that agile means no planning, documentation, commitments, processes, or roles like project managers, when applied properly agile can dramatically improve an organization's ability to deliver working software.
Documentation thrives in an agile methodology
This presentation shows agile newbies how to successfully incorporate accurate and complete documentation into the agile process.
Documentation by the Techies, for the Techies; Documentation in Agile
Documentation by the Techies, for the Techies; Documentation in AgileRajeev Jain (Scrum Master, Program Mgr, Technical Writer)
A very unique and first of its kind workshop for Software developers, Testers, Business Analyst, Product/Project managers, Administrators, Architects, and other engineering team members on how to create the internal engineering documents such as:
- Design Documents, Requirement Specifications, User Stories, Epic
- API Guides, Functional Specifications, Porting Guide, Cook Book
- Architecture Docs, ERDs
Duration: 4 hours to 3-Days
Contact: Rajeev-rajeevjain72@gmail.comRecommended
London Alexa Devs 9th Meetup - Look Who's Talking
The document describes a meetup of the London Alexa Devs group that was held on December 12, 2017. The agenda included discussing recent Alexa news, a talk on enhancing skills for the Echo Show, and networking over drinks. The meetup organizers provided their contact information for anyone interested in giving a future talk. Templates and capabilities for the Echo Show like lists, bodies of text, images, audio/video players were also outlined.
Akka in Action: Heiko Seeburger
Scalable systems make us face challenges like concurrency, distribution, fault tolerance, elasticity, etc. Akka not only steps up to meet these, but it makes writing scalable software particularly easy. We will demo Akka's most important tool, the actor model, using a vivid example and live coding.
Nikki Tirado - the pillars of cloudiness / Unlocked: the Hybrid Cloud 12 May ...
Nikki Tirado is a product trainer at Rackspace Academy. She gave a presentation on the pillars of cloud computing which include:
1. Parallel and modular architecture which allows flexible scaling.
2. Agile development which embraces failure to innovate quickly and reduce time to market.
3. Secure infrastructure to protect customer data and applications.
How to Upgrade Angular 1 to Angular 2 - Piece by Piece
The document discusses upgrading from Angular 1 to Angular 2 incrementally. It covers the basics of Angular 1 and Angular 2, including controllers, directives, scopes, services, dependency injection, components, and more. The presentation provides an overview of best practices for upgrading Angular 1 incrementally to Angular 2 and demonstrates the process. It also notes some potential pitfalls and leaves time for questions.
Arduino Introduction (Blinking LED) Presentation (workshop #5)
This Arduino Introduction presentation are the power point slides - see the PDF version for a step by step screenshots of what we showed live during the online workshops.
A workshop as part of series of online workshops, stemmed from an LSTA grant to educate librarians and library school students on makerspaces, especially in academic libraries. October 15, 2014
Agile foundation and agile myths
The document compares predictive and agile software development approaches. It outlines that predictive approaches rely on upfront planning and strict adherence to plans, which can be unrealistic given the inherent uncertainties in software projects. Agile approaches separate estimates from execution, focus on frequent delivery of working software, and emphasize adapting to changes and feedback. While myths exist that agile means no planning, documentation, commitments, processes, or roles like project managers, when applied properly agile can dramatically improve an organization's ability to deliver working software.
Documentation thrives in an agile methodology
This presentation shows agile newbies how to successfully incorporate accurate and complete documentation into the agile process.
Documentation by the Techies, for the Techies; Documentation in Agile
Documentation by the Techies, for the Techies; Documentation in AgileRajeev Jain (Scrum Master, Program Mgr, Technical Writer)
A very unique and first of its kind workshop for Software developers, Testers, Business Analyst, Product/Project managers, Administrators, Architects, and other engineering team members on how to create the internal engineering documents such as:
- Design Documents, Requirement Specifications, User Stories, Epic
- API Guides, Functional Specifications, Porting Guide, Cook Book
- Architecture Docs, ERDs
Duration: 4 hours to 3-Days
Contact: Rajeev-rajeevjain72@gmail.comProducing Quality Documentation In An Agile Development Environment
The document discusses how technical writers can produce quality documentation in an Agile development environment using Scrum methodology. It provides an overview of Agile and Scrum, including Scrum roles, artifacts, and meetings. It addresses how writers can integrate with Scrum teams, challenges they may face, and advantages of Scrum. The role of documentation managers is also examined, along with potential issues to watch out for and benefits writers can gain from Scrum. Additional resources on the topic are provided.
SIGDOC 2011 - Necessary and Neglected? An Empirical Study of Internal Documen...
SIGDOC 2011 - Necessary and Neglected? An Empirical Study of Internal Documen...Christoph Johann Stettina
Presentation slides for the "Necessary and Neglected? An Empirical Study of Internal Documentation in Agile Software Development Teams" paper presented at SIGDOC 2011Agile documentation
The document discusses agile and lean documentation practices. It notes that the fundamental issue is communication, not documentation. Documentation should be evolutionary and seek feedback regularly. Well-written documentation supports organizational memory but poor for project communication. Documentation should be concise with overviews and roadmaps preferred over details. With high-quality code and tests, less system documentation is needed.
In Search Of An Agile Documentation Process
The document discusses an agile documentation process that focuses on keeping requirements current for developers, maintaining synchronization between documentation and software, and concurrent delivery of software, help, and manuals. This results in reduced design time, fewer bugs reported, and faster development time. The key is communication and teamwork between teams. The process involves a GUI-driven model based on user stories that delivers just enough information just in time, involves both marketing and engineering, and provides a framework for communication while generating necessary artifacts.
Agile And Documentation
The document discusses applying an Agile mindset to documentation processes rather than strictly following Agile methodologies. It emphasizes that Agile values working software over comprehensive documentation, and that documentation should be "fit for purpose" and integrated with the development team. Technical writers on Agile teams participate in daily meetings, interact with engineers, and adapt documentation to the team and culture.
What is 'Just Enough' Documentation in Agile?
There are lots of misconceptions around what Agile says about documentation. One is that Agile has NO Documentation! That brings a smile to a few folks and drives others (like me) crazy! If you’ve read anything about Agile, you’ll hear that what it really preaches is ‘Just In Time’ or ‘Just Enough’ documentation. So what does that mean? Why aim for ‘Just Enough’ and not ‘Perfect’ Documentation? This seminar was presented at the IIBA group.
Want this seminar presented at YOUR organization? just email sally@agiletransformation.com
Today’s Agile Documentation
This document discusses agile documentation practices based on a survey of 57 Symantec information developers. Some key findings include:
- Most information developers have less than one year of agile experience and see benefits of agile like improved schedules and delivering value.
- Frequent deployment and reviews have improved documentation quality by focusing on smaller chunks of work. Remote collaboration remains a challenge.
- Agile practices like daily stand-ups, estimating tasks, and transparent reporting increase motivation and accountability for documentation work.
- Strategies like cross-training, defining "done", tailoring stories to the organization, and using technology help information developers adapt to agile.
Being Agile With Documentation
Agile environments can be both challenging and rewarding places for technical writers. Appropriate documentation is essential to the efficient production, testing, and acceptance of software. One way to be Agile with documentation to evolve it in parallel with the system development — delivering user stories, use cases, UI designs, system tests, manuals, and even online help — with just enough detail, and just in time. Come and explore some ways that you can be Agile with your documentation. This presentation isn't intended to provide a silver bullet solution, but it may give you some ideas beyond those famous (infamous?) 3x5 index cards.
Lean Enterprise - Enabling Innovative Culture
The pace of change is accelerating. Organizations must continually revisit the question, "What businesses are we in, and how can we organize to maximize our long-term potential?"
Barry O’Reilly and Joanne Molesky share actionable insights on how you can innovate at scale, create high performance organization, and lead in the era of disruption.
Gain insights into processes, portfolio and financial management practices, and organizational design and culture that will help you unleash innovation.
Laughing at the workspace
Learn how to get a happier workforce by following the tips in this presentation. Become a better manager and get employees that love their work.
Documentation in the agile software development process
Abandoning any documentation in agile software development is widespread due to a mistaken interpretation of the agile value "working software over comprehensive documentation". Aren't there any forms of documentation in practice which are actually agile?
75 Jahre Stadtkapelle Blumberg
Präsentation vom Festbankett am 12.04.2014 in der Stadthalle in Blumberg.
Your retrospective suck!
This document provides guidance on how to improve retrospective meetings by making them more fun and focusing on system thinking. It recommends three key elements: more fun, system thinking, and an alternative phase model. Specific techniques are suggested such as using metaphors like a soccer game or pirate adventure to structure the retrospective. The power of causal loop diagrams and current reality trees for understanding the system is also discussed. The document advocates applying systems thinking models like the ABIDE model to help participants view their work in the context of complex interactions within the overall system.
Retrospektiven als Change Management Tool
Retrospektiven sind der Kern eines jeden iterativen Prozesses. Sinnvollerweise werden auch Change Management Prozesse iterativ durchgeführt. Deshalb bilden Retrospektiven den idealen Rahmen, um einen solchen Prozess zu starten und zu begleiten.
Why does product_development_suck
A lot of product development projects suck. Most of the time because of a missing purpose and a clear focus on what is really important. Impact Mapping can help to create such a purpose and to focus on the capabilities that are in context with the business goals.
15 Agile Mythen
In dieser Präsentation beschreibe ich 15 agile Mythen. Das ganze wurde an der Agile Bodensee Konferent 2012 präsentiert.
Ale2012 retrospective
The document discusses ways to make retrospectives for agile software development teams more engaging and effective. It suggests adding hypotheses to retrospectives to give them more purpose and focus. Various metaphor-based retrospective formats are presented, like using soccer or cooking terms, to help teams think differently. The key ideas are that retrospectives need purpose and new perspectives to avoid repetition and keep people motivated to work on identified issues.
Retrospectives - The most boring meetings ever
Retrospectives can be the most fun events. In this presentation I give you some ideas what you can do to spice your retrospectives up.
4 grundübel pechakucha
This document identifies the four main evils in (agile) teams as ignorance, fear, laziness, and apathy. It provides photos and definitions for each evil. Contact information is provided for Marc Löffler, the author.
Scrum zombie
A Scrum zombie is somebody attending the various Scrum meetings but don't know about the Scrum values behind it. This short presentation gives some tips, how to help Scrum teams to embrace these values.
Kaboom
This document discusses watermelon reporting and ways to increase transparency in projects. Watermelon reporting occurs when a project's status is inaccurately reported as better than it is when moving up management levels. To address this, the document recommends using transparent project tracking tools like sprint and backlog burndowns visible to all teams. It also describes a real-life example where multiple teams addressed watermelon reporting by visualizing workflows, consolidating backlogs, and creating an agile dashboard for management to see overall project status. Transparency through tools like these can eliminate watermelon reporting according to the document.
More Related Content
Viewers also liked
Producing Quality Documentation In An Agile Development Environment
The document discusses how technical writers can produce quality documentation in an Agile development environment using Scrum methodology. It provides an overview of Agile and Scrum, including Scrum roles, artifacts, and meetings. It addresses how writers can integrate with Scrum teams, challenges they may face, and advantages of Scrum. The role of documentation managers is also examined, along with potential issues to watch out for and benefits writers can gain from Scrum. Additional resources on the topic are provided.
SIGDOC 2011 - Necessary and Neglected? An Empirical Study of Internal Documen...
SIGDOC 2011 - Necessary and Neglected? An Empirical Study of Internal Documen...Christoph Johann Stettina
Presentation slides for the "Necessary and Neglected? An Empirical Study of Internal Documentation in Agile Software Development Teams" paper presented at SIGDOC 2011Agile documentation
The document discusses agile and lean documentation practices. It notes that the fundamental issue is communication, not documentation. Documentation should be evolutionary and seek feedback regularly. Well-written documentation supports organizational memory but poor for project communication. Documentation should be concise with overviews and roadmaps preferred over details. With high-quality code and tests, less system documentation is needed.
In Search Of An Agile Documentation Process
The document discusses an agile documentation process that focuses on keeping requirements current for developers, maintaining synchronization between documentation and software, and concurrent delivery of software, help, and manuals. This results in reduced design time, fewer bugs reported, and faster development time. The key is communication and teamwork between teams. The process involves a GUI-driven model based on user stories that delivers just enough information just in time, involves both marketing and engineering, and provides a framework for communication while generating necessary artifacts.
Agile And Documentation
The document discusses applying an Agile mindset to documentation processes rather than strictly following Agile methodologies. It emphasizes that Agile values working software over comprehensive documentation, and that documentation should be "fit for purpose" and integrated with the development team. Technical writers on Agile teams participate in daily meetings, interact with engineers, and adapt documentation to the team and culture.
What is 'Just Enough' Documentation in Agile?
There are lots of misconceptions around what Agile says about documentation. One is that Agile has NO Documentation! That brings a smile to a few folks and drives others (like me) crazy! If you’ve read anything about Agile, you’ll hear that what it really preaches is ‘Just In Time’ or ‘Just Enough’ documentation. So what does that mean? Why aim for ‘Just Enough’ and not ‘Perfect’ Documentation? This seminar was presented at the IIBA group.
Want this seminar presented at YOUR organization? just email sally@agiletransformation.com
Today’s Agile Documentation
This document discusses agile documentation practices based on a survey of 57 Symantec information developers. Some key findings include:
- Most information developers have less than one year of agile experience and see benefits of agile like improved schedules and delivering value.
- Frequent deployment and reviews have improved documentation quality by focusing on smaller chunks of work. Remote collaboration remains a challenge.
- Agile practices like daily stand-ups, estimating tasks, and transparent reporting increase motivation and accountability for documentation work.
- Strategies like cross-training, defining "done", tailoring stories to the organization, and using technology help information developers adapt to agile.
Being Agile With Documentation
Agile environments can be both challenging and rewarding places for technical writers. Appropriate documentation is essential to the efficient production, testing, and acceptance of software. One way to be Agile with documentation to evolve it in parallel with the system development — delivering user stories, use cases, UI designs, system tests, manuals, and even online help — with just enough detail, and just in time. Come and explore some ways that you can be Agile with your documentation. This presentation isn't intended to provide a silver bullet solution, but it may give you some ideas beyond those famous (infamous?) 3x5 index cards.
Lean Enterprise - Enabling Innovative Culture
The pace of change is accelerating. Organizations must continually revisit the question, "What businesses are we in, and how can we organize to maximize our long-term potential?"
Barry O’Reilly and Joanne Molesky share actionable insights on how you can innovate at scale, create high performance organization, and lead in the era of disruption.
Gain insights into processes, portfolio and financial management practices, and organizational design and culture that will help you unleash innovation.
Laughing at the workspace
Learn how to get a happier workforce by following the tips in this presentation. Become a better manager and get employees that love their work.
Documentation in the agile software development process
Abandoning any documentation in agile software development is widespread due to a mistaken interpretation of the agile value "working software over comprehensive documentation". Aren't there any forms of documentation in practice which are actually agile?
Viewers also liked (11)
Producing Quality Documentation In An Agile Development Environment
Producing Quality Documentation In An Agile Development Environment
SIGDOC 2011 - Necessary and Neglected? An Empirical Study of Internal Documen...
SIGDOC 2011 - Necessary and Neglected? An Empirical Study of Internal Documen...
Documentation in the agile software development process
Documentation in the agile software development process
More from Marc Löffler
75 Jahre Stadtkapelle Blumberg
Präsentation vom Festbankett am 12.04.2014 in der Stadthalle in Blumberg.
Your retrospective suck!
This document provides guidance on how to improve retrospective meetings by making them more fun and focusing on system thinking. It recommends three key elements: more fun, system thinking, and an alternative phase model. Specific techniques are suggested such as using metaphors like a soccer game or pirate adventure to structure the retrospective. The power of causal loop diagrams and current reality trees for understanding the system is also discussed. The document advocates applying systems thinking models like the ABIDE model to help participants view their work in the context of complex interactions within the overall system.
Retrospektiven als Change Management Tool
Retrospektiven sind der Kern eines jeden iterativen Prozesses. Sinnvollerweise werden auch Change Management Prozesse iterativ durchgeführt. Deshalb bilden Retrospektiven den idealen Rahmen, um einen solchen Prozess zu starten und zu begleiten.
Why does product_development_suck
A lot of product development projects suck. Most of the time because of a missing purpose and a clear focus on what is really important. Impact Mapping can help to create such a purpose and to focus on the capabilities that are in context with the business goals.
15 Agile Mythen
In dieser Präsentation beschreibe ich 15 agile Mythen. Das ganze wurde an der Agile Bodensee Konferent 2012 präsentiert.
Ale2012 retrospective
The document discusses ways to make retrospectives for agile software development teams more engaging and effective. It suggests adding hypotheses to retrospectives to give them more purpose and focus. Various metaphor-based retrospective formats are presented, like using soccer or cooking terms, to help teams think differently. The key ideas are that retrospectives need purpose and new perspectives to avoid repetition and keep people motivated to work on identified issues.
Retrospectives - The most boring meetings ever
Retrospectives can be the most fun events. In this presentation I give you some ideas what you can do to spice your retrospectives up.
4 grundübel pechakucha
This document identifies the four main evils in (agile) teams as ignorance, fear, laziness, and apathy. It provides photos and definitions for each evil. Contact information is provided for Marc Löffler, the author.
Scrum zombie
A Scrum zombie is somebody attending the various Scrum meetings but don't know about the Scrum values behind it. This short presentation gives some tips, how to help Scrum teams to embrace these values.
Kaboom
This document discusses watermelon reporting and ways to increase transparency in projects. Watermelon reporting occurs when a project's status is inaccurately reported as better than it is when moving up management levels. To address this, the document recommends using transparent project tracking tools like sprint and backlog burndowns visible to all teams. It also describes a real-life example where multiple teams addressed watermelon reporting by visualizing workflows, consolidating backlogs, and creating an agile dashboard for management to see overall project status. Transparency through tools like these can eliminate watermelon reporting according to the document.
Scrum zombie
Sei doch kein Scrum Zombie. Wie kann man verhindern, dass man ein Scrum-Team aus lauter Zombies hat?
Howtodefendagainstthe10thingsthatdrivesscrummasterscrazy slideshare
How to defend against the 10 things that drive ScrumMasters crazy. Learn about the four evil root causes and how to overcome them.
Howtodefendagainstthe10thingsthatdrivesscrummasterscrazy
The document discusses 10 things that can drive a ScrumMaster crazy: 1) Doing tasks outside the sprint backlog, 2) Hiding impediments, 3) Not communicating with the product owner during sprints, 4) Ignoring the definition of done, 5) Claiming to have no work assigned when tasks remain open, 6) Last-minute sprint review preparation, 7) Not splitting large tasks, 8) Chronic tardiness, 9) Constantly asking what to work on next, and 10) Distracting meetings. The root causes are identified as fear, laziness, complacency, and apathy. Suggestions to address these issues include teaching the Scrum process, getting commitment from team members, and
7 things to sabotage an agile coach camp
The document lists 7 things that could sabotage an Agile coaching camp, including not proposing topics for open space sessions, ignoring the facilitator, disturbing sessions with unrelated questions, refusing to participate in games, talking loudly on a mobile phone, leaving abruptly, and refusing to talk at all. The purpose seems to be highlighting counterproductive behaviors that would disrupt an Agile coaching event.
10 Things To Drive Your Scrum Master Crazy
This document lists 10 things that can frustrate a ScrumMaster, including doing tasks outside the sprint backlog, hiding impediments, not communicating with the product owner during sprints, ignoring definitions of done, claiming to have nothing to do when the sprint backlog is not complete, last minute preparation for sprint reviews, not splitting large tasks, chronic tardiness, constantly asking what task to do next, and disrupting scrum meetings. The document is authored by Marc Löffler, a certified scrum professional and agile coach.
More from Marc Löffler (16)
Howtodefendagainstthe10thingsthatdrivesscrummasterscrazy slideshare
Howtodefendagainstthe10thingsthatdrivesscrummasterscrazy slideshare
Howtodefendagainstthe10thingsthatdrivesscrummasterscrazy
Howtodefendagainstthe10thingsthatdrivesscrummasterscrazy
Recently uploaded
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Infrastructure Challenges in Scaling RAG with Custom AI models
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.
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
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.
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Essentials of Automations: The Art of Triggers and Actions in FME
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!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
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.
Video Streaming: Then, Now, and in the Future
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.
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Recently uploaded (20)
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Agile myth
- 1. Agile Myths
- 2. Agile = no documentation
- 5. Agile = Silver Bullet
- 6. Agile = Simple Switch
- 7. Agile = Easy
- 8. Agile = Software Development