Multiple Business Analyst Views in Agile
Download as pptx, pdf1 like69 views
This document outlines different views and activities in an agile process including the iteration view, release view, and day view. The iteration view shows the typical events and flow of a two week sprint with daily stand-ups, kick-off, volleyball, and IPM showcase at the end. The release view illustrates how multiple iterations fit together and feed into one another. The day view provides more detail on daily activities like stand-ups, wall updates, story sign-ups, and development huddles.
1 of 2
Download to read offline
Ad
Recommended
Agile Release & Iteration Planning
Agile Release & Iteration Planning Intelliware Development Inc.
油
The document discusses the different levels of planning in Agile development: release planning, iteration planning, and task planning. It provides details on each level, including who is involved, how to define a release plan, estimating velocity, common problems and solutions, and examples. The key aspects covered are the differences between releases and iterations, estimating at each level, and breaking down stories into tasks.The Agile PMP Workshop
The Agile PMP WorkshopMike Cottmeyer
油
The document discusses Agile project management methodologies, emphasizing the need for flexibility in uncertain project environments. It outlines principles from the Agile Manifesto, including customer satisfaction through continuous delivery and responsiveness to change, advocating for better communication and collaboration among team members. Additionally, it covers practical aspects of Agile practices, such as backlog management, sprint planning, and retrospective processes to foster continuous improvement.Agile Testing and Release Management
Agile Testing and Release Managementcraigparsons77
油
The document discusses a case study on agile development, focusing on the practices and principles that make agile successful in software projects. It emphasizes the importance of cohesive teams, iterative development, and effective communication through frameworks such as the Agile Manifesto and various team structures. Key aspects covered include managing iterations, quality checkpoints, and the roles and responsibilities in release management to enhance collaboration and efficiency within agile teams.Walkabout workshop
Walkabout workshopKnowit_TM
油
This document outlines an agenda for demonstrating how to make project, program, and portfolio management more agile using the Unified Vision Framework. It includes goals of showing how to cascade vision and strategy, use the VSPT model and 4D model, and implement agile governance. The document provides examples and exercises for attendees to practice these concepts, including creating epics and user stories for a project backlog, discussing a case study, and planning a portfolio "walkabout" to identify dependencies between projects. Charts are presented showing how the Unified Vision Framework has helped organizations double their project velocity without increasing team size.Agile User Stories
Agile User Storieskahgeh75
油
This document discusses agile software development practices with a focus on user stories. It covers the objectives of using user stories, a brief history and motivation for agile practices, an overview of the agile process including daily standups and planning meetings, and the components and writing of user stories. It also discusses managing projects using tools for planning, estimating, and tracking progress. Key practices for development teams like refactoring, test automation, and dealing with unplanned tasks are also summarized.Agile Release & Iteration Planning
Agile Release & Iteration PlanningIntelliware Development Inc.
油
The document discusses the three levels of agile planning: release, iteration, and task planning. It describes the process for defining a release plan including estimating velocity, organizing stories into iterations, and allowing for plan variations. Iteration planning and task planning are also summarized, including when they occur, who is involved, and an example task board.Agile process with a fixed cost
Agile process with a fixed costRalph Johnson
油
An agile software development process is proposed that allows for a fixed budget and scope. The process involves planning with user stories, allocating stories to sprints, daily scrums, automated testing and deployment, and client sign-off. Any additional requirements are tracked as change requests that can be completed with contingencies or additional funds. The environments are separated to allow efficient testing and deployment without overhead. This process aims to balance the agile development benefits with the fixed budget needs of CFOs.Scrum and Visual Studio 2010
Scrum and Visual Studio 2010Patrick Yong
油
This document discusses using Scrum for agile software development. It covers planning a project with a product backlog of prioritized user stories, planning sprints by committing to stories and tasks, running sprints with daily standups and a demo at the end, and reporting on burndowns, tests, bugs, and story progress. Visual Studio tools like work items and queries can help manage artifacts for Scrum projects. Iterative development with Scrum focuses on early delivery of valuable features.Agile QA Process
Agile QA ProcessAnand Bagmar
油
The document outlines the Agile QA process, emphasizing that quality is a shared responsibility among the team, with QA playing a proactive role. It details stages including Agile testing from iteration to release, responsibilities within each iteration, and effective communication practices to enhance collaboration. Additionally, it provides guidelines for defect reporting, testing strategies, and tools for maintaining visibility and tracking the quality of the product.User stories how to cook a cat?
User stories how to cook a cat?Vladimir Tarasov
油
The document outlines the characteristics and importance of user stories in software development, emphasizing their role in delivering value while being small, testable, and independently manageable. It provides examples of good and bad user stories, with explanations of their drawbacks, and discusses related concepts like epics and themes. Additionally, it highlights the iterative and incremental development process and the roles of stakeholders in shaping user stories.Product owner
Product ownerLuis Gon巽alves, CSP
油
The product owner is responsible for maximizing the value of the product by ensuring that the appropriate features are implemented in each release. This includes creating and prioritizing the product backlog, accepting or rejecting user stories, and collaborating with the scrum master and development team. The product owner defines the product vision and user stories using an INVEST framework to ensure they are independent, negotiable, valuable, small, estimable, and testable. Acceptance criteria are also defined to determine when a story is complete.Product owner
Product ownerMrSnow76
油
The product owner is responsible for maximizing the value of the product by ensuring that the appropriate features are implemented in each release. This includes managing the product backlog, which contains the features, enhancements and fixes prioritized by the product owner. The product owner works closely with the scrum master and development team to refine user stories, establish acceptance criteria, participate in planning and review sessions, and make decisions about the product.Iteration planning and user story definition
Iteration planning and user story definitionjobin joy
油
The document discusses iteration planning in agile software development. Iteration planning is a meeting at the start of each iteration where the development team plans the next set of product backlog items to complete within the iteration timeframe. The team determines how many stories can fit based on velocity, breaks stories into tasks, estimates task hours, and ensures capacity is not exceeded. The product owner describes high-priority stories and the team plans the tasks needed to complete them.Story writing
Story writingItamar Hassin
油
This document discusses stories as a unit of behavioral change in agile development. It defines stories as representing business value from a user's perspective that can be tested and quantified. Stories should be written to minimize business risk. The elements of a good story are outlined as having a narrative focus from a persona's point of view with a clear value statement and definition of what constitutes completion. The mechanics of story kickoff, development, testing and milestones are also summarized. Do's and don'ts emphasize involving stakeholders and using business not technical language.How to write Good User Stories?
How to write Good User Stories?Inflectra
油
The document outlines a webinar hosted by Dr. Sriram Rajagopalan focused on writing effective user stories within agile methodologies, emphasizing the importance of understanding user personas and strategic requirements gathering. Key practices for writing good user stories are identified, such as promoting team collaboration, ensuring clarity, and prioritizing user value. The presentation concludes with a summary of best practices and encourages audience engagement through Q&A and feedback.Transitioning To Agile
Transitioning To Agile ThoughtWorks Studios
油
The document discusses transitioning to agile software development, highlighting key concepts such as incremental and iterative processes, collaboration, and the importance of defined roles within agile teams. It stresses the need for executive commitment, careful planning, and the potential cultural impacts when adopting agile practices. Various roles in agile teams, along with practices for managers, developers, and testers, are outlined, emphasizing the necessity for team involvement and continuous integration.User Stories
User StoriesRobert Dempsey
油
The document discusses user stories in the context of Agile development, emphasizing their role in representing customer requirements and facilitating conversations rather than merely documenting details. It explains the characteristics of good user stories, the importance of acceptance criteria, and the process of writing stories, including sources and user roles involved. Key guidelines are provided to ensure stories are independent, negotiable, valuable, estimatable, and testable, along with a focus on effective communication and iterative development.Test Driven Development via Agile Testing
Test Driven Development via Agile TestingAnand Bagmar
油
The document discusses test-driven development within agile projects, emphasizing the importance of automation and the test pyramid for effective testing strategies. It outlines behavior-driven development (BDD) with examples of test specifications and user scenarios, highlighting the transition from manual to automated testing frameworks. The text also touches on the collaboration between development and QA teams and the tools that facilitate this process.Effective User Story Writing
Effective User Story WritingAhmed Misbah
油
The document discusses effective user story writing in agile development. It covers topics like what a product backlog and user stories are, how to write good user stories, acceptance criteria, and tools to help with user story development like story mapping workshops and definition of ready. The goal is to provide guidance to write clear, valuable user stories that help teams deliver the desired product functionality.Agile Dependency Management
Agile Dependency ManagementKmanthei
油
This document discusses various types of dependencies that can impact agile planning and development if not properly managed. It begins by covering dependencies related to requirements preparation, UI design, and inter-story dependencies that can delay development if not addressed in advance. It then discusses external dependencies on other teams, vendors, or systems that may not follow agile practices. The document provides recommendations for minimizing the impact of dependencies, such as advanced planning, cross-team coordination, and determining if dependencies are truly necessary or if workarounds are possible. The overall message is that dependencies require extra planning efforts to avoid blocking development work or impacting velocity.Agile Scrum at Double V3
Agile Scrum at Double V3bmasse @ Nexio
油
This document discusses how to work with a Scrum organization as a client. It outlines the key roles in Scrum - Product Manager, Scrum Master, and cross-functional team. It describes the Scrum process, including meetings, artifacts, and metrics used. It also discusses how Scrum-friendly contracts differ from traditional fixed schedule/budget contracts. Clients should understand the iterative nature of Scrum and work with the Product Manager as the main point of contact.Digite - Project Management Training
Digite - Project Management TrainingDigite, Inc.
油
The document provides an overview of agile project management in Digit辿 Enterprise, including common agile methodologies and elements, how agile projects are set up and managed in Digit辿, and how reporting and tracking of user stories, iterations, releases and team progress is done. Key aspects covered are product backlog definition, release and iteration planning, story execution and logging efforts, test execution and defect tracking, and agile reports.Introduction to Agile & Scrum
Introduction to Agile & ScrumHawkman Academy
油
This document provides an overview of an introduction workshop on Agile and Scrum. The workshop covers topics such as the history and principles of Agile, an introduction to Scrum frameworks and roles, and exercises on writing user stories and estimating story points. Participants will learn about Agile and Scrum methodologies, how to write and evaluate user stories, and techniques for relative estimation like planning poker. The goal is for participants to understand key Agile and Scrum concepts and practices and be able to apply them.Get Ready For Your First Iteration
Get Ready For Your First IterationNaresh Jain
油
The document outlines a structured approach for product development within an agile community, focusing on creating shared goals, user personas, and story maps to guide iterative delivery. It emphasizes the importance of community involvement, planning, and continuous improvement through feedback and retrospectives. Key tools include project charters, defining user experiences, and prioritizing tasks to enhance product value.Agile - Iteration 0 CodeMash 2010
Agile - Iteration 0 CodeMash 2010kensipe
油
The document discusses the purpose and activities of Iteration 0 in an agile development process. It describes setting up key infrastructure items like version control, IDE configuration, build systems, continuous integration, and project management tools. It emphasizes automating as many tasks as possible. The goal of Iteration 0 is to establish the foundation for subsequent iterations by creating a stable development environment and processes.Agile Scrum Overview
Agile Scrum OverviewJason Dean
油
The document discusses Agile Scrum, including:
- The Agile Manifesto principles of prioritizing individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan.
- Scrum roles like Product Owner, Scrum Master, and cross-functional team members.
- Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives.
- User stories, epics, and conditions of satisfaction to define work in the product backlog.
- The goal of each sprint is to produce potentially shippable increments of functionality.Webinar 5 - Excellence in reporting
Webinar 5 - Excellence in reportingSriram Rajagopalan
油
This webinar discussed excellence in reporting for agile projects. It began with introducing the speaker, Dr. Sriram Rajagopalan, and providing an agenda for the webinar. It then covered how reports should tell a story with specific elements like measures, audiences, and objectives. The webinar explored different types of reports including burnup, burndown, velocity and earned value reports. It emphasized using reports to communicate purpose and provide actionable insights. Finally, it demonstrated reporting features in the SpiraTeam tool and invited questions from participants.Agile Project Management - Course Details
Agile Project Management - Course Detailsalirazakdsp2023
油
The document provides an overview of Agile project management, emphasizing its relevance in rapidly changing environments driven by technology and customer demands. It contrasts Agile methodologies with traditional approaches, highlighting principles like customer collaboration, flexibility, and iterative progress. Additionally, it discusses the benefits of Agile practices, including improved product delivery and alignment between business and technology.A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdf
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdfPriyanka Aash
油
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...Fwdays
油
What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.More Related Content
Similar to Multiple Business Analyst Views in Agile (20)
Agile QA Process
Agile QA ProcessAnand Bagmar
油
The document outlines the Agile QA process, emphasizing that quality is a shared responsibility among the team, with QA playing a proactive role. It details stages including Agile testing from iteration to release, responsibilities within each iteration, and effective communication practices to enhance collaboration. Additionally, it provides guidelines for defect reporting, testing strategies, and tools for maintaining visibility and tracking the quality of the product.User stories how to cook a cat?
User stories how to cook a cat?Vladimir Tarasov
油
The document outlines the characteristics and importance of user stories in software development, emphasizing their role in delivering value while being small, testable, and independently manageable. It provides examples of good and bad user stories, with explanations of their drawbacks, and discusses related concepts like epics and themes. Additionally, it highlights the iterative and incremental development process and the roles of stakeholders in shaping user stories.Product owner
Product ownerLuis Gon巽alves, CSP
油
The product owner is responsible for maximizing the value of the product by ensuring that the appropriate features are implemented in each release. This includes creating and prioritizing the product backlog, accepting or rejecting user stories, and collaborating with the scrum master and development team. The product owner defines the product vision and user stories using an INVEST framework to ensure they are independent, negotiable, valuable, small, estimable, and testable. Acceptance criteria are also defined to determine when a story is complete.Product owner
Product ownerMrSnow76
油
The product owner is responsible for maximizing the value of the product by ensuring that the appropriate features are implemented in each release. This includes managing the product backlog, which contains the features, enhancements and fixes prioritized by the product owner. The product owner works closely with the scrum master and development team to refine user stories, establish acceptance criteria, participate in planning and review sessions, and make decisions about the product.Iteration planning and user story definition
Iteration planning and user story definitionjobin joy
油
The document discusses iteration planning in agile software development. Iteration planning is a meeting at the start of each iteration where the development team plans the next set of product backlog items to complete within the iteration timeframe. The team determines how many stories can fit based on velocity, breaks stories into tasks, estimates task hours, and ensures capacity is not exceeded. The product owner describes high-priority stories and the team plans the tasks needed to complete them.Story writing
Story writingItamar Hassin
油
This document discusses stories as a unit of behavioral change in agile development. It defines stories as representing business value from a user's perspective that can be tested and quantified. Stories should be written to minimize business risk. The elements of a good story are outlined as having a narrative focus from a persona's point of view with a clear value statement and definition of what constitutes completion. The mechanics of story kickoff, development, testing and milestones are also summarized. Do's and don'ts emphasize involving stakeholders and using business not technical language.How to write Good User Stories?
How to write Good User Stories?Inflectra
油
The document outlines a webinar hosted by Dr. Sriram Rajagopalan focused on writing effective user stories within agile methodologies, emphasizing the importance of understanding user personas and strategic requirements gathering. Key practices for writing good user stories are identified, such as promoting team collaboration, ensuring clarity, and prioritizing user value. The presentation concludes with a summary of best practices and encourages audience engagement through Q&A and feedback.Transitioning To Agile
Transitioning To Agile ThoughtWorks Studios
油
The document discusses transitioning to agile software development, highlighting key concepts such as incremental and iterative processes, collaboration, and the importance of defined roles within agile teams. It stresses the need for executive commitment, careful planning, and the potential cultural impacts when adopting agile practices. Various roles in agile teams, along with practices for managers, developers, and testers, are outlined, emphasizing the necessity for team involvement and continuous integration.User Stories
User StoriesRobert Dempsey
油
The document discusses user stories in the context of Agile development, emphasizing their role in representing customer requirements and facilitating conversations rather than merely documenting details. It explains the characteristics of good user stories, the importance of acceptance criteria, and the process of writing stories, including sources and user roles involved. Key guidelines are provided to ensure stories are independent, negotiable, valuable, estimatable, and testable, along with a focus on effective communication and iterative development.Test Driven Development via Agile Testing
Test Driven Development via Agile TestingAnand Bagmar
油
The document discusses test-driven development within agile projects, emphasizing the importance of automation and the test pyramid for effective testing strategies. It outlines behavior-driven development (BDD) with examples of test specifications and user scenarios, highlighting the transition from manual to automated testing frameworks. The text also touches on the collaboration between development and QA teams and the tools that facilitate this process.Effective User Story Writing
Effective User Story WritingAhmed Misbah
油
The document discusses effective user story writing in agile development. It covers topics like what a product backlog and user stories are, how to write good user stories, acceptance criteria, and tools to help with user story development like story mapping workshops and definition of ready. The goal is to provide guidance to write clear, valuable user stories that help teams deliver the desired product functionality.Agile Dependency Management
Agile Dependency ManagementKmanthei
油
This document discusses various types of dependencies that can impact agile planning and development if not properly managed. It begins by covering dependencies related to requirements preparation, UI design, and inter-story dependencies that can delay development if not addressed in advance. It then discusses external dependencies on other teams, vendors, or systems that may not follow agile practices. The document provides recommendations for minimizing the impact of dependencies, such as advanced planning, cross-team coordination, and determining if dependencies are truly necessary or if workarounds are possible. The overall message is that dependencies require extra planning efforts to avoid blocking development work or impacting velocity.Agile Scrum at Double V3
Agile Scrum at Double V3bmasse @ Nexio
油
This document discusses how to work with a Scrum organization as a client. It outlines the key roles in Scrum - Product Manager, Scrum Master, and cross-functional team. It describes the Scrum process, including meetings, artifacts, and metrics used. It also discusses how Scrum-friendly contracts differ from traditional fixed schedule/budget contracts. Clients should understand the iterative nature of Scrum and work with the Product Manager as the main point of contact.Digite - Project Management Training
Digite - Project Management TrainingDigite, Inc.
油
The document provides an overview of agile project management in Digit辿 Enterprise, including common agile methodologies and elements, how agile projects are set up and managed in Digit辿, and how reporting and tracking of user stories, iterations, releases and team progress is done. Key aspects covered are product backlog definition, release and iteration planning, story execution and logging efforts, test execution and defect tracking, and agile reports.Introduction to Agile & Scrum
Introduction to Agile & ScrumHawkman Academy
油
This document provides an overview of an introduction workshop on Agile and Scrum. The workshop covers topics such as the history and principles of Agile, an introduction to Scrum frameworks and roles, and exercises on writing user stories and estimating story points. Participants will learn about Agile and Scrum methodologies, how to write and evaluate user stories, and techniques for relative estimation like planning poker. The goal is for participants to understand key Agile and Scrum concepts and practices and be able to apply them.Get Ready For Your First Iteration
Get Ready For Your First IterationNaresh Jain
油
The document outlines a structured approach for product development within an agile community, focusing on creating shared goals, user personas, and story maps to guide iterative delivery. It emphasizes the importance of community involvement, planning, and continuous improvement through feedback and retrospectives. Key tools include project charters, defining user experiences, and prioritizing tasks to enhance product value.Agile - Iteration 0 CodeMash 2010
Agile - Iteration 0 CodeMash 2010kensipe
油
The document discusses the purpose and activities of Iteration 0 in an agile development process. It describes setting up key infrastructure items like version control, IDE configuration, build systems, continuous integration, and project management tools. It emphasizes automating as many tasks as possible. The goal of Iteration 0 is to establish the foundation for subsequent iterations by creating a stable development environment and processes.Agile Scrum Overview
Agile Scrum OverviewJason Dean
油
The document discusses Agile Scrum, including:
- The Agile Manifesto principles of prioritizing individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan.
- Scrum roles like Product Owner, Scrum Master, and cross-functional team members.
- Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives.
- User stories, epics, and conditions of satisfaction to define work in the product backlog.
- The goal of each sprint is to produce potentially shippable increments of functionality.Webinar 5 - Excellence in reporting
Webinar 5 - Excellence in reportingSriram Rajagopalan
油
This webinar discussed excellence in reporting for agile projects. It began with introducing the speaker, Dr. Sriram Rajagopalan, and providing an agenda for the webinar. It then covered how reports should tell a story with specific elements like measures, audiences, and objectives. The webinar explored different types of reports including burnup, burndown, velocity and earned value reports. It emphasized using reports to communicate purpose and provide actionable insights. Finally, it demonstrated reporting features in the SpiraTeam tool and invited questions from participants.Agile Project Management - Course Details
Agile Project Management - Course Detailsalirazakdsp2023
油
The document provides an overview of Agile project management, emphasizing its relevance in rapidly changing environments driven by technology and customer demands. It contrasts Agile methodologies with traditional approaches, highlighting principles like customer collaboration, flexibility, and iterative progress. Additionally, it discusses the benefits of Agile practices, including improved product delivery and alignment between business and technology.Recently uploaded (20)
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdf
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdfPriyanka Aash
油
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...Fwdays
油
What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.UserCon Belgium: Honey, VMware increased my bill
UserCon Belgium: Honey, VMware increased my billstijn40
油
VMwares pricing changes have forced organizations to rethink their datacenter cost management strategies. While FinOps is commonly associated with cloud environments, the FinOps Foundation has recently expanded its framework to include Scopesand Datacenter is now officially part of the equation. In this session, well map the FinOps Framework to a VMware-based datacenter, focusing on cost visibility, optimization, and automation. Youll learn how to track costs more effectively, rightsize workloads, optimize licensing, and drive efficiencyall without migrating to the cloud. Well also explore how to align IT teams, finance, and leadership around cost-aware decision-making for on-prem environments. If your VMware bill keeps increasing and you need a new approach to cost management, this session is for you!10 Key Challenges for AI within the EU Data Protection Framework.pdf
10 Key Challenges for AI within the EU Data Protection Framework.pdfPriyanka Aash
油
10 Key Challenges for AI within the EU Data Protection FrameworkCurietech AI in action - Accelerate MuleSoft development
Curietech AI in action - Accelerate MuleSoft developmentshyamraj55
油
CurieTech AI in Action Accelerate MuleSoft Development
Overview:
This presentation demonstrates how CurieTech AIs purpose-built agents empower MuleSoft developers to create integration workflows faster, more accurately, and with less manual effort
linkedin.com
+12
curietech.ai
+12
meetups.mulesoft.com
+12
.
Key Highlights:
Dedicated AI agents for every stage: Coding, Testing (MUnit), Documentation, Code Review, and Migration
curietech.ai
+7
curietech.ai
+7
medium.com
+7
DataWeave automation: Generate mappings from tables or samples95%+ complete within minutes
linkedin.com
+7
curietech.ai
+7
medium.com
+7
Integration flow generation: Auto-create Mule flows based on specificationsspeeds up boilerplate development
curietech.ai
+1
medium.com
+1
Efficient code reviews: Gain intelligent feedback on flows, patterns, and error handling
youtube.com
+8
curietech.ai
+8
curietech.ai
+8
Test & documentation automation: Auto-generate MUnit test cases, sample data, and detailed docs from code
curietech.ai
+5
curietech.ai
+5
medium.com
+5
Why Now?
Achieve 10 productivity gains, slashing development time from hours to minutes
curietech.ai
+3
curietech.ai
+3
medium.com
+3
Maintain high accuracy with code quality matching or exceeding manual efforts
curietech.ai
+2
curietech.ai
+2
curietech.ai
+2
Ideal for developers, architects, and teams wanting to scale MuleSoft projects with AI efficiency
Conclusion:
CurieTech AI transforms MuleSoft development into an AI-accelerated workflowletting you focus on innovation, not repetition.Agentic AI for Developers and Data Scientists Build an AI Agent in 10 Lines o...
Agentic AI for Developers and Data Scientists Build an AI Agent in 10 Lines o...All Things Open
油
Presented at All Things Open RTP Meetup
Presented by William Hill - Developer Advocate, NVIDIA
Title: Agentic AI for Developers and Data Scientists
Build an AI Agent in 10 Lines of Code and the Concepts Behind the Code
Abstract: In this talk we will demonstrate building a working data science AI agent in 10 lines of basic Python code in a Colab notebook. Our AI Agent will perform LLM prompt-driven visual analysis using open-source libraries. In this session we will show how to develop an AI Agent using GPUs through NVIDIAs developer program and Google Colab notebooks. After coding our AI Agent, we will break down the 10 lines of code. We will show the key components and open source library integrations that enable the agent's functionality, focusing on practical implementation details and then the theoretical concepts. The presentation concludes with a survey of current LLM technologies and the latest trends in developing AI applications for enthusiasts and enterprisesTech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdf
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdfcaoyixuan2019
油
A presentation at Internetware 2025.Quantum AI: Where Impossible Becomes Probable
Quantum AI: Where Impossible Becomes ProbableSaikat Basu
油
Imagine combining the "brains" of Artificial Intelligence (AI) with the "super muscles" of Quantum Computing. That's Quantum AI!
It's a new field that uses the mind-bending rules of quantum physics to make AI even more powerful.OpenACC and Open Hackathons Monthly Highlights June 2025
OpenACC and Open Hackathons Monthly Highlights June 2025OpenACC
油
The OpenACC organization focuses on enhancing parallel computing skills and advancing interoperability in scientific applications through hackathons and training. The upcoming 2025 Open Accelerated Computing Summit (OACS) aims to explore the convergence of AI and HPC in scientific computing and foster knowledge sharing. This year's OACS welcomes talk submissions from a variety of topics, from Using Standard Language Parallelism to Computer Vision Applications. The document also highlights several open hackathons, a call to apply for NVIDIA Academic Grant Program and resources for optimizing scientific applications using OpenACC directives.WebdriverIO & JavaScript: The Perfect Duo for Web Automation
WebdriverIO & JavaScript: The Perfect Duo for Web Automationdigitaljignect
油
In todays dynamic digital landscape, ensuring the quality and dependability of web applications is essential. While Selenium has been a longstanding solution for automating browser tasks, the integration of WebdriverIO (WDIO) with Selenium and JavaScript marks a significant advancement in automation testing. WDIO enhances the testing process by offering a robust interface that improves test creation, execution, and management. This amalgamation capitalizes on the strengths of both tools, leveraging Seleniums broad browser support and WDIOs modern, efficient approach to test automation. As automation testing becomes increasingly vital for faster development cycles and superior software releases, WDIO emerges as a versatile framework, particularly potent when paired with JavaScript, making it a preferred choice for contemporary testing teams.Hyderabad MuleSoft In-Person Meetup (June 21, 2025) 際際滷s
Hyderabad MuleSoft In-Person Meetup (June 21, 2025) 際際滷sRavi Tamada
油
Hyderabad MuleSoft In-Person Meetup (June 21, 2025) 際際滷s9-1-1 Addressing: End-to-End Automation Using FME
9-1-1 Addressing: End-to-End Automation Using FMESafe Software
油
This session will cover a common use case for local and state/provincial governments who create and/or maintain their 9-1-1 addressing data, particularly address points and road centerlines. In this session, you'll learn how FME has helped Shelby County 9-1-1 (TN) automate the 9-1-1 addressing process; including automatically assigning attributes from disparate sources, on-the-fly QAQC of said data, and reporting. The FME logic that this presentation will cover includes: Table joins using attributes and geometry, Looping in custom transformers, Working with lists and Change detection.Securing Account Lifecycles in the Age of Deepfakes.pptx
Securing Account Lifecycles in the Age of Deepfakes.pptxFIDO Alliance
油
Securing Account Lifecycles in the Age of DeepfakesSecurity Tips for Enterprise Azure Solutions
Security Tips for Enterprise Azure SolutionsMichele Leroux Bustamante
油
Delivering solutions to Azure may involve a variety of architecture patterns involving your applications, APIs data and associated Azure resources that comprise the solution. This session will use reference architectures to illustrate the security considerations to protect your Azure resources and data, how to achieve Zero Trust, and why it matters. Topics covered will include specific security recommendations for types Azure resources and related network security practices. The goal is to give you a breadth of understanding as to typical security requirements to meet compliance and security controls in an enterprise solution.2025_06_18 - OpenMetadata Community Meeting.pdf
2025_06_18 - OpenMetadata Community Meeting.pdfOpenMetadata
油
The community meetup was held Wednesday June 18, 2025 @ 9:00 AM PST.
Catch the next OpenMetadata Community Meetup @ https://www.meetup.com/openmetadata-meetup-group/
In this month's OpenMetadata Community Meetup, "Enforcing Quality & SLAs with OpenMetadata Data Contracts," we covered data contracts, why they matter, and how to implement them in OpenMetadata to increase the quality of your data assets!
Agenda Highlights:
Introducing Data Contracts: An agreement between data producers and consumers
Data Contracts key components: Understanding a contract and its purpose
ｨ Writing your first contract: How to create your own contracts in OpenMetadata
An OpenMetadata MCP Server update!
And More!Connecting Data and Intelligence: The Role of FME in Machine Learning
Connecting Data and Intelligence: The Role of FME in Machine LearningSafe Software
油
In this presentation, we want to explore powerful data integration and preparation for Machine Learning. FME is known for its ability to manipulate and transform geospatial data, connecting diverse data sources into efficient and automated workflows. By integrating FME with Machine Learning techniques, it is possible to transform raw data into valuable insights faster and more accurately, enabling intelligent analysis and data-driven decision making.The Future of Product Management in AI ERA.pdf
The Future of Product Management in AI ERA.pdfAlyona Owens
油
Hi, Im Aly Owens, I have a special pleasure to stand here as over a decade ago I graduated from CityU as an international student with an MBA program. I enjoyed the diversity of the school, ability to work and study, the network that came with being here, and of course the price tag for students here has always been more affordable than most around.
Since then I have worked for major corporations like T-Mobile and Microsoft and many more, and I have founded a startup. I've also been teaching product management to ensure my students save time and money to get to the same level as me faster avoiding popular mistakes. Today as Ive transitioned to teaching and focusing on the startup, I hear everybody being concerned about Ai stealing their jobs Well talk about it shortly.
But before that, I want to take you back to 1997. One of my favorite movies is Fifth Element. It wowed me with futuristic predictions when I was a kid and Im impressed by the number of these predictions that have already come true. Self-driving cars, video calls and smart TV, personalized ads and identity scanning. Sci-fi movies and books gave us many ideas and some are being implemented as we speak. But we often get ahead of ourselves:
Flying cars,Colonized planets, Human-like AI: not yet, Time travel, Mind-machine neural interfaces for everyone: Only in experimental stages (e.g. Neuralink).
Cyberpunk dystopias: Some vibes (neon signs + inequality + surveillance), but not total dystopia (thankfully).
On the bright side, we predict that the working hours should drop as Ai becomes our helper and there shouldnt be a need to work 8 hours/day. Nobody knows for sure but we can require that from legislation. Instead of waiting to see what the government and billionaires come up with, I say we should design our own future.
So, we as humans, when we dont know something - fear takes over. The same thing happened during the industrial revolution. In the Industrial Era, machines didnt steal jobsthey transformed them but people were scared about their jobs. The AI era is making similar changes except it feels like robots will take the center stage instead of a human. First off, even when it comes to the hottest space in the military - drones, Ai does a fraction of work. AI algorithms enable real-time decision-making, obstacle avoidance, and mission optimization making drones far more autonomous and capable than traditional remote-controlled aircraft. Key technologies include computer vision for object detection, GPS-enhanced navigation, and neural networks for learning and adaptation. But guess what? There are only 2 companies right now that utilize Ai in drones to make autonomous decisions - Skydio and DJI.
Salesforce Summer '25 Release Frenchgathering.pptx.pdf
Salesforce Summer '25 Release Frenchgathering.pptx.pdfyosra Saidani
油
Salesforce Summer '25 Release Frenchgathering.pptx.pdfAd
Multiple Business Analyst Views in Agile
- 1. Iteration Start 1 2 3 4 5 Days (Iteration View) IPM Showcase RetrospectiveStand-up Kick-off, Volleyball, Pre-IPM Iteration End Day Start Day End i-2 i-1 i+1 Iterations (Release View) Pre-IPM i IPM Showcase Retrospective End Inputs to next iteration(s) Start Inputs from previous iteration(s) Stand-up Stories (Day View) Day Start Day End Pre stand- up work Updating Wall Sign-ups Story n Kick-off Story m Volleyball Story o Kick-off Story p questions Stories a , b , c analysis Dev Huddle Pre-IPM conversations QA questions Multiple Business Analyst Views in Agile
- 2. Product Backlog Release Backlog Pre-IPM Iteration Backlog IPM Kick-off In Dev Questions Volleyball QA Done Done Showcase + UAT Feedback Prioritization Release Planning Story Sequencing Analysis Story Sign-offs Iteration Start Pairing Sign-ups Follow ups DevelopmentDev Huddles Development Testing Prep for Showcase Acceptance Iteration Close Incorporate Story Lifecycle