Introduction to agile documentation
•
1 like•925 views
This document introduces agile documentation. It discusses that agile documentation focuses on delivering value to customers over rigid guidelines. Documentation should occur when necessary and adapt to changes. The document recommends documenting technical and functional views before, during, and after a project for purposes like architecture diagrams, user stories, and code as documentation. It also discusses tools like AsciiDoc and JBake for documentation.
Report
Share
Report
Share
Download to read offline
Recommended
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.
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.
Lightweight Documentation
This document summarizes a presentation about using lightweight documentation approaches in agile software development. It discusses how traditional software development life cycle (SDLC) phases involve detailed documentation, while agile practices emphasize lightweight documentation like product visions, user stories, and wikis. Best practices for agile documentation are presented, like using executable specifications, documenting stable elements, and generating system documentation through reverse engineering. The document concludes with exercises for groups to discuss improving documentation topics and writing reader-focused stories.
Documentation in the Agile Space
This document discusses agile documentation practices. It outlines the Agile Manifesto values of individuals, interactions, working software, and responding to change over processes, tools, comprehensive documentation, contracts, and plans. It describes formal documentation required by stakeholders and informal documentation for development teams. Examples of each are provided. Methods for formal documentation include documents, email, and calls, while informal uses wikis, messaging, and conferencing. The document concludes that agile documentation should start conversations, be lightweight, capture customer requirements, and be open to change.
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.
Establishing documentation delivery as a practice in Agile
In this fast growing and closely connected industry, being Agile is an advantage for vendors providing technical documentation services. This document explains six simple techniques with which you can establish documentation delivery as a practice in Agile. It also includes a comprehensive checklist for Agile Technical Writers. It also answers five prominent questions normally asked by Technical communicators.
The Art of Agile Documentation
A Sense-making workshop to simplify valuable documentation and reduce wasteful documentation.
Myth: “Agile teams don’t document.”
Truth: Agile teams produce excellent and valuable documentation.
Agile Engineering practices have revolutionized the ways in which documentation is treated and produced. In high-stakes environments with heavy compliance and audit requirements, a tendency toward exhaustive documentation is dangerously common. This workshop provides direct guidance and simple tools to help a document-heavy workplace think differently about documentation.
I have developed this workshop to help an organization reframe their understanding of documentation with respect to knowledge work in complex environments so that they may eliminate unnecessary artifacts and simplify/automate others.
David Sabine
The role of the architect in agile
In Agile development, architects still play an important role by setting constraints and principles to provide guidance and boundaries for development teams. While Agile values working software over documentation, architects can document architecture decisions and provide guidance through code examples. On Agile teams, the architect acts as an owner who facilitates architectural decisions, explores new technologies, and evolves the architecture over time based on learnings. The architect also helps align development across teams when needed.
Recommended
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.
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.
Lightweight Documentation
This document summarizes a presentation about using lightweight documentation approaches in agile software development. It discusses how traditional software development life cycle (SDLC) phases involve detailed documentation, while agile practices emphasize lightweight documentation like product visions, user stories, and wikis. Best practices for agile documentation are presented, like using executable specifications, documenting stable elements, and generating system documentation through reverse engineering. The document concludes with exercises for groups to discuss improving documentation topics and writing reader-focused stories.
Documentation in the Agile Space
This document discusses agile documentation practices. It outlines the Agile Manifesto values of individuals, interactions, working software, and responding to change over processes, tools, comprehensive documentation, contracts, and plans. It describes formal documentation required by stakeholders and informal documentation for development teams. Examples of each are provided. Methods for formal documentation include documents, email, and calls, while informal uses wikis, messaging, and conferencing. The document concludes that agile documentation should start conversations, be lightweight, capture customer requirements, and be open to change.
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.
Establishing documentation delivery as a practice in Agile
In this fast growing and closely connected industry, being Agile is an advantage for vendors providing technical documentation services. This document explains six simple techniques with which you can establish documentation delivery as a practice in Agile. It also includes a comprehensive checklist for Agile Technical Writers. It also answers five prominent questions normally asked by Technical communicators.
The Art of Agile Documentation
A Sense-making workshop to simplify valuable documentation and reduce wasteful documentation.
Myth: “Agile teams don’t document.”
Truth: Agile teams produce excellent and valuable documentation.
Agile Engineering practices have revolutionized the ways in which documentation is treated and produced. In high-stakes environments with heavy compliance and audit requirements, a tendency toward exhaustive documentation is dangerously common. This workshop provides direct guidance and simple tools to help a document-heavy workplace think differently about documentation.
I have developed this workshop to help an organization reframe their understanding of documentation with respect to knowledge work in complex environments so that they may eliminate unnecessary artifacts and simplify/automate others.
David Sabine
The role of the architect in agile
In Agile development, architects still play an important role by setting constraints and principles to provide guidance and boundaries for development teams. While Agile values working software over documentation, architects can document architecture decisions and provide guidance through code examples. On Agile teams, the architect acts as an owner who facilitates architectural decisions, explores new technologies, and evolves the architecture over time based on learnings. The architect also helps align development across teams when needed.
Strange Bedfellows? Agile and Architecture
The document discusses aligning architecture practices with agile principles and delivery. It proposes that architecture can be viewed as a product in itself when it comes to enterprise and solution architecture. When architecture is the product, it can be delivered using agile practices to provide value early despite uncertainty. The document also discusses how agile principles apply to architecture values around decision quality, strategic alignment and performance. It suggests the relationship between agile and architecture depends on whether architecture is the product or enables information system changes.
Evolving toward Microservices - O’Reilly SACON Keynote
O’Reilly Software Architecture Conference Keynote 4/2016
Evolving toward Microservices
How HomeDepot.com made the switch
Video published at: https://www.oreilly.com/ideas/evolving-toward-microservices-how-home-depot-made-the-transition
Agile Data Architecture
It is quite possible to use Agile techniques for creating and maintaining a data architecture. Doing so will dramatically reduce the risk of failed data warehouse projects. This webinar will give you a quick overview of the benefits and challenges of Agile Data Modeling, Evolutionary Database Design, Agile Modeling, Conformed Dimensions, Bus Matrix, Database Refactoring, and an Agile framework for Agile data projects
From the designers laptop to the users
The document discusses the goals and learnings from a design system mission to enable teams to create straightforward user experiences. It notes that the tension between product and design system goals is healthy. Key learnings include looking at existing products, synthesizing information to move forward, focusing on experiences rather than just components, and building the design system like a product. The document also outlines different models for how a design system can be built and aligned with product roadmaps.
How Intuit is overhauling legacy engineering practices at scale with innersource
Intuit is overhauling their legacy engineering practices by implementing an "innersource" program inspired by open source practices. They established unified guidelines, set teams up for success by appointing trusted committers and defining review SLAs. They are also scaling the effort by establishing technical community leaders and prioritizing foundational capabilities. Getting started involves connecting with leaders, researching standards, identifying model teams, and conducting workshops to teach the new practices. Roles like engineers, product managers, and data analysts are needed, along with tooling like an internal contributions site and rewards program. The benefits include empowered and engaged engineers, decreased wait times, higher quality products, and faster fixes for customers.
Engineering a Design Culture
The document discusses challenges faced by design teams and proposes adopting engineering best practices to improve collaboration, engagement, and productivity. It identifies six challenges design teams often face: designers focusing on individual craft; designing in a vacuum; low perceived productivity when files are shared; lack of open communication; lack of transparency in others' work; and constant hustle with no reflection. To address these, the document recommends practices like partner designing, peer reviews, source file control, regular design standups, show-and-tell sessions, and design retrospectives. The outcomes of implementing these practices on one team included improved collaboration, engagement, and productivity as well as a visibly better culture and morale.
[Education] Bonita Live Tour 2019 - Business Process Automation
One of our customers in Education, Old Dominion University, tells you about their digital transformation: why they were hungry for a BPM solution, how Bonita served up what they were looking for, the results that have left them satisfied, and of course - what’s next!
Agenda:
- Interview of Natalie Metzger & Todd Dergenski from Old Dominion University (Education). Old Dominion has a very large number of students and staff and therefore a large volume of data with a complex matrix organisation. Their digital transformation project lead them to full automation of account requests for better service and user experience.
- Q&A
Heart of agile by Pierre Hervouet
The document discusses the principles of Agile methodology. It begins by describing the Agile Manifesto and its values of prioritizing working software over documentation and customer collaboration over contract negotiation. It then outlines 12 principles of Agile, including early and continuous delivery of valuable software to satisfy customers, welcoming changing requirements, and self-organizing teams. Finally, it notes some potential downsides or "dark sides" to Agile practices, such as an overemphasis on speed over quality or lack of planning.
Designing Exploding Websites (Euro IA 2009)
More and more, online information is scattered over multiple online channels and websites.
At Info.nl, we have translated this development into our model of the Exploding Website. The model describes what strategic steps you need to take to define the right part of the service in the right context. We also redefined our methodology for user experience design based on the vision of the Exploding Website.
UX, DX, DSX: Developers and Data Scientists as Users
More and more companies nowadays are investing heavily in building infrastructure for developers and data scientists. But often, building infrastructure products are treated as pure engineering practices and differentiated from feature products.
I would like to share my experience leading a team at BuzzFeed in building user-centric infrastructure products for our developers and data scientists, and how I integrate and adapt traditional PM techniques for technical products.
Building software for our peers is a double-edged sword. On one hand, our users are technologists themselves and have immense appreciation for well-designed infrastructure and tools. On the other hand, it is very tempting for us as developers to make assumptions about those folks with whom we work closely. When building tools for data scientists, it is especially crucial to keep in mind that they have their own distinct workflows and needs.
Open core summit 2020: Building an Open Source office on a shoestring budget
This is the talk by Intuit's Aliza Carpio and Rocio Montes for OCS 2020. Building an Open Source office on a shoestring budget:
A Guide to Getting Started “on the cheap”
Agile Software development
This document discusses Agile software development and how it differs from the traditional Waterfall model. Some key points covered include the Agile manifesto which values individuals, working software, customer collaboration and responding to change over processes, documentation and plans. It notes that Agile and Waterfall differ in terms of iteration length and the amount of design done before coding begins. Agile focuses on gathering feedback through techniques like test-driven development rather than thinking harder upfront. Financial aspects are also compared, with Agile aimed at early value and cashflow while Waterfall focuses on return on investment.
Introduction to Agile-Scrum
This is the slide I have used for a 2.5 hours long training session conducted as part of Faculty Development Programme for a reputed University in Kerala
San Diego Start Up Month: Rockstar Open Source
This presentation outlines Intuit's open source program, which was started on a small budget with minimal resources. The program was inspired by breaking down open source into achievable steps. It grew Intuit's open source projects fourfold within two years while increasing diversity and contributions from female engineers. The program provided benefits like engineer pride, diversity in projects, and strengthening Intuit's tech brand reputation.
Developer week: An Engineer’s Essential Tool in Agile: Design Thinking
These slides are from Developer Week Global (June 16-17) presentation by Sonia May Patlan and Aliza Carpio.
DrupalCon San Francisco- The State of Drupal as a Web Application & Product ...
This was a DrupalCon SF Session looking at Drupal shops building products via Drupal. Several of these folks have completely left their Drupal services behind and are now running product businesses (ex: MapBox & Pantheon, from Development Seed & Chapter Three).
Prototyping and Scrum
This presentation is about the challenges faced when doing prototypes and to make sure that these prototypes are useful for the developers.
It is about how the prototyping activity fits into the iterative implementation cycles (Scrum Sprints) and how the triangle of UX, development and visual design works together, in particular if external service providers are involved.
Effectively Culturing a Healthy Culture and Workflow - Jeff Pierce - DevOpsD...
The document discusses effective strategies for cultivating a healthy organizational culture and workflow. It recommends adopting personal responsibility by having developers deploy their own code, requiring strong CI/CD tools and rollback plans. It also stresses picking an application architecture philosophy and sticking to it for consistency, making important decisions before emergencies occur, and using existing tools when possible to reduce costs.
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?
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.
Techniques for Gathering Agile Requirements
Presenter: Jon Hodge, Aras
This is a working group session in which we will discuss and demonstrate approaches for interactively building an Agile backlog of requirements with your project team.
More Related Content
What's hot
Strange Bedfellows? Agile and Architecture
The document discusses aligning architecture practices with agile principles and delivery. It proposes that architecture can be viewed as a product in itself when it comes to enterprise and solution architecture. When architecture is the product, it can be delivered using agile practices to provide value early despite uncertainty. The document also discusses how agile principles apply to architecture values around decision quality, strategic alignment and performance. It suggests the relationship between agile and architecture depends on whether architecture is the product or enables information system changes.
Evolving toward Microservices - O’Reilly SACON Keynote
O’Reilly Software Architecture Conference Keynote 4/2016
Evolving toward Microservices
How HomeDepot.com made the switch
Video published at: https://www.oreilly.com/ideas/evolving-toward-microservices-how-home-depot-made-the-transition
Agile Data Architecture
It is quite possible to use Agile techniques for creating and maintaining a data architecture. Doing so will dramatically reduce the risk of failed data warehouse projects. This webinar will give you a quick overview of the benefits and challenges of Agile Data Modeling, Evolutionary Database Design, Agile Modeling, Conformed Dimensions, Bus Matrix, Database Refactoring, and an Agile framework for Agile data projects
From the designers laptop to the users
The document discusses the goals and learnings from a design system mission to enable teams to create straightforward user experiences. It notes that the tension between product and design system goals is healthy. Key learnings include looking at existing products, synthesizing information to move forward, focusing on experiences rather than just components, and building the design system like a product. The document also outlines different models for how a design system can be built and aligned with product roadmaps.
How Intuit is overhauling legacy engineering practices at scale with innersource
Intuit is overhauling their legacy engineering practices by implementing an "innersource" program inspired by open source practices. They established unified guidelines, set teams up for success by appointing trusted committers and defining review SLAs. They are also scaling the effort by establishing technical community leaders and prioritizing foundational capabilities. Getting started involves connecting with leaders, researching standards, identifying model teams, and conducting workshops to teach the new practices. Roles like engineers, product managers, and data analysts are needed, along with tooling like an internal contributions site and rewards program. The benefits include empowered and engaged engineers, decreased wait times, higher quality products, and faster fixes for customers.
Engineering a Design Culture
The document discusses challenges faced by design teams and proposes adopting engineering best practices to improve collaboration, engagement, and productivity. It identifies six challenges design teams often face: designers focusing on individual craft; designing in a vacuum; low perceived productivity when files are shared; lack of open communication; lack of transparency in others' work; and constant hustle with no reflection. To address these, the document recommends practices like partner designing, peer reviews, source file control, regular design standups, show-and-tell sessions, and design retrospectives. The outcomes of implementing these practices on one team included improved collaboration, engagement, and productivity as well as a visibly better culture and morale.
[Education] Bonita Live Tour 2019 - Business Process Automation
One of our customers in Education, Old Dominion University, tells you about their digital transformation: why they were hungry for a BPM solution, how Bonita served up what they were looking for, the results that have left them satisfied, and of course - what’s next!
Agenda:
- Interview of Natalie Metzger & Todd Dergenski from Old Dominion University (Education). Old Dominion has a very large number of students and staff and therefore a large volume of data with a complex matrix organisation. Their digital transformation project lead them to full automation of account requests for better service and user experience.
- Q&A
Heart of agile by Pierre Hervouet
The document discusses the principles of Agile methodology. It begins by describing the Agile Manifesto and its values of prioritizing working software over documentation and customer collaboration over contract negotiation. It then outlines 12 principles of Agile, including early and continuous delivery of valuable software to satisfy customers, welcoming changing requirements, and self-organizing teams. Finally, it notes some potential downsides or "dark sides" to Agile practices, such as an overemphasis on speed over quality or lack of planning.
Designing Exploding Websites (Euro IA 2009)
More and more, online information is scattered over multiple online channels and websites.
At Info.nl, we have translated this development into our model of the Exploding Website. The model describes what strategic steps you need to take to define the right part of the service in the right context. We also redefined our methodology for user experience design based on the vision of the Exploding Website.
UX, DX, DSX: Developers and Data Scientists as Users
More and more companies nowadays are investing heavily in building infrastructure for developers and data scientists. But often, building infrastructure products are treated as pure engineering practices and differentiated from feature products.
I would like to share my experience leading a team at BuzzFeed in building user-centric infrastructure products for our developers and data scientists, and how I integrate and adapt traditional PM techniques for technical products.
Building software for our peers is a double-edged sword. On one hand, our users are technologists themselves and have immense appreciation for well-designed infrastructure and tools. On the other hand, it is very tempting for us as developers to make assumptions about those folks with whom we work closely. When building tools for data scientists, it is especially crucial to keep in mind that they have their own distinct workflows and needs.
Open core summit 2020: Building an Open Source office on a shoestring budget
This is the talk by Intuit's Aliza Carpio and Rocio Montes for OCS 2020. Building an Open Source office on a shoestring budget:
A Guide to Getting Started “on the cheap”
Agile Software development
This document discusses Agile software development and how it differs from the traditional Waterfall model. Some key points covered include the Agile manifesto which values individuals, working software, customer collaboration and responding to change over processes, documentation and plans. It notes that Agile and Waterfall differ in terms of iteration length and the amount of design done before coding begins. Agile focuses on gathering feedback through techniques like test-driven development rather than thinking harder upfront. Financial aspects are also compared, with Agile aimed at early value and cashflow while Waterfall focuses on return on investment.
Introduction to Agile-Scrum
This is the slide I have used for a 2.5 hours long training session conducted as part of Faculty Development Programme for a reputed University in Kerala
San Diego Start Up Month: Rockstar Open Source
This presentation outlines Intuit's open source program, which was started on a small budget with minimal resources. The program was inspired by breaking down open source into achievable steps. It grew Intuit's open source projects fourfold within two years while increasing diversity and contributions from female engineers. The program provided benefits like engineer pride, diversity in projects, and strengthening Intuit's tech brand reputation.
Developer week: An Engineer’s Essential Tool in Agile: Design Thinking
These slides are from Developer Week Global (June 16-17) presentation by Sonia May Patlan and Aliza Carpio.
DrupalCon San Francisco- The State of Drupal as a Web Application & Product ...
This was a DrupalCon SF Session looking at Drupal shops building products via Drupal. Several of these folks have completely left their Drupal services behind and are now running product businesses (ex: MapBox & Pantheon, from Development Seed & Chapter Three).
Prototyping and Scrum
This presentation is about the challenges faced when doing prototypes and to make sure that these prototypes are useful for the developers.
It is about how the prototyping activity fits into the iterative implementation cycles (Scrum Sprints) and how the triangle of UX, development and visual design works together, in particular if external service providers are involved.
Effectively Culturing a Healthy Culture and Workflow - Jeff Pierce - DevOpsD...
The document discusses effective strategies for cultivating a healthy organizational culture and workflow. It recommends adopting personal responsibility by having developers deploy their own code, requiring strong CI/CD tools and rollback plans. It also stresses picking an application architecture philosophy and sticking to it for consistency, making important decisions before emergencies occur, and using existing tools when possible to reduce costs.
What's hot (18)
Evolving toward Microservices - O’Reilly SACON Keynote
Evolving toward Microservices - O’Reilly SACON Keynote
How Intuit is overhauling legacy engineering practices at scale with innersource
How Intuit is overhauling legacy engineering practices at scale with innersource
[Education] Bonita Live Tour 2019 - Business Process Automation
[Education] Bonita Live Tour 2019 - Business Process Automation
UX, DX, DSX: Developers and Data Scientists as Users
UX, DX, DSX: Developers and Data Scientists as Users
Open core summit 2020: Building an Open Source office on a shoestring budget
Open core summit 2020: Building an Open Source office on a shoestring budget
Developer week: An Engineer’s Essential Tool in Agile: Design Thinking
Developer week: An Engineer’s Essential Tool in Agile: Design Thinking
DrupalCon San Francisco- The State of Drupal as a Web Application & Product ...
DrupalCon San Francisco- The State of Drupal as a Web Application & Product ...
Effectively Culturing a Healthy Culture and Workflow - Jeff Pierce - DevOpsD...
Effectively Culturing a Healthy Culture and Workflow - Jeff Pierce - DevOpsD...
Viewers also liked
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?
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.
Techniques for Gathering Agile Requirements
Presenter: Jon Hodge, Aras
This is a working group session in which we will discuss and demonstrate approaches for interactively building an Agile backlog of requirements with your project team.
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.
SharePoint Fest Chicago - Shifting the Paradigm of Requirements Gathering
SharePoint Fest Chicago - Shifting the Paradigm of Requirements GatheringMichelle Caldwell, PSM, SSGB
Are you tired of attending or leading the same old boring requirements-
gathering sessions? Would you like to find a way to get
stakeholders excited about requirements gathering? Then this
session is for you!
Find out how to use collaborative play to build better solution
requirements for SharePoint projects (or any other project for that
matter). You will learn fun ways to do work–seriously! Learn how
to tap into true innovation and uncover hidden business requirements.
What are you waiting for? Come to this session and learn
how to put these tools into action!
You will be able to:
Introduce new and field-tested concepts for creating a clear and compelling vision for SharePoint
Facilitate more effective requirements-gathering sessions
Identify and avoid five problem patterns that plague many project teams
Hit the ground running with new templates that you can use to facilitate your own innovation games
Refine requirements down to measurable business value, and map to strategic business goals using the "rainbow" techniqueContent Experience Modeling: Designing Customer Value and Consistency
Full-day workshop presented at 2104 STC Summit
Are you working with many products, large content sets, many audiences, or broad business requirements? Are you finding it difficult to create a content experience to your customers that is consistent and enables logical, meaningful content access? And do you strive to deliver high value and delight? In addition, do you need to develop robust content experiences that stand the test of time, even if the visual presentation and templates must change with marketplace trends? Models enable you to design and implement a valuable experience for your customers, consistently, across products, authors, audiences, and time – even in a very large enterprise. In this workshop, we’ll work through the modeling process, and you will leave with the hands-on experience of developing a use model, a content model, and an access model.
In this workshop, we will discuss why modeling is important and describe the process, including prerequisite input to ensure high-quality, valid models. Then we will walk through a concrete exercise to develop use, content, and access models for a fictional company, taking the business situation, audience, and likely product-use into account. Finally we’ll discuss approaches for applying the models, and you will try your hand at implementing a release-specific architecture based on the models.
Handouts:
#1 Requirements worksheet: http://www.slideshare.net/aames/01requirements
#2 Scenario worksheet: http://www.slideshare.net/aames/02scenarios
#3 Design worksheet: http://www.slideshare.net/aames/03design
#4 Information Use Model worksheet: http://www.slideshare.net/aames/04info-usemodel
#5 Content Model worksheet: http://www.slideshare.net/aames/05content-model
#6 Access Model worksheet: http://www.slideshare.net/aames/06access-model
Using agile for business process design and development oct 19, 2010 ottawa
Is Agile Scrum just for software development or can it also be used to achieve great business process design and development as well?
Presented to the Ottawa IIBA Chapter on October 19, 2010
Workshop: Cisco Mobility Express Solution: Simple by Design
Learn how the Cisco Mobility Express solution eliminates the need for an appliance-based WLAN controller for small-scale deployments, while delivering Cisco's enterprise-scale expertise.
JAD Workshops
Joint Application Design (JAD) was developed by IBM in the late 1970s. It is a requirements determination method that brings together business and IT professionals in a structured workshop to determine and discuss system requirements
Water scrum-fall is-reality_of_agile_for_most
- Many organizations adopt aspects of Agile like Scrum but fail to fully realize its benefits due to constraints from organizational culture and governance processes (water-Scrum-fall). Under this model, upfront planning and requirements definition occurs outside of sprints (water), teams use Scrum practices to develop within sprints, and strict release gates limit how often software can be released (fall).
- To increase agility, organizations must understand the limitations of water-Scrum-fall and explicitly decide where to push boundaries between phases, involve development more in requirements, keep teams together across projects, and enable more frequent software releases.
Maturing Agile SDLC & workflow improvements
This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
Building a developer documentation wiki
The document discusses building a developer documentation wiki. It describes surveying developers to understand their documentation needs, including a preference for single dedicated sites with clear navigation and tutorials. It then details moving documentation from an old wiki to a new one, including customizing the new wiki with themes, plugins, and iterative development. It also covers managing community contributions through permissions, licensing, and "doc sprints" where contributors focus on documentation.
Effective requirements gathering workshops
PLEASE DOWNLOAD TO VIEW ANIMATIONS & SPEAKER NOTES.
Analyst: What would you like SharePoint to do?
Customer: Well, what can it do?
Analyst: Tons! Let me show you…
All too often, this is how conversations between analysts and customers/stakeholders begin, and it isn’t helpful to anyone. SharePoint has a vast array of capabilities, but if you start by describing or demonstrating what SharePoint can do and how the technology works, you will end up with customers who are confused and don’t know where to begin, or who have massively overblown expectations.
In this session, you will learn how to set up and conduct workshops with various stakeholders that will allow you to understand their real needs. You will then learn how to document and organize this information so that it is useful to the stakeholders and that will allow you to guide them through prioritization and planning.
You will learn when NOT to do demonstrations of SharePoint, and when and how to do demos that are powerful and effective.
JIRA 101 - Over(our)head No Longer!
A presentation about JIRA as it applied to the company's changing software development process. Given to the devs.
Applying both Agile and Waterfall in one project
Agile is gathering momentum but its not easy to switch to Agile especially in complex environments like banking or multinationals. Many companies can’t refuse Waterfall but understand the value of Agile and want to start applying it. How to combine Waterfall and Agile in one project, do it effectively and get value? In every standard Waterfall phase from initiation till closure Agile is able to help Project manager, team and stakeholders be more effective, adaptive, meet end user expectations better and have a fun. There are cases from CISCO Systems, NASA, US health care program to learn from.
I want to demonstrate that it is possible and often necessary to combine both Waterfall and Agile in one project. We will review challenges of big complex environments that have absorbed Waterfall and have strict procedures and guidelines but are willing to gradually move to Agile.
Software Development with Agile Waterfall Hybrid Method
Our latest webinar "Software Development with Agile Waterfall Hybrid Method" presents you the pros and cons of both methodologies, Agile and Waterfall.
Watch our webinar to learn more about what kind of projects the Hybrid model works for best, and how exactly you can implement a Hybrid approch in software development and benefit from the advanced features of codeBeamer ALM software.
Writing Effective User Stories
This document discusses writing effective user stories for agile software development. It defines what user stories are, how they follow the INVEST model, and how to gather and manage user stories through techniques like user role modeling, interviews, observation, and workshops. It also covers pros and cons of the user story approach.
Agifall - Combining Waterfall and Agile Development Process for Digital and S...
We all know waterfall has generally fallen out of favour and agile is the new process wunderkind. However, is pure agile really appropriate, or even possible, for the majority of our current digital projects? If the technical team is driving the agile development process from the start, just how and when do we integrate the user experience and creative contribution into the project lifecycle? Does agile really mean development first with no upfront design or specification, or, is there a better way to make agile development more effective when it begins? Certainly agile can be problematic for client projects when the statement of work contract is king for establishing project scope ahead of time. So how do we successfully integrate the benefits of agile into client-vendor engagements without putting either party at risk? This presentation topic is on how to effectively combine the best of waterfall and agile into a hybrid process model called “Agifall.” No process is perfect, but Agifall just might be the one that works best for your next project.
Definition of Ready (XP2011)
The document discusses the definition of ready as it relates to user stories and sprints in agile software development. It provides details on what constitutes a user story being ready, including it being defined, having acceptance criteria, identified dependencies, sized by the team, and more. It also lists criteria for a sprint to be ready, such as the sprint backlog being prioritized and containing all committed work with no hidden work, and all team members having calculated their capacity for the sprint.
Viewers also liked (20)
Documentation in the agile software development process
Documentation in the agile software development process
Producing Quality Documentation In An Agile Development Environment
Producing Quality Documentation In An Agile Development Environment
SharePoint Fest Chicago - Shifting the Paradigm of Requirements Gathering
SharePoint Fest Chicago - Shifting the Paradigm of Requirements Gathering
Content Experience Modeling: Designing Customer Value and Consistency
Content Experience Modeling: Designing Customer Value and Consistency
Using agile for business process design and development oct 19, 2010 ottawa
Using agile for business process design and development oct 19, 2010 ottawa
Workshop: Cisco Mobility Express Solution: Simple by Design
Workshop: Cisco Mobility Express Solution: Simple by Design
Software Development with Agile Waterfall Hybrid Method
Software Development with Agile Waterfall Hybrid Method
Agifall - Combining Waterfall and Agile Development Process for Digital and S...
Agifall - Combining Waterfall and Agile Development Process for Digital and S...
Similar to Introduction to agile documentation
BizSpark SF Lightning Talk: "Design Patterns for Designers" by Stephan Orme
The document discusses design patterns for product design. It explains that design patterns originate from Christopher Alexander's work and capture solutions to common design problems. The document then outlines the key components of the product design process, including understanding needs, agreeing with stakeholders, and providing direction. It describes discovery and design processes that involve user research, diagramming solutions, and developing models, views, and controls. The goal is to understand needs, get stakeholder agreement, and provide clear direction for developers.
Producing documentation for Eclipse RCP applications using single source prin...
This document discusses using single source principles to produce documentation for Eclipse RCP applications. It outlines typical documentation deliverables like printed manuals, help files, and online documentation. Traditional documentation tools have challenges like redundant content and complex workflows. The document proposes using DITA and the DITAworks toolset as a solution. DITAworks allows authoring once and generating documentation in multiple formats from a single source. It also facilitates content reuse and integration with development processes.
Amiya_SCRUM@2016
The document provides a summary of Amiya Kumar Rout's experience as a Technical Manager with over 13 years of experience managing IT projects. He has extensive experience delivering projects using technologies like Microsoft Azure, DevOps, SharePoint and .NET. He is a certified SCRUM Master and Six Sigma Green Belt with a proven track record of managing teams and projects successfully.
Combining Orchestration and Choreography for a Clean Architecture
- Combining orchestration and choreography can provide a clean architecture for software systems. Orchestration uses a command-based style while choreography uses an event-driven communication style.
- Writing integrations following clean and hexagonal architecture principles increases maintainability, testability, and flexibility. This involves organizing the architecture into layers with adapters translating between systems and no outgoing dependencies from the domain core.
- Applying domain-driven design patterns like bounded contexts and domain events can further improve decoupling when combined with orchestration and choreography. Key practices include throwing events for data changes and only using them for communication outside bounded contexts.
Project post-mortem analysis
Learn more tips & techniques at www.pmpwisdom.blogspot.com
Register for a free webinar at
https://pmpwisdom.blogspot.com/p/webinar.html
DevEx Essentials
Ever wondered about Developer Experience (DevEx) and how it can truly impact your work? Join us for a chat where we break down what DevEx is and why it's relevant for everyone, not just devs. DevsOps and productivity expert Dr. Nicole Forsgren will reveal how DevEx can ignite cultural change and deliver real results in today's rapid software development landscape, backed by the latest research findings. She will share how Microsoft is leveraging a DevEx perspective to drive cultural shifts and enable AI-powered innovations that make expertise available to all teams. It's not just about code; it's about fostering better vibes and achieving outstanding outcomes for all. Don't miss out on this journey into the magic of DevEx.
Is Agile Documentation An Oxymoron?
The document discusses how agile development teams can take an agile approach to documentation in complex environments that require documentation for maintenance teams or auditors. It notes that while lightweight documentation works for development, more is needed for maintenance and audits. The author advocates treating documentation as separate deliverables produced during iterations to close gaps. By taking a just-in-time approach and identifying reusable elements, agile teams can generate necessary documentation without compromising agile principles.
Professional Resume for Lead Business Solutions, Business Analyst, Technical ...
Lead Business Solutions with 10 years experience in BFSI, Energy, Retail, and Telecommunication industries
Saikrishna_Bejjanki_HP Exstream Developer
Saikrishna Bejjanki is an Associate Consultant seeking a position to utilize and expand skills offering professional growth. He has 5.11 years of experience in HP Exstream Dialogue, mainframes, and financial domains including banking and insurance. He is proficient in COBOL, JCL, DB2, CICS, VSAM and has strong knowledge of migration projects from DOC1 composition to HP Exstream.
apidays LIVE New York 2021 - Docs Driven API Development by Rahul Dighe, Paypal
This document discusses an approach called "docs driven development" (DDD) where documentation is written before code is developed. The key points are:
DDD involves writing low-fidelity documentation like integration guides and API specifications before writing code. This helps align teams, get early feedback, and remind developers what product they are building. Potential benefits include fewer gaps in products and better alignment between teams. DDD is not a replacement for formal documentation or testing, but is meant to guide development from the start. The document provides examples of how DDD can be implemented and addresses common concerns about the approach.
Event Storming #10 DDDGreece
Introduction to one of the most recently developed techniques for collaborative modelling that has taken the DDD community by storm (pun intended).
Profile_Harish_Gaddale
Harish Gaddale is an integration architect with 8 years of experience in integration architecture and development. He has extensive experience with TIBCO products and full SDLC, and has worked on numerous integration projects for customers like NXP Semiconductors. Some of his responsibilities have included designing integration architectures, developing interfaces, unit testing, supporting go-lives, and providing technical consultancy. He is proficient in technologies like TIBCO Suite, Web services, EDI, and SaaS integrations with applications such as Workday, Ariba, and Salesforce.
Evolution of design systems at GE
The story of multiple generations of design systems created to support UX design practices at GE. Video of narration here: https://www.youtube.com/watch?v=Ou3v7aiJQU0
IC-SDV 2019: Down-to-earth machine learning: What you always wanted your data...
Applications of machine learning on NLP tasks today receive a lot of attention and have been shown to yield state of the art results on a wide range of tasks. We describe several cases where machine learning is deployed productively under the usual constaints of real-world projects: Real-world requirements, fast throughput, reasonably low requirements in terms of training corpus size and high quality results. What we observe is a general trend towards open source - also our components are open source. With the software being mostly freely available, among the key success criteria for many NLP projects today therefore is first and foremost the necessary expertise required to combine, tune and apply open source components.
Developing architects by design
The document discusses developing architects through capability-based training programs. It notes that the demand for architects exceeds supply, and in-house training has been ineffective. It advocates defining capabilities that architects should demonstrate, such as preparing architecture documents. It also recommends experience-based programs that impart knowledge, provide mentorship and assess capabilities through activities, exercises and projects. The goal is to align training with business needs and develop architects through a structured, outcomes-focused approach.
Large drupal site builds a workshop for sxsw interactive - march 17, 2015
Slides from a 4hr workshop at SXSW 2015 on Large Drupal Projects and how to manage them, and the special technical challenges.
Dany.shapiro cv-en
Dany Shapiro has over 11 years of experience as a Big Data and Cloud Architect. He currently works at ECI as an Architect in the CTO Group, where he focuses on disruptive solutions like Big Data, Cloud Computing, and machine learning. Previously he worked at SAP, where he was a Software Architect and helped develop a Platform as a Service solution. He has extensive experience with technologies like Apache Spark, Hadoop, MongoDB, Java, and Cloud platforms like AWS and Cloud Foundry.
Discover, Define, Deliver - a workflow to create successful digital products.
Presentation from STX Next Summit 2016 by Dominik Oślizło describing the Discover, Define, Deliver process, a rock-solid approach that ensures smooth idea-to-product transitions and radically accelerates time-to-market.
Integrating Advanced Analytics with Autodesk Solutions
Learn how to integrate analytics software with Autodesk products to improve project visibility and communicate progress, issues and accomplishments to project stakeholders.
This class highlights proven approaches to design and integrate analytics into a project and demonstrates how stakeholders have the ability to view charts and trends including the ability to drill down into project data to identify challenge areas and apply corrective actions to improve the likelihood of a successful project outcome.
Knowage 8 presentation
The new functionalities of KNOWAGE 8 allow to integrate advanced and increasingly personalized analyses in decision-making processes in a simple and rapid way.
Similar to Introduction to agile documentation (20)
BizSpark SF Lightning Talk: "Design Patterns for Designers" by Stephan Orme
BizSpark SF Lightning Talk: "Design Patterns for Designers" by Stephan Orme
Producing documentation for Eclipse RCP applications using single source prin...
Producing documentation for Eclipse RCP applications using single source prin...
Combining Orchestration and Choreography for a Clean Architecture
Combining Orchestration and Choreography for a Clean Architecture
Professional Resume for Lead Business Solutions, Business Analyst, Technical ...
Professional Resume for Lead Business Solutions, Business Analyst, Technical ...
apidays LIVE New York 2021 - Docs Driven API Development by Rahul Dighe, Paypal
apidays LIVE New York 2021 - Docs Driven API Development by Rahul Dighe, Paypal
IC-SDV 2019: Down-to-earth machine learning: What you always wanted your data...
IC-SDV 2019: Down-to-earth machine learning: What you always wanted your data...
Large drupal site builds a workshop for sxsw interactive - march 17, 2015
Large drupal site builds a workshop for sxsw interactive - march 17, 2015
Discover, Define, Deliver - a workflow to create successful digital products.
Discover, Define, Deliver - a workflow to create successful digital products.
Integrating Advanced Analytics with Autodesk Solutions
Integrating Advanced Analytics with Autodesk Solutions
Recently uploaded
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
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.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
“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.
UiPath Test Automation using UiPath Test Suite series, part 6
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
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
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
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Fueling AI with Great Data with Airbyte Webinar
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.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
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!
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
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
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Recently uploaded (20)
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Introduction to agile documentation
- 1. INTRODUCTION TO AGILE DOCUMENTATION Daniel Grycman / bilstein group, Ennepetal / @danielgrycman
- 2. ABOUT ME Software Developer & Consultant at Ferdinand Bilstein GmbH + Co. KG, Ennepetal Specialist for Dynamic Publishing Processes, Atlassian Stack Development & Integration Interests: IDEs & Tools, Documentation as part of SDLC, Docker, Microservice based architectures Member of the organizing team of ruhrJUG in Essen Local organizer of Docker Meetup Bochum
- 5. CENTRAL SERVICE SOLUTIONS Data Maintenance Division System Development Division
- 6. AGILE MANIFESTO Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 7. DOCUMENTING WITH AN AGILE MINDSET No rigid guidelines on how to document Focus on delivering value to the customer Rethinking the way to document Adapting the change Documentation should occur when necessary
- 8. WHY DOCUMENT? Needed for what purpose? Target audience? Use of documentation?
- 10. BEFORE THE PROJECT STARTS Technical view High-level architecture diagrams Functional view Main epics to identify the main characteristics of the development case
- 12. DURING THE PROJECT / TECHNICAL VIEW Test-Driven Development (TDD) Behaviour-Driven Development (BDD) Well structured code Code as documentation
- 13. DURING THE PROJECT / FUNCTIONAL VIEW User story as requirements for developers with well-defined, clear in meaning acceptance criteria Acceptance criteria as documentation
- 15. AFTER IMPLEMENTATION AND ROLLOUT / TECHNICAL VIEW Code as technical documentation
- 16. AFTER IMPLEMENTATION AND ROLLOUT / FUNCTIONAL VIEW Code as living documentation
- 17. WHERE TO DOCUMENT? Accessible and updatable repository
- 18. WHEN TO DOCUMENT? Produce documentation incrementally Evolve documentation along with the development
- 19. ASCIIDOC(TOR) Ruby implementation of python-based Asciidoc interpreter Asciidoc is a lightweight markup language Single source publishing toolchain
- 20. JBAKE — Dan Allen Jekyll of the JVM
- 21. JBAKE originally a static site / blog generator support of several template engine implementable in a build pipeline
- 22. DEMO TIME
- 24. REFERENCES Images copyright by Bilstein Group, Ennepetal expect of: building_blocks.jpg — Björn Egil Johansen notebook_with_pencils — Matt Carnock plane_start.jpg — Bernal Saborio / berkuspic route.jpg — Over Doz scrum_cycle.jpg — Oliver Tacke signpost.jpg — Chris Blakeley
- 25. Generated with Asciidoctor v1.5.4.