This document outlines an Agile planning and estimating workshop presented by Joshua Partogi. The workshop covers Scrum concepts like timeboxing, product backlog creation and ordering, estimating work in story points, sprint planning, and monitoring progress via burn down charts and velocity. Participants work through exercises to practice these techniques in planning and estimating the work for a mobile tourism app project over multiple sprints and releases.
This document advertises the Web of the Future and provides a rubric to assess skill levels in using chosen software programs. The rubric contains 10 criteria to evaluate planning and organization, addressing criteria, creativity and originality, presentation, and workload distribution. Skill levels range from 1 (no skill) to 5 (advanced skills and planning).
iCompass - Imagineer the possibilities, Realize your potentialSatya Chari
"iCompass" - Imagineering one\'s potential with the confluence of information, collaboration, cooperation, participation and motivation enabled by technology....supported by commerce, if so desired.
This company profile document provides information about an animation and game development company. It discusses the company's services, team size and experience, infrastructure including a render farm and network, research and development areas, communication policies, current and upcoming projects, and examples of character, environment, and asset concepts for an animated feature film project. The document contains visual examples and concepts to support the descriptions.
The document discusses designing user experiences to move beyond usability and functionality to create experiences that are meaningful, pleasurable, and memorable. It presents the User Experience Curve model which outlines a hierarchy of needs from basic tasks to more subjective experiences involving aesthetics, flow, and emotional engagement. The goal is to cross the "chasm" from task-focused design to experience-focused design that brings joy and excitement to users.
The document discusses designing user experiences and outlines 7 principles for creating optimal experiences:
1. Create a great first impression with attractive design.
2. Provide attentive service that anticipates user needs.
3. Allow for personalization and customization.
4. Pay attention to details.
5. Provide feedback to prevent frustration and manage expectations.
6. Make the experience fun through things like points and leaderboards.
7. Craft an environment like Starbucks or Virgin that enhances the overall experience.
The document discusses planning a software release using user stories, including introducing the concept of user stories, sizing stories, prioritizing stories, identifying value drivers and themes in the backlog of stories, calculating return on investment, and identifying non-functional requirements. The goal is to provide guidance on effectively organizing a backlog of user stories to plan a successful software release.
Applying DevOps from the Mobile to the MainframeCA Technologies
As part of key IT initiatives to improve customer experience, reduce IT costs, ensure compliance and increase reliability, Akbank took on an audacious project to apply DevOps principles and an Agile approach as standard across all of the bank's applications, including customer-facing, branch infrastructure, multi-channel architecture and mainframe areas. Building a tool chain that covers project initiation through to deployment in production in such a complex environment is a challenging task. Akbank chose to link its existing toolset using CA Release Automation as a Continuous Delivery backbone, with CA Harvest and CA Endevor to manage source code, build and package tasks. This session will explore the vision to improve the development cycle, as well as the requirements for the project, and ultimately the benefits being realized.
For more information, please visit http://cainc.to/Nv2VOe
This document advertises the Web of the Future and provides a rubric to assess skill levels in using chosen software programs. The rubric contains 10 criteria to evaluate planning and organization, addressing criteria, creativity and originality, presentation, and workload distribution. Skill levels range from 1 (no skill) to 5 (advanced skills and planning).
iCompass - Imagineer the possibilities, Realize your potentialSatya Chari
"iCompass" - Imagineering one\'s potential with the confluence of information, collaboration, cooperation, participation and motivation enabled by technology....supported by commerce, if so desired.
This company profile document provides information about an animation and game development company. It discusses the company's services, team size and experience, infrastructure including a render farm and network, research and development areas, communication policies, current and upcoming projects, and examples of character, environment, and asset concepts for an animated feature film project. The document contains visual examples and concepts to support the descriptions.
The document discusses designing user experiences to move beyond usability and functionality to create experiences that are meaningful, pleasurable, and memorable. It presents the User Experience Curve model which outlines a hierarchy of needs from basic tasks to more subjective experiences involving aesthetics, flow, and emotional engagement. The goal is to cross the "chasm" from task-focused design to experience-focused design that brings joy and excitement to users.
The document discusses designing user experiences and outlines 7 principles for creating optimal experiences:
1. Create a great first impression with attractive design.
2. Provide attentive service that anticipates user needs.
3. Allow for personalization and customization.
4. Pay attention to details.
5. Provide feedback to prevent frustration and manage expectations.
6. Make the experience fun through things like points and leaderboards.
7. Craft an environment like Starbucks or Virgin that enhances the overall experience.
The document discusses planning a software release using user stories, including introducing the concept of user stories, sizing stories, prioritizing stories, identifying value drivers and themes in the backlog of stories, calculating return on investment, and identifying non-functional requirements. The goal is to provide guidance on effectively organizing a backlog of user stories to plan a successful software release.
Applying DevOps from the Mobile to the MainframeCA Technologies
As part of key IT initiatives to improve customer experience, reduce IT costs, ensure compliance and increase reliability, Akbank took on an audacious project to apply DevOps principles and an Agile approach as standard across all of the bank's applications, including customer-facing, branch infrastructure, multi-channel architecture and mainframe areas. Building a tool chain that covers project initiation through to deployment in production in such a complex environment is a challenging task. Akbank chose to link its existing toolset using CA Release Automation as a Continuous Delivery backbone, with CA Harvest and CA Endevor to manage source code, build and package tasks. This session will explore the vision to improve the development cycle, as well as the requirements for the project, and ultimately the benefits being realized.
For more information, please visit http://cainc.to/Nv2VOe
Continuous integration and delivery with Xamarin and VSTSGill Cleeren
The document discusses using Visual Studio Team Services (VSTS) and Xamarin for mobile DevOps. It covers setting up a VSTS project and configuring continuous integration for iOS and Android apps. Unit testing is integrated into the build pipeline. Test Cloud is used to test apps on multiple devices. HockeyApp is used to deploy builds to testers and monitor crashes and feedback. The goal is to streamline the mobile app development process through continuous integration, delivery, and monitoring.
This document discusses the role of an architect in agile development. It compares waterfall and agile architecture approaches. The architect's responsibilities in agile include incrementally documenting designs, communicating with the team, embracing change, and removing impediments. Best practices for agile architecture include inviting peer review, challenging assumptions, and learning from mistakes. The architect must understand coding and know how to work with people as technology alone is not enough.
Agile planning with Rational Team Concert (RTC) workshop provides tip for agile team to successfully use RTC to support for the three innermost levels of Mike Cohn's planning onion: product, release and sprint / iteration planning. RTC also provides extensive support source code management and integration to CI build and automated release deployment tools such as UrbanCode Deploy
For more information see https://jazz.net/library/article/593
Details
Rational Team Concert (RTC) provides a lightweight tool to help project teams plan, executing and monitor agile, waterfall and scaled agile development projects (such as Scrum, Scrum of Scrums, Disciplined Agile Delivery - DAD, or Scaled Agile Framework - SAFe.
For agile projects / programs, RTC provides tools to create product, release and sprint backlogs for teams, to create individual plans for developers, and to track the progress during an iteration and to balance the work load of developers.
For waterfall projects / programs, RTC provides development teams with traditional project management capabilities such as work breakdown structures, schedule dependencies, constraints and Gantt charts.
This document discusses refactoring, which involves restructuring existing code without changing its external behavior or functionality. It provides definitions of refactoring and describes best practices for refactoring code, such as taking small, incremental steps and verifying that automated tests still pass after each change. Specific refactoring techniques are also explained, like extracting duplicate code into methods, removing unnecessary complexity or duplication, and consolidating conditional expressions for clarity. The document cautions against fixing bugs during refactoring and emphasizes making changes in a way that simplifies the code and removes code smells.
Strategic human resource planning. Human resources planning is a process that identifies current and future human resources needs for an organization to achieve its goals. Human resources planning should serve as a link between human resources management and the overall strategic plan of an organization.
The document introduces Scrum and its roles, artifacts, and activities. It discusses the Scrum process including sprint planning, daily standups, sprint demos, and retrospectives. It emphasizes that teams should strictly follow Scrum practices like having a product backlog, sprint backlog, and definition of done to achieve the benefits of an agile framework. Failing to properly implement Scrum can undermine its effectiveness.
Bringing User-CenteredDesign Practices intoAgile Development Projectsabcd82
The document discusses bringing user-centered design practices into agile development projects. It outlines an agenda for a workshop on this topic, including discussions of the agile development context, project inception and planning, building and validation, and adapting practices. The workshop will cover modeling business goals and users, aligning user research with agile processes, and leveraging information radiators. Releasing software incrementally can increase return on investment by starting to generate value earlier.
- Scrum is an agile framework for managing complex projects using short development cycles ("sprints"), regular inspection of progress, and adaptation to change. It emphasizes communication, collaboration, and incremental delivery of work.
- Key Scrum roles include the Product Owner who prioritizes features, the Development Team who implements them, and the Scrum Master who facilitates the process.
- Core Scrum activities are Sprint Planning meetings, Daily Scrums, Sprint Reviews, and Sprint Retrospectives, which focus the team and enable inspection and adaptation.
- The Product Backlog contains prioritized features and the Sprint Backlog contains work for the current Sprint. A Burn Down Chart tracks progress. Scrum
This document discusses managing agile projects using Scrum. It provides an overview of Scrum, including common roles, artifacts, and events like sprints, sprint planning, daily scrums, sprint reviews, and retrospectives. It also discusses how project management practices from PMBOK like scope, schedule, cost can be addressed in Scrum, with the product backlog, release planning, and tracking work remaining. The document aims to explain how to use Scrum for managing agile software development projects.
Inflectica Technologies a web development company provides professional services of: web application development, ecommerce website design and programming, dedicated teams of web developers with high quality, affordable cost and timely delivery.
The document discusses adopting agile practices at an enterprise scale. It begins with an overview of agile principles and how Scrum is commonly used for teams. However, scaling agile to larger companies presents challenges related to management roles, technical specifications, and global collaboration. The Scaled Agile Framework addresses these challenges through features like program increment planning that synchronize work across many teams. Case studies show companies achieving benefits like increased productivity, faster issue resolution, and lower costs when using scaled agile frameworks.
Agile From the Top Down: Executives & Leadership Living Agile by Jon StahlLeanDog
The document summarizes a presentation by Jon R. Stahl on getting executive leadership and organizations to practice agile principles from the top down. It discusses how most agile movements are not sustainable because they fail to change culture and establish a process. It advocates that leadership must live the values of agility, seek to understand their unique culture, and be transparent. It also provides examples of information radiators that can help visualize work, values, projects and assets to establish transparency and shared understanding.
Continuous integration and delivery with Xamarin and VSTSGill Cleeren
The document discusses using Visual Studio Team Services (VSTS) and Xamarin for mobile DevOps. It covers setting up a VSTS project and configuring continuous integration for iOS and Android apps. Unit testing is integrated into the build pipeline. Test Cloud is used to test apps on multiple devices. HockeyApp is used to deploy builds to testers and monitor crashes and feedback. The goal is to streamline the mobile app development process through continuous integration, delivery, and monitoring.
This document discusses the role of an architect in agile development. It compares waterfall and agile architecture approaches. The architect's responsibilities in agile include incrementally documenting designs, communicating with the team, embracing change, and removing impediments. Best practices for agile architecture include inviting peer review, challenging assumptions, and learning from mistakes. The architect must understand coding and know how to work with people as technology alone is not enough.
Agile planning with Rational Team Concert (RTC) workshop provides tip for agile team to successfully use RTC to support for the three innermost levels of Mike Cohn's planning onion: product, release and sprint / iteration planning. RTC also provides extensive support source code management and integration to CI build and automated release deployment tools such as UrbanCode Deploy
For more information see https://jazz.net/library/article/593
Details
Rational Team Concert (RTC) provides a lightweight tool to help project teams plan, executing and monitor agile, waterfall and scaled agile development projects (such as Scrum, Scrum of Scrums, Disciplined Agile Delivery - DAD, or Scaled Agile Framework - SAFe.
For agile projects / programs, RTC provides tools to create product, release and sprint backlogs for teams, to create individual plans for developers, and to track the progress during an iteration and to balance the work load of developers.
For waterfall projects / programs, RTC provides development teams with traditional project management capabilities such as work breakdown structures, schedule dependencies, constraints and Gantt charts.
This document discusses refactoring, which involves restructuring existing code without changing its external behavior or functionality. It provides definitions of refactoring and describes best practices for refactoring code, such as taking small, incremental steps and verifying that automated tests still pass after each change. Specific refactoring techniques are also explained, like extracting duplicate code into methods, removing unnecessary complexity or duplication, and consolidating conditional expressions for clarity. The document cautions against fixing bugs during refactoring and emphasizes making changes in a way that simplifies the code and removes code smells.
Strategic human resource planning. Human resources planning is a process that identifies current and future human resources needs for an organization to achieve its goals. Human resources planning should serve as a link between human resources management and the overall strategic plan of an organization.
The document introduces Scrum and its roles, artifacts, and activities. It discusses the Scrum process including sprint planning, daily standups, sprint demos, and retrospectives. It emphasizes that teams should strictly follow Scrum practices like having a product backlog, sprint backlog, and definition of done to achieve the benefits of an agile framework. Failing to properly implement Scrum can undermine its effectiveness.
Bringing User-CenteredDesign Practices intoAgile Development Projectsabcd82
The document discusses bringing user-centered design practices into agile development projects. It outlines an agenda for a workshop on this topic, including discussions of the agile development context, project inception and planning, building and validation, and adapting practices. The workshop will cover modeling business goals and users, aligning user research with agile processes, and leveraging information radiators. Releasing software incrementally can increase return on investment by starting to generate value earlier.
- Scrum is an agile framework for managing complex projects using short development cycles ("sprints"), regular inspection of progress, and adaptation to change. It emphasizes communication, collaboration, and incremental delivery of work.
- Key Scrum roles include the Product Owner who prioritizes features, the Development Team who implements them, and the Scrum Master who facilitates the process.
- Core Scrum activities are Sprint Planning meetings, Daily Scrums, Sprint Reviews, and Sprint Retrospectives, which focus the team and enable inspection and adaptation.
- The Product Backlog contains prioritized features and the Sprint Backlog contains work for the current Sprint. A Burn Down Chart tracks progress. Scrum
This document discusses managing agile projects using Scrum. It provides an overview of Scrum, including common roles, artifacts, and events like sprints, sprint planning, daily scrums, sprint reviews, and retrospectives. It also discusses how project management practices from PMBOK like scope, schedule, cost can be addressed in Scrum, with the product backlog, release planning, and tracking work remaining. The document aims to explain how to use Scrum for managing agile software development projects.
Inflectica Technologies a web development company provides professional services of: web application development, ecommerce website design and programming, dedicated teams of web developers with high quality, affordable cost and timely delivery.
The document discusses adopting agile practices at an enterprise scale. It begins with an overview of agile principles and how Scrum is commonly used for teams. However, scaling agile to larger companies presents challenges related to management roles, technical specifications, and global collaboration. The Scaled Agile Framework addresses these challenges through features like program increment planning that synchronize work across many teams. Case studies show companies achieving benefits like increased productivity, faster issue resolution, and lower costs when using scaled agile frameworks.
Agile From the Top Down: Executives & Leadership Living Agile by Jon StahlLeanDog
The document summarizes a presentation by Jon R. Stahl on getting executive leadership and organizations to practice agile principles from the top down. It discusses how most agile movements are not sustainable because they fail to change culture and establish a process. It advocates that leadership must live the values of agility, seek to understand their unique culture, and be transparent. It also provides examples of information radiators that can help visualize work, values, projects and assets to establish transparency and shared understanding.
Gcsv2011 using career portfolios-anna graf williams and emily sellersServe Indiana
The document discusses using career portfolios to document community service experience and transferable skills. It describes the basic components of a career portfolio, including a professional bio, resume, work samples, references, and documentation of community service, degrees and awards. Employers are increasingly interested in soft skills gained through community service, such as leadership, customer service, and problem solving. The document provides suggestions for requesting documentation from community service organizations to include in a portfolio as evidence of skills and competencies. It also discusses using apps and social media to track community service hours and increase impact.
Distributed Agile - Symbiosis or Antagonism?
A white paper recently presented at an Agile meetup with focus a on distributed agile misconceptions, barriers, patterns and antipatterns, culture-structure-practices model with industry case studies.
Embedding a Scrum culture avec Harvey Wheaton, Scrum AllianceXavier Warzee
Harvey Wheaton has experience in various industries including pharmaceuticals, retail banking, consulting, and investment banking. He joined Electronic Arts in 2003 where he first encountered scrum-like environments. He discovered scrum in 2005 and took a class in 2006. In 2008, he started his own games development studio called Supermassive Games and has been embedding scrum practices since. The key elements of scrum for the studio include two-week sprints, cross-discipline teams, physical planning, and daily stand-ups. The studio focuses on rapid iteration, making software the priority, and continually inspecting and adapting their processes.
This document provides contact information for Richard Cheng, an agile trainer and coach who has experience leading agile transformations in government and commercial organizations, and lists his credentials including certifications in Scrum, SAFe, LeSS, and project management from organizations like PMI, Scrum Alliance, and Agile Alliance. It also includes his email, phone number, LinkedIn profile, and Twitter handle to facilitate contacting him.
Harvey Wheaton spoke at ProductTank October 2011 and shared his experiences of building and running Agile teams at his games studio Supermassive Games.
The document outlines the design process used by Motivitylabs, which includes 5 stages: 1) Brief, 2) Research, 3) Concept, 4) Design, and 5) Launch. It provides details about each stage and the key activities involved such as creating personas and wireframes in the concept stage, visual mockups and design evaluations in the design stage, and A/B testing and beta launches in the launch stage. The overall process is intended to help Motivitylabs thoroughly understand users, develop concepts that meet user needs, design effective interfaces, and launch products through user testing.
This document discusses three key challenges to scaling agile adoption: distributed teams, hybrid projects, and scaling agile in general. It provides advice on overcoming these challenges, including establishing clear communication for distributed teams, creating a hybrid project management office to manage both agile and non-agile teams, and ensuring the right organizational culture and support is in place for large-scale agile transformation. Polls are included to gauge attendees' experience with these topics.
Ken Schwaber chez Microsoft pour le French Scrum User GroupXavier Warzee
Scrum.org helps organizations adopt Scrum through maintaining bodies of knowledge on Scrum practices, developing training materials, and creating assessments to evaluate competence. It focuses on spreading the use of Scrum to improve software development and address common problems through certifying Scrum practitioners and developers in modern engineering practices.
Mindmaps: Agile and Lightweight Documentation for TestingTechWell
Quality starts with requirements. In small to mid-size companies, it is not uncommon for the communication chain to be broken. Florin Ursu shares ways to avoid miscommunication through a streamlined process in which requirements are communicated to both developers and testers simultaneously; then developers write code while testers document what will be tested. Florin explores what mindmaps are; what they can be used for, both in general and applied to software development; and then dives deeper into how mindmaps can be used for testing. He describes how his teams use mindmaps to brainstorm, organize testing scenarios, prioritize work, review test scenarios, present results to stakeholders highlighting what was tested and—just as importantly—what was not tested, issues found, and risks. Using example mindmaps, Florin highlights important details captured in day to day work, including tips regarding format, communication style, and how to “sell” the idea of mindmaps to your stakeholders.
Programming agents without a programming languageAryan Rathore
Programming Agents without a Programming Language
Agents have the potential to actively participate in accomplishing tasks, rather than serving as passive tools as do today's applications.
However, people do not want generic agents--they want help with their jobs, their tasks, their goals.
Agents must be flexible enough to be tailored to each individual.
The most flexible way to tailor a software entity is to program it.
The problem is that programming is too difficult for most people today.
The document discusses the Agile development methodology and Scrum framework, describing Waterfall and its limitations, the core principles of Agile which value collaboration and working software over documentation, and how Scrum is implemented at W3i through user stories, estimating, daily standups, burndowns, sprint reviews and retrospectives.
In the world of agile, there is theory and then there is practice. We like to talk about self-organizing teams, asynchronous execution, BDD, TDD, and emergent architecture. We also talk about cross-functional teams: how analysts, testers, architects, technical writers, and UX designers belong on the same team, right next to programmers. It all sounds nice in theory, but how does this work in reality? What do these people actually do? How do they interact? What does it look like? Is there really a pragmatic way to make this work?
In this simulation, a cross-functional team will actually build a piece of software. Every specialist will have a hand in the process. Every specialist will also act as a generalist. Everyone will add value. And as a team, we’ll get something DONE.
This is your opportunity to see agile development in practice, and to bridge the gap between what agilists say and what teams do. And it’s not as new or as difficult as you think – affinity between testers, BA’s, coders, and other team members has really been at the root of effective development practices all along. Let’s just finally acknowledge that it works, demonstrate its capabilities, and encourage it going forward.
This IS agile development.
PowerPoint presentation on Agile software development and Scrum. First and foremost it´s not about tools or processes. It´s about the mindset needed to be successful in delivering valuable software to the customer
Intro to Scrum for Software Development TeamAna Pegan
Here are the steps to break down a user story into a sprint backlog:
1. The product owner presents the user story to the team:
"As a vacation planner, I want to see potential destinations on a map so I can pick a location."
2. The team discusses what needs to be done to implement the story and breaks it into specific tasks:
- Design database schema for destinations
- Create destinations table
- Add sample destinations to database
- Design map view UI
- Integrate map view into app
- Display destinations on map
3. Estimates are made for each task. Tasks are ordered and pulled into the sprint backlog based on priority, dependencies, and team
Vladimirs Ivanovs IPMA GYCW2013 Agile - traditional or balanced mixVladimirs Ivanovs
Vladimirs Ivanovs, IPMA GYCW2013 Dubrovnik Croatia, interactive workshop/game "Agile - traditional or balanced mix" or "Creating children's book with SCRUM".
About trainer:
Vladimirs is consultant and trainer in Project Management and IT Service Management, IPMA-B and ITIL Expert certified. Board member at IPMA Latvia, assessor, developing Young Crew group. Teaching Programme and Project Portfolio Management for masters in Project Management. Has a degree in Computer Sciences and Executive MBA from Stockholm School of Economics. Worked for large telecoms and as CIO for global retail chain. Owner of ITSM LLC, company that is solving IT and Project Management issues, providing consulting and trainings, CIOs and PMs for rent. Have been recently speaking on global TFT12 conference, regional Agile and Project Management events.
This document discusses human aspects in Scrum. It summarizes the Agile Manifesto values, emphasizing individuals, interactions, working software, customer collaboration, and responding to change. The essence of Scrum is the team making commitments and delivering valuable features regularly through self-organization and transparency. Core Scrum values include commitment, team spirit, respect, trust, and courage. Scrum provides a simple framework using basic tenets to solve complex problems faster. The Scrum roles are the Scrum Master, Product Owner, and self-organizing team.
Similar to Agile planning & estimating joshua partogi (20)
The document summarizes DevOps Day 2013 that was held in Silicon Valley from June 21-22, 2013. It provides details about the event location, participants, sessions covered, and goals of attending. Specifically, it discusses learning about DevOps practices, differences from agile development, and continuous quality approaches in a community-focused event with presentations from consulting and solution providers.
The document summarizes a conference called Velocity 2013 Conference. It provides details about:
- The purpose of attending the conference was to learn about reference architectures for build/deployment systems, monitoring, and mobile deployment.
- The conference covered topics like mobile performance, operations, and web performance. It included technical sessions on solving performance and operational issues in large-scale environments.
- Some of the sessions discussed tools for packaging, log collection, monitoring metrics, testing methods, lessons learned from projects, and scaling load balancing infrastructure to over a billion users.
The document discusses the concept of "unicorns" in software innovation. It defines unicorns as people who can perform multiple specialty functions and solve a broad set of problems for their team. It explains that many startups are desperately seeking "unicorns" due to changes in software development that require more cross-functional skills. It outlines eight attributes of standout tech companies, including having empathy for customers, making opinionated products, learning quickly through doing rather than textbooks, and being good communicators. The document argues that success in software innovation is now defined more by cultural fit and attitude than specific skills or educational background.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
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.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
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.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Agile planning & estimating joshua partogi
1. Scrum Planning and Estimating Workshop
Joshua Partogi
@jpartogi
Agile Korea Conference 2012
Scrum.org - Improving the Profession of Software Development
2. Who Am I? 안녕
• Professional Scrum Trainer through Scrum.org
• Scrum Indonesia 인도네시아 community founder
• K-pop 가요 and Korean drama 한국드라마 avid and Korean food lover
Scrum.org - Improving the Profession of Software Development
3. The rule of the game
5
• Every events in Scrum have timebox mins
• We are going to do many discussions and exercises in groups
• Every discussions and exercises will have timebox
This shows the timebox
Scrum.org - Improving the Profession of Software Development
4. Team Forming and Discussion
5
Form a group of 5 and discuss these questions mins
• Give your team a name
Scrum.org - Improving the Profession of Software Development
5. How do we answer these questions?
• When is the project is going to finish?
• How much is the project going to co$t?
Scrum.org - Improving the Profession of Software Development
6. Today we are going to learn about estimating and
planning in Scrum
cises
Wit h joyful exer
y
along the wa
Scrum.org - Improving the Profession of Software Development
7. Group Estimation
In Scrum, estimation is only done by group of people who will be committing to
do the work.
Everyb
e o
eads ar own o dy have thei
Two h e p
solid p inions of how
r
than on
better roduct
should a
By getting many opinions from be
many different people we can
have many alternatives that can
be systematically evaluated
ore
People are m ork
committe d with the w
by
that are estimated
themselves
Scrum.org - Improving the Profession of Software Development
8. The Myth
With more analysis and
effort, estimates get
significantly more accurate.
Scrum.org - Improving the Profession of Software Development
9. Estimation is often Expensive
Accuracy'
Effort'or'Time'
Scrum.org - Improving the Profession of Software Development
10. The Basic Truths
• It doesn’t matter how long you do the planning and estimate, if you don’t have all
the skills required you may still come up with a bad plan.
• The best way to predict the future is not to come up with detailed analysis but to
invent it and inspect the outcome.
• It is important to have cross-functional team to come up with good estimate
otherwise you have a dysfunctional team.
Scrum.org - Improving the Profession of Software Development
11. Levels of Planning in Scrum
• Sprint Planning is just first step
• Plan constantly, not just in the beginning
• Planning is an activity, not a document
• Recognize, embrace, and support Release Sprint Daily
Planning Planning Planning
change rather than trying to control it
Scrum.org - Improving the Profession of Software Development
12. Visit Korea Mobile Apps
To support the Visit Korea program, the Korea Tourism Organisation want to make
a location based mobile apps that will help tourists find notable places in Korea.
• Tourist should be able to search and make an online • The system should handle internationalization as many
both from browser and mobile app booking for all types tourists from all over the world will be using this
of accomodation (i.e Hotel, Budget, Homestay) in Korea. application.
• Tourist should be able to rate and give a comment for • The web application should be viewable on major
the accomodation they have stayed in. browsers.
• Tourist should be able to search other members who • The apps should support mobile web and native mobile
offers their service as tourist guide. apps as well as desktop web.
• Tourist should be able to give an online financial reward • The system should be scalable for up to 100,000 users
and give a recommendation for these tourist guides. and available 24/7.
• Tourist should be able to find nearby notable restaurants • The system should be secure as there will be some
and places to visit from their mobile phone. transaction involved.
• Tourist should be able to rate and give a comment for
the restaurants and places they have visited.
Scrum.org - Improving the Profession of Software Development
13. The Plan
• The KTO virtually has unlimited funding for this project but would prefer something
is released as soon as possible so that users can use it and give feedback about the
apps.
• Today is the September 1st. KTO plan to have the first release on December 1st
right before Christmas.
• The first release should be the minimum viable product with core functionalities and
should at least support one mobile platform.
• If the core functionalities is not available, user will not use the product and the
project will be a loss.
• The second release is planned for March 1st should at least support another mobile
platform and have more functionalities.
Scrum.org - Improving the Profession of Software Development
14. The Release Planning Exercise
Scrum.org - Improving the Profession of Software Development
15. Creating the Product Backlog for December 1st Release
15
• Create a Product Backlog for December 1st Release ( 3 Sprints ) mins
• Just make sure you have enough work until December 1st, you don’t
have to create the Product Backlog for the whole product.
• Create a card for each Product Backlog Item / work item
• Do not strive for perfection, just the best you can do
Scrum.org - Improving the Profession of Software Development
16. Product Backlog Ordering 순서
• A Product Backlog layout a roadmap for the product so that everyone can see
the vision for the product itself.
1st Quarter 2nd Quarter 2nd Half-year The future
1st Sprint
If we still
have money
and
everything is
2nd & 3rd Sprint
going well
Scrum.org - Improving the Profession of Software Development
17. Ordering 순서 the Product Backlog
15
• Order the Product Backlog so that everyone can see what Product Backlog mins
Item will be done first and what will be done last.
• Put the relative value number on each card. Assume that you will use the
number 1-500 No two PBI can have the same value number.
• The system will be unusable if the non-functionality requirements are not
fulfilled.
• New PBI may emerge.
1 10 20 30 40 50 100 500
2 21 41
Scrum.org - Improving the Profession of Software Development
18. Estimating Product Backlog Items with Points
• Very common way to estimate work • Points are additive
• Based on size and complexity, not • Based on historical reality
duration or man hours • Easy to use and understand
• Unitless and numerically relative
• Different for each team of estimators
Scrum.org - Improving the Profession of Software Development
19. Estimating with Points
∞ : not feasible for
8 ? 8 the time being
? : still unclear
Product Backlog 0 : it is already
Item supported by the
8 system
4
2
Scrum.org - Improving the Profession of Software Development
20. Estimating 평가 the size of Product Backlog Item
15
• We are going to play Planning Poker cards. The number describe the size mins
or effort (not man hours) to implement the PBI.
• Select the PBI that have a medium relative size and assign it a 4.
• Put the PBI that are relatively easier on the left hand side and the PBI that
are relatively more difficult on the right hand side of the medium PBI.
• Now estimate the PBI as a group.
• Each estimator selects a card that’s his or her estimate.
• Cards are turned over so all can see them (synchronously).
• Don’t broadcast opinion before the cards are turned over.
• Re-estimate until estimates converge.
Scrum.org - Improving the Profession of Software Development
21. The Sprint Planning Exercise
Scrum.org - Improving the Profession of Software Development
22. Sprint Planning
• In Scrum, Sprint Planning is divided into two parts.
• In the first part, the purpose is to discuss what to make. The Sprint Goal is
crafted.
• In the second part, the purpose is to discuss how to implement the selected
Product Backlog Item from the first part. The output is the Sprint Backlog
Scrum.org - Improving the Profession of Software Development
23. Sprint Planning Part 1
15
• There are three 1 month Sprints until December 1st. mins
• Your team has worked together before and based on historical data your
team is only able to deliver 16 points of work in one month Sprint.
• Based on the ordered Product Backlog, select the Product Backlog Items
for the 1st Sprint.
• If the PBIs are too large, you may need to decompose the PBIs into
several smaller items so that it fits in one Sprint.
• Tear apart the cards that are no longer used to prevent confusion.
• From the selected Product Backlog Items, define the Sprint goal
Scrum.org - Improving the Profession of Software Development
24. Sprint Planning Part 2
15
• Now that we have selected the PBIs for the first Sprint we are going to mins
define the works to implement the PBIs
• For each PBIs, define the tasks needed to be done.
• Each tasks may not exceed more than one day to accomplish.
• Tasks may include several functions such as design, programming, quality
control, documentation
• Write each tasks on one sticky.
• Write the number of hours needed for each tasks.
Scrum.org - Improving the Profession of Software Development
25. Scrum Board
Put these Sprint Backlog to be visible for everyone to see so that everyone knows
what needs to be done during the Sprint
PBI TODO In Progress Done
Scrum.org - Improving the Profession of Software Development
26. Monitoring Sprint Progress
• Scrum suggests that the team
150
has a tool to monitor progress
towards the end of the Sprint
112.5
• Sprint Burndown chart is one of
75
the tool
• The metric can be number of
37.5
remaining hours, remaining tasks
or remaining points
0
• This is updated daily usually after
1 2 3 4 5 6 7 8 9 10
Daily Scrum Meeting
Scrum.org - Improving the Profession of Software Development
27. Velocity
• Velocity 속도 is the capacity 용적 of how much the team can do in one Sprint.
• Usually an accumulation or addition of points “done” PBIs in one Sprint.
Scrum.org - Improving the Profession of Software Development
28. Release Planning Rule of Thumb
1. An accurate Release Plan requires an ordered an estimated Product Backlog
2. An accurate Release Plan requires a known Velocity
Scrum.org - Improving the Profession of Software Development
29. From here we can be confident to tell the
customer when a project will be finished and go
for a fix bid project
Scrum.org - Improving the Profession of Software Development
30. Thank You
감사합니다
@jpartogi
Scrum.org - Improving the Profession of Software Development
31. Learn more about Scrum at
Professional Scrum Master Training
Visit http://scrumway.asia
Scrum.org - Improving the Profession of Software Development