Presentation at Scan-Agile 2011 and Agile Riga Day 2011 about how to recognize what type of project you are in, and how to improve it towards a more agile, responsive, higher quality project
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
This document discusses how to address scaling agile needs on JIRA using SAFe (Scaled Agile Framework). It introduces cPrime as a SAFe and Agile training partner. It provides an overview of SAFe concepts like portfolio, program and team levels. It describes how business and architectural epics flow through the system from identification to implementation. It shows how epics can be allocated to Agile release trains and decomposed into features. Finally, it discusses investment themes and some JIRA addons for supporting SAFe.
Be ready with your questions and Join our next webinar to know:
- Where software testing began
- Early software testing methodology
- The rise of agile testing
- Recent testing trends
- The future of testing and Testers
============== Follow us ==============
Website: http://xpdays.org
Linked In: https://www.linkedin.com/company/xpdays
Facebook: https://www.facebook.com/xpdaysorg
Twitter: https://twitter.com/xpdaysorg
Presentazione al Meetup Appsterdam del 16 gennaio 2014.
La creazione di App si sposa molto bene con i valori e i principi di Agile. Nella puntata di The Big Bang Theory - The Bus Pants Utilization | L'utilizzo dei pantaloni da autobus vede Sheldon che cerca di dirigere il team imponendo ruoli ed attivita' e questo non funziona. Alla fine viene sbattuto fuori di casa.
In Agile il team si auto-organizza, condividendo le scelte e lavorando insieme per un obiettivo condiviso. Sviluppatori, grafici, esperti dei contenuti, illustratori e altre figure lavorano all'unisono in modo sereno e sostenibile.
This webinar discussed how a company called AcademicText.com transitioned from early Scrum adoption at the team level to implementing the Scaled Agile Framework (SAFe) across multiple teams. It began with Scrum training and using Jira for individual teams. Issues with coordination and dependencies between teams led to adopting SAFe. Key aspects discussed included:
- Aligning teams into Agile Release Trains (ARTs) organized by value streams
- Planning at the program level using a portfolio backlog, epics, and features
- Conducting SAFe release planning meetings over two days to develop the program increment plan
- Tracking progress through metrics like feature completeness and release burndowns
- Managing the
Fiverr - delivering fast w/ no QA - Agile Israel 2016 Gil WassermanAgileSparks
This document discusses Fiverr's approach to quality assurance called "NoQA" where QA is removed from the critical path of software development in order to allow for faster delivery of features. Some key aspects of Fiverr's NoQA approach include:
- Removing QA from being a gatekeeper and instead integrating QA as part of the development team
- Relying on developers to test their own code through techniques like unit testing and deployment to staging environments
- Focusing on continuous monitoring of production systems to identify issues once features are live
- Guiding principles of trust, autonomy, ownership and accountability to replace formal QA processes
- Embracing uncertainty and continuous learning as software development is viewed as an ongoing knowledge game
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
This document discusses how to address scaling agile needs on JIRA using SAFe (Scaled Agile Framework). It introduces cPrime as a SAFe and Agile training partner. It provides an overview of SAFe concepts like portfolio, program and team levels. It describes how business and architectural epics flow through the system from identification to implementation. It shows how epics can be allocated to Agile release trains and decomposed into features. Finally, it discusses investment themes and some JIRA addons for supporting SAFe.
Be ready with your questions and Join our next webinar to know:
- Where software testing began
- Early software testing methodology
- The rise of agile testing
- Recent testing trends
- The future of testing and Testers
============== Follow us ==============
Website: http://xpdays.org
Linked In: https://www.linkedin.com/company/xpdays
Facebook: https://www.facebook.com/xpdaysorg
Twitter: https://twitter.com/xpdaysorg
Presentazione al Meetup Appsterdam del 16 gennaio 2014.
La creazione di App si sposa molto bene con i valori e i principi di Agile. Nella puntata di The Big Bang Theory - The Bus Pants Utilization | L'utilizzo dei pantaloni da autobus vede Sheldon che cerca di dirigere il team imponendo ruoli ed attivita' e questo non funziona. Alla fine viene sbattuto fuori di casa.
In Agile il team si auto-organizza, condividendo le scelte e lavorando insieme per un obiettivo condiviso. Sviluppatori, grafici, esperti dei contenuti, illustratori e altre figure lavorano all'unisono in modo sereno e sostenibile.
This webinar discussed how a company called AcademicText.com transitioned from early Scrum adoption at the team level to implementing the Scaled Agile Framework (SAFe) across multiple teams. It began with Scrum training and using Jira for individual teams. Issues with coordination and dependencies between teams led to adopting SAFe. Key aspects discussed included:
- Aligning teams into Agile Release Trains (ARTs) organized by value streams
- Planning at the program level using a portfolio backlog, epics, and features
- Conducting SAFe release planning meetings over two days to develop the program increment plan
- Tracking progress through metrics like feature completeness and release burndowns
- Managing the
Fiverr - delivering fast w/ no QA - Agile Israel 2016 Gil WassermanAgileSparks
This document discusses Fiverr's approach to quality assurance called "NoQA" where QA is removed from the critical path of software development in order to allow for faster delivery of features. Some key aspects of Fiverr's NoQA approach include:
- Removing QA from being a gatekeeper and instead integrating QA as part of the development team
- Relying on developers to test their own code through techniques like unit testing and deployment to staging environments
- Focusing on continuous monitoring of production systems to identify issues once features are live
- Guiding principles of trust, autonomy, ownership and accountability to replace formal QA processes
- Embracing uncertainty and continuous learning as software development is viewed as an ongoing knowledge game
The document discusses the Kanban methodology for managing software development projects. It begins by explaining what Kanban is and its origins. It then outlines the key Kanban principles of visualizing workflow, limiting work-in-progress, managing flow, making policies explicit, using feedback loops, and continuously improving. Examples are provided of how to implement these principles using a Kanban board. Advanced techniques like epic clustering and swim lanes are also covered. Tips are given on getting started with Kanban and allowing it to evolve over time.
XP teams take every iteration commitment seriously by delivering working software. Continuous Delivery of working product increments and early releasing gives concrete feedback about the state of the system at any time and also increases customer satisfaction.
Gear up for Continuous Integration with Salesforce DX, Circle CI and ClaytonDaniel Stange
Everyone in the Salesforce ecosystem knows how painful the rollout of changes with Changeset can be, and how tedious the setup for Ant build jobs is. Luckily, Salesforce DX is a huge leap forward in terms of modern enterprise software lifecycle management. I am going to present how my development toolchain links DX, Clayton and Circle CI, and we are going to build a Circle configuration together to help you getting rid of change sets forever.
Scrum, Kanban, and DevOps Sitting in a Tree… - Big Apple Scrum Day 2018Yuval Yeret
Scrum, Kanban, and DevOps Sitting on a Tree... (Learn how to leverage Kanban & Scrum together and how to fit DevOps into the picture)Should we use Scrum? Should we use Kanban? Where does DevOps fit into the picture? The best agile teams already know they don’t need to choose. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership. DevOps really is mainly about doing Agile the right way. In this session, we will look at a core definition of Scrum, Kanban & DevOps, do some myth-busting as well as identify the quite significant common ground between Scrum, Kanban and DevOps. We will then look at practical ways like the Kanban-based Sprint Backlog, Flow-based Daily Scrum, Visualizing aging work, Flow-based Sprint Planning - which bring some Kanban flow into your Scrum. We will look at how to bring Scrum roles/events/artifacts into your Kanban. We will look at ways to wrap Scrum with a Kanban Flow system that looks upstream/downstream and at the higher level picture of a DevOps Culture/Process. You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with some ideas for experiments to try when back at work.
The document discusses the benefits of using Rally, an agile test management tool, in software development and testing projects. It notes that agile development is becoming the norm. Rally helps manage requirements, estimation, test case creation, execution, defect tracking, and reporting throughout the agile project lifecycle. It integrates with other tools and provides benefits like real-time status, coordination across teams, and analytics. An example case study describes how Rally was used effectively over multiple sprints in one of Marlabs' client projects to plan, track progress, link defects to user stories, and generate reports.
There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster.
Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.
Sam McAfee talks about how they have applied Kanban and lean methodologies at RadicalFusion during the San Francisco Agile User Group meeting at Atlassian.
http://youtu.be/RkV1WgeQX8A
This document discusses blending SCRUM and Kanban approaches. It describes using Kanban at different levels of an organization, including at the portfolio, program, and team levels. Kanban focuses on limiting work in progress to improve flow and make bottlenecks visible. The document compares SCRUM and Kanban methods and suggests using a combination of the two by overlaying Kanban's work in progress limits on top of a SCRUM board at the team level. This allows restricting work in each column to optimal levels to increase throughput and productivity across the entire enterprise.
This document introduces Agile project management. It outlines the key principles of the Agile manifesto which focus on individuals, working software, customer collaboration, and responding to change over rigid plans. The document compares the traditional Waterfall process to the iterative Agile process. In Agile, requirements are captured in a product backlog and prioritized in sprints. Teams work in short sprints to deliver working software and get feedback through reviews and retrospectives to continuously improve.
Traditional testing approaches involve post-development testing phases where quality is expected to be boosted after code is complete, but this illusion of control can lead to delays if requirements are not fully delivered. Agile testing is iterative and incremental, with testers testing each coding increment as soon as it is finished so that programmers never get ahead of testers and a story is not done until tested. True agile teams focus on repeatable quality and efficiency rather than just delivering specified requirements by a release date.
The document discusses revisiting Extreme Programming (XP) as an agile methodology that focuses on technical practices. It notes that while Scrum provides a project management framework, it lacks engineering practices like continuous integration, test-driven development, refactoring, and pair programming that are part of XP. Adopting these XP practices can help teams build quality into software development and enhance their agility. However, these technical practices are often not used, leaving people disengaged from the agile process. The document argues that revisiting XP as an independent methodology that incorporates engineering practices could help teams develop software better, faster, and with happier engineers through continuous learning.
Kanban is a software development technique based on lean manufacturing principles from Toyota. It visualizes workflows on a kanban board to limit work in progress, identify bottlenecks, and continuously improve the process. The document recommends mapping your value stream, determining velocity, using a pull system, and expediting bottlenecks to adopt Kanban successfully like at PHPFactory.
Technique To Prioritize Key Tasks In Agile Process PowerPoint Presentation Sl...SlideTeam
A technique that helps the organization to prioritize various activities in their software development project is known as prioritization technique in agile. The following presentation provides an overview of the project and implements agile methodology in the same, once agile methodology is implemented a list of priority task is identified with the help of multiple techniques such as MoSCoW, Kano Model and relative average method. This presentation is helpful for IT organizations and IT managers with an objective to optimize their software development process by identifying tasks that are to be given utmost priority with the help of different types of prioritization techniques. Initially this presentation provides an overview of the project as it displays the project details and the structure of the project team which has scrum master, developers and operational team. Once the project overview is taken the approach for software development is decided. Once the workings and operations of the project are decided, various prioritization techniques are utilized in order to identify key priority tasks. These techniques can be MoSCoW or Must have, should have, could have and would have or Kano model or weighted average method. After utilizing these techniques multiple key priority tasks are identified. After carefully understanding the priority tasks the cost of the entire project is highlighted and the performance of the project is tracked with the help of various KPIs or key performance indicators. https://bit.ly/3ilCrPq
Creation and refinement of the product backlog can be achived in different ways.
Roman Pichler, in is post originally written in Jul, 16 2012 - http://www.romanpichler.com/blog/agile-product-innovation/the-product-canvas , has proposed a really interesting approach: use canvas to create and share product vision and product backlog creation and refinement.
I used this approach for a while with cool results.
These slides are a step-by-step introduction of the tool.
Please send me feedbacks to correct and improve it!
You can use these slides under Creative Commons Attribution-ShareAlike 3.0 Unported License.
A Brave Journey in Merge Waters: How Paysafe Consolidated Their Atlassian ToolsAtlassian
After a large merger in mid-2015, Paysafe, a fintech company providing payment solutions worldwide, had several instances of Atlassian products spread across the globe. With 4 JIRA Software, 3 Confluence, 2 Bitbucket, 2 Bamboo and 2 HipChat server instances, our team made the bold decision to unify them into a single instance for each product. Further complicating the already daunting task were 6 active directories of users, a diverse set of admins, and different levels of organizational maturity across our development, product, and business teams. A year after we set sail, Paysafe now has a single production instance of the majority of these products, with little impact to users, no data loss, and improved performance. In this session, we will outline our journey into the uncharted waters of consolidation focusing on our 4 JIRA instances, as this was the most critical and challenging mission in our quest. Together with our Atlassian Solution Partner, Nemetschek Bulgaria, we will share tips and best practices on limiting downtime, eliminating the risk for loss of vital data, and the unification of user management.
Radostina Kavrakova, IT Product Support Manager, Paysafe Group plc
George Stoyanov, Senior Software Engineer & Project Leader, Nemetschek Bulgaria
Whether your business is a small, fast-growing agile shop, or a larger company that is trying to adopt agile methodologies, success hinges on a proper foundation of roles, responsibilities, and processes. In this talk, we’ll cover how Trulia tackles these areas, and discuss how JIRA Agile helped us expand our agile cycles.
Agile Testing FAQs and Mythbuster - Software Testing Atlanta Conference 2015Yuval Yeret
- The document discusses agile testing practices and strategies. It addresses myths around testing roles and responsibilities in agile teams.
- A key point is that testing should shift left towards more continuous quality, adding feature-level testing earlier in sprints. Automation is important but not the main role of testers.
- Testers play an important role in backlog grooming and specifying acceptance tests to guide development work. Continuous quality is a journey that provides value at each step.
LCNUG 2015 - what's new for agile teams in TFS 2015Angela Dugan
With the upcoming launch of TFS 2015, it's hard to keep track of all of the new features. This presentation is a quick synopsis of what has been added in the agile planning and testing space with the latest releases to TFS 2105 and VSO.
Are you thinking to involve QA and test in Unit Testing but are unsure how?
Or are you looking to improve you existing unit testing set up?
In this webinar we discussed: QA's role in Unit Testing
Topics Covered:
- Agile Testing
- Agile QA Team Dynamics
- Types of Testing
- Collaborative Unit Testing
- Unit Testing with distributed teams
DevOps - Agile on Steroids by Tom Clement Oketch and Augustine KisituThoughtworks
This document discusses challenges with traditional Agile approaches and how DevOps aims to address them. It notes that while organizations may think they are Agile, problems still arise around deployment pain points, inability to adapt to change, and dissatisfied clients. DevOps focuses on automating processes, breaking down silos between teams, and continuous delivery through culture change, infrastructure automation, measurement, and information sharing. The presentation emphasizes that DevOps is not a role or certification but a relationship and approach centered on collaboration and automation.
A szokás hatalma és a választás paradoxona - Kolozsi István, kolboidIstván Kolozsi
A 2013. október 16-án tartott előadás az Internet Hungary-n hangzott el. http://www.internethungary.com/
A prezentációhoz tartozó blog poszt:
https://blog.kolboid.eu/a-szokas-hatalma-es-a-valasztas-paradoxona/
The document discusses the Kanban methodology for managing software development projects. It begins by explaining what Kanban is and its origins. It then outlines the key Kanban principles of visualizing workflow, limiting work-in-progress, managing flow, making policies explicit, using feedback loops, and continuously improving. Examples are provided of how to implement these principles using a Kanban board. Advanced techniques like epic clustering and swim lanes are also covered. Tips are given on getting started with Kanban and allowing it to evolve over time.
XP teams take every iteration commitment seriously by delivering working software. Continuous Delivery of working product increments and early releasing gives concrete feedback about the state of the system at any time and also increases customer satisfaction.
Gear up for Continuous Integration with Salesforce DX, Circle CI and ClaytonDaniel Stange
Everyone in the Salesforce ecosystem knows how painful the rollout of changes with Changeset can be, and how tedious the setup for Ant build jobs is. Luckily, Salesforce DX is a huge leap forward in terms of modern enterprise software lifecycle management. I am going to present how my development toolchain links DX, Clayton and Circle CI, and we are going to build a Circle configuration together to help you getting rid of change sets forever.
Scrum, Kanban, and DevOps Sitting in a Tree… - Big Apple Scrum Day 2018Yuval Yeret
Scrum, Kanban, and DevOps Sitting on a Tree... (Learn how to leverage Kanban & Scrum together and how to fit DevOps into the picture)Should we use Scrum? Should we use Kanban? Where does DevOps fit into the picture? The best agile teams already know they don’t need to choose. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership. DevOps really is mainly about doing Agile the right way. In this session, we will look at a core definition of Scrum, Kanban & DevOps, do some myth-busting as well as identify the quite significant common ground between Scrum, Kanban and DevOps. We will then look at practical ways like the Kanban-based Sprint Backlog, Flow-based Daily Scrum, Visualizing aging work, Flow-based Sprint Planning - which bring some Kanban flow into your Scrum. We will look at how to bring Scrum roles/events/artifacts into your Kanban. We will look at ways to wrap Scrum with a Kanban Flow system that looks upstream/downstream and at the higher level picture of a DevOps Culture/Process. You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with some ideas for experiments to try when back at work.
The document discusses the benefits of using Rally, an agile test management tool, in software development and testing projects. It notes that agile development is becoming the norm. Rally helps manage requirements, estimation, test case creation, execution, defect tracking, and reporting throughout the agile project lifecycle. It integrates with other tools and provides benefits like real-time status, coordination across teams, and analytics. An example case study describes how Rally was used effectively over multiple sprints in one of Marlabs' client projects to plan, track progress, link defects to user stories, and generate reports.
There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster.
Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.
Sam McAfee talks about how they have applied Kanban and lean methodologies at RadicalFusion during the San Francisco Agile User Group meeting at Atlassian.
http://youtu.be/RkV1WgeQX8A
This document discusses blending SCRUM and Kanban approaches. It describes using Kanban at different levels of an organization, including at the portfolio, program, and team levels. Kanban focuses on limiting work in progress to improve flow and make bottlenecks visible. The document compares SCRUM and Kanban methods and suggests using a combination of the two by overlaying Kanban's work in progress limits on top of a SCRUM board at the team level. This allows restricting work in each column to optimal levels to increase throughput and productivity across the entire enterprise.
This document introduces Agile project management. It outlines the key principles of the Agile manifesto which focus on individuals, working software, customer collaboration, and responding to change over rigid plans. The document compares the traditional Waterfall process to the iterative Agile process. In Agile, requirements are captured in a product backlog and prioritized in sprints. Teams work in short sprints to deliver working software and get feedback through reviews and retrospectives to continuously improve.
Traditional testing approaches involve post-development testing phases where quality is expected to be boosted after code is complete, but this illusion of control can lead to delays if requirements are not fully delivered. Agile testing is iterative and incremental, with testers testing each coding increment as soon as it is finished so that programmers never get ahead of testers and a story is not done until tested. True agile teams focus on repeatable quality and efficiency rather than just delivering specified requirements by a release date.
The document discusses revisiting Extreme Programming (XP) as an agile methodology that focuses on technical practices. It notes that while Scrum provides a project management framework, it lacks engineering practices like continuous integration, test-driven development, refactoring, and pair programming that are part of XP. Adopting these XP practices can help teams build quality into software development and enhance their agility. However, these technical practices are often not used, leaving people disengaged from the agile process. The document argues that revisiting XP as an independent methodology that incorporates engineering practices could help teams develop software better, faster, and with happier engineers through continuous learning.
Kanban is a software development technique based on lean manufacturing principles from Toyota. It visualizes workflows on a kanban board to limit work in progress, identify bottlenecks, and continuously improve the process. The document recommends mapping your value stream, determining velocity, using a pull system, and expediting bottlenecks to adopt Kanban successfully like at PHPFactory.
Technique To Prioritize Key Tasks In Agile Process PowerPoint Presentation Sl...SlideTeam
A technique that helps the organization to prioritize various activities in their software development project is known as prioritization technique in agile. The following presentation provides an overview of the project and implements agile methodology in the same, once agile methodology is implemented a list of priority task is identified with the help of multiple techniques such as MoSCoW, Kano Model and relative average method. This presentation is helpful for IT organizations and IT managers with an objective to optimize their software development process by identifying tasks that are to be given utmost priority with the help of different types of prioritization techniques. Initially this presentation provides an overview of the project as it displays the project details and the structure of the project team which has scrum master, developers and operational team. Once the project overview is taken the approach for software development is decided. Once the workings and operations of the project are decided, various prioritization techniques are utilized in order to identify key priority tasks. These techniques can be MoSCoW or Must have, should have, could have and would have or Kano model or weighted average method. After utilizing these techniques multiple key priority tasks are identified. After carefully understanding the priority tasks the cost of the entire project is highlighted and the performance of the project is tracked with the help of various KPIs or key performance indicators. https://bit.ly/3ilCrPq
Creation and refinement of the product backlog can be achived in different ways.
Roman Pichler, in is post originally written in Jul, 16 2012 - http://www.romanpichler.com/blog/agile-product-innovation/the-product-canvas , has proposed a really interesting approach: use canvas to create and share product vision and product backlog creation and refinement.
I used this approach for a while with cool results.
These slides are a step-by-step introduction of the tool.
Please send me feedbacks to correct and improve it!
You can use these slides under Creative Commons Attribution-ShareAlike 3.0 Unported License.
A Brave Journey in Merge Waters: How Paysafe Consolidated Their Atlassian ToolsAtlassian
After a large merger in mid-2015, Paysafe, a fintech company providing payment solutions worldwide, had several instances of Atlassian products spread across the globe. With 4 JIRA Software, 3 Confluence, 2 Bitbucket, 2 Bamboo and 2 HipChat server instances, our team made the bold decision to unify them into a single instance for each product. Further complicating the already daunting task were 6 active directories of users, a diverse set of admins, and different levels of organizational maturity across our development, product, and business teams. A year after we set sail, Paysafe now has a single production instance of the majority of these products, with little impact to users, no data loss, and improved performance. In this session, we will outline our journey into the uncharted waters of consolidation focusing on our 4 JIRA instances, as this was the most critical and challenging mission in our quest. Together with our Atlassian Solution Partner, Nemetschek Bulgaria, we will share tips and best practices on limiting downtime, eliminating the risk for loss of vital data, and the unification of user management.
Radostina Kavrakova, IT Product Support Manager, Paysafe Group plc
George Stoyanov, Senior Software Engineer & Project Leader, Nemetschek Bulgaria
Whether your business is a small, fast-growing agile shop, or a larger company that is trying to adopt agile methodologies, success hinges on a proper foundation of roles, responsibilities, and processes. In this talk, we’ll cover how Trulia tackles these areas, and discuss how JIRA Agile helped us expand our agile cycles.
Agile Testing FAQs and Mythbuster - Software Testing Atlanta Conference 2015Yuval Yeret
- The document discusses agile testing practices and strategies. It addresses myths around testing roles and responsibilities in agile teams.
- A key point is that testing should shift left towards more continuous quality, adding feature-level testing earlier in sprints. Automation is important but not the main role of testers.
- Testers play an important role in backlog grooming and specifying acceptance tests to guide development work. Continuous quality is a journey that provides value at each step.
LCNUG 2015 - what's new for agile teams in TFS 2015Angela Dugan
With the upcoming launch of TFS 2015, it's hard to keep track of all of the new features. This presentation is a quick synopsis of what has been added in the agile planning and testing space with the latest releases to TFS 2105 and VSO.
Are you thinking to involve QA and test in Unit Testing but are unsure how?
Or are you looking to improve you existing unit testing set up?
In this webinar we discussed: QA's role in Unit Testing
Topics Covered:
- Agile Testing
- Agile QA Team Dynamics
- Types of Testing
- Collaborative Unit Testing
- Unit Testing with distributed teams
DevOps - Agile on Steroids by Tom Clement Oketch and Augustine KisituThoughtworks
This document discusses challenges with traditional Agile approaches and how DevOps aims to address them. It notes that while organizations may think they are Agile, problems still arise around deployment pain points, inability to adapt to change, and dissatisfied clients. DevOps focuses on automating processes, breaking down silos between teams, and continuous delivery through culture change, infrastructure automation, measurement, and information sharing. The presentation emphasizes that DevOps is not a role or certification but a relationship and approach centered on collaboration and automation.
A szokás hatalma és a választás paradoxona - Kolozsi István, kolboidIstván Kolozsi
A 2013. október 16-án tartott előadás az Internet Hungary-n hangzott el. http://www.internethungary.com/
A prezentációhoz tartozó blog poszt:
https://blog.kolboid.eu/a-szokas-hatalma-es-a-valasztas-paradoxona/
Este documento define los metales como cuerpos sólidos y buenos conductores del calor y la electricidad que se usan para fabricar numerosos objetos. Explica que los metales son maleables, dúctiles, tenaces y resistentes mecánicamente. Se obtienen de elementos nativos, óxidos, cloruros, carbonatos y fosfatos. Se clasifican y aplican en construcción, maquinaria, cañerías, chapas y más. Su obtención y fabricación puede impactar el medio ambiente, pero existen tecnologías para reducir
Putting Service back into Public Service / Service Experience Camp 2014Service Experience Camp
It makes perfect sense to assume that public services are citizen-centric because they are essentially created for citizens. But what does it really mean to design citizen-centric services? What are the ah-ha! moments, and what are the challenges?
Tong Teck Lim, & Joycelyn Chua from the Ministry of Manpower, Singapore spoke about ‘Putting Service back into Public Service’ during Service Experience Camp 2014 in Berlin.
Dokumen tersebut membahas tentang kontrak bisnis, termasuk pengertian kontrak bisnis, asas dan syarat sah kontrak, prestasi dan wanprestasi, penyelesaian sengketa kontrak, jenis-jenis kontrak bisnis, dan sebab-sebab berakhirnya suatu perjanjian.
The document discusses traffic and usage statistics for the new GRSS website since its launch in January 2010. It provides details on the top visited pages and referrers. It also summarizes growth in social media members on Facebook and LinkedIn. The document outlines pilots for live speaker streaming, a mobile site, and search engine optimization efforts to increase visibility of the GRSS website.
אנחנו חיים בעולם מרובה ערוצים, מרובה מסכים, מרובה רשתות... המון קורה ובקצב מהיר. כולנו רוצים להיות מעודכנים בהכל עכשיו ומיד אבל בפועל אין לנו זמן... מקסימום יכולים לתפוס את ה"צינור".
בדיוק לשם כך, מחלקת מחקר אסטרטגי יצרה עבורכם את Spot‘it- סקירה שבועית שתאפשר לכם בצורה הפשוטה והקלה ביותר להתעדכן תוך מספר דקות בכל מה שחם ומעורר השראה בתרבות האינטרנט העכשווית.
ה-כול החל מסרטוני הרשת הוויראליים ביותר, פרסומות ומהלכים שיווקיים מעוררי השראה, הקליפים הנצפים ביותר, תכניות הטלוויזיה הכי מדוברות, הסרטים הכי חדשים ועוד, ועוד, ועוד...
This document discusses popular online platforms and recommends using them to learn. It lists YouTube and Wikipedia as good free resources for gaining knowledge on various topics from anywhere at any time through online videos and articles. The document encourages taking advantage of these platforms with a smiley face at the end.
Zingly is a multi-banking app for European banking - think of it as a Venmo for the Europe. An easy to use mobile app makes payments simpler than ever before, regardless of a bank you have.
Zingly uses a super secure open-source PowerAuth 2.0 protocol for authentication and transaction signing, so that user money is extra safe.
کارت امتیازی متوازن ابزاری است برای چاری سازی کنترل و پایش استراتژیها و شاخض های عملکردی شرکت ها
در مرکز تحقیق و توسعه خشکبار ایران این تکنیک برای دستیابی به توسعه پایدار و ایجاد نگاه استراتژیک تدریس می گردد
Instead of fighting about “who’s agile” or “who’s more agile than whom”, it would be useful to create a set of patterns, that once recognized would help us define if we are or have been able to successfully implement an Agile life-cycle for our project and portfolio.
In this session we will explore how it “feels” to work in an Agile project. It is not enough to do Scrum or Kanban, you need to know if you are doing it right.
This document discusses how Kanban and DevOps are related. It describes how Kanban practices like visualizing workflow, limiting work-in-progress, and creating feedback loops can help optimize flow and continuous improvement in DevOps. The document provides examples of applying Kanban techniques to problems in areas like flow, feedback, and risk management. It argues that Kanban is a natural fit for facilitating incremental changes in DevOps initiatives over time.
This is a demo presentation prepared for the recruitment of Lecturer in CSE at Green University. In this presentation, an introduction to Software Development Life Cycle is demonstrated in an intuitive way.
The document discusses how PayPal transitioned to a "lean engineering" model between 2011-2014 to better support rapid experimentation and continuous learning. It outlines four key principles of lean engineering: 1) Enable continuous learning through frequent delivery and prototyping. 2) Design for experimentation and frequent changes. 3) Democratize innovation by keeping teams small and using open source tools. 4) Use lean UX processes to give structure and feedback to agile development, treating users as the "brain" of engineering efforts. The document provides examples of how PayPal implemented these principles through techniques like continuous delivery, same-stack prototyping, open source development, and integrating lean UX processes with agile.
(Minimum) Enterprise Viable Product - a relookSriram Sabesan
Building a case and defining the characteristic of an Enterprise Viable Product. There is no minimum threshold - but a different value measure. It is not count of feature-set, but robustness and scale
Lean Engineering: How to make Engineering a full Lean UX partnerBill Scott
In 1999, PayPal's name was synonymous with innovation. In fact, the so called PayPal Mafia (original founders) went on to establish Tesla, SpaceX, YouTube, Skype and other startups. They also provided the early investments of many of the most innovative companies on the internet today. But over time that innovation slowed to a crawl.
In 2011 a number of things begin to come together for PayPal that started its journey back to innovation. This is the story of that reboot and how engineering has played a key role in partnering directly with product and design to move from a culture of products having a long shelf life, to one of rapid experimentation.
In this talk, Bill will outline the principles of Lean Engineering; principles for engineering that enable learning. Drawing from his experience leading User Interface Engineering at both Netflix & PayPal, Bill will walk you through the key principles your engineering team will need to adopt to be that enabler for product and design in your organization. This talk will not just inspire you, but it will also give you some hard earned advice on making this a reality in your organization.
Given at Agile Camp 2013, San Jose, CA. Sept. 21
How do you take a gigantic organization like PayPal that was entrenched in a culture of a “”long shelf life”” and transform it to a culture of rapid experimentation? Bill will give 3 principles applied to PayPal engineering to make it a full partner with Lean UX. This will be illustrated by showing how they re-factored the tech stack and changed the way engineers work in Lean streams with design & product partners and how it plays with agile.
As a backdrop Bill will discuss several historical factors in the field of software engineering that are antithetical to the Lean Startup mindset but still find their way into most large enterprises. By understanding this historical context and applying lean principles he will demonstrate how a lean transformation can take place in any enterprise.
Scala Days Chicago 2017: Building a Company on ScalaNatalie Vegel
Tapad co-founder and CTO, Dag Liodden, shares best practices on how companies can embrace Scala to spur growth and use the language to help deliver high quality code at high velocity.
In the rapidly changing world we live in now, Agile is the mantra to live by! We all need to be agile, nimble, adaptive and respond to the changes rapidly.
Texavi’s Tech Bootcamp is a series of free online courses on agile and digital transformation.Texavi's Tech Bootcamp will equip you to be job-ready with practical and real-time insights, as well as offering access to our treasure of insightful, high-quality resources and materials.
The part 1 of this series will be touching upon the overview and setting the context with introducing the agile mindset. This is very important in order to start the agile journey. We will tread through the foundation of agile, how its different from the mainstream waterfall model, and look at the evolution of the agile development methodologies over the decades.
We will then have a look at the various popular agile methodologies such as Kanban, Scrum, DSDM, SAFe, Lean etc.
The document discusses the System Development Life Cycle (SDLC), which is a standard model used worldwide to develop software. It describes the main stages of the SDLC as analysis, planning, implementation, and testing. Analysis is the first and most important phase where requirements are determined and the problem is broken down. Planning involves assigning tasks to team members. Implementation is the longest and most expensive phase. Testing is an ongoing phase where thorough testing takes place. The document also discusses various SDLC models including waterfall, iterative enhancement, prototyping, spiral, build and fix, and rapid application development models.
Lean Engineering: Engineering for Learning & Experimentation in the Enterpris...Rosenfeld Media
Bill Scott: "Lean Engineering: Engineering for Learning & Experimentation in the Enterprise"
Enterprise UX 2015 • May 13, 2015 • San Antonio, TX, USA
http://enterpriseux.net
Presentation (animated) on Agilve vs Iterative vs Waterfall models in SDLC.
Detailed comparison across Process, Planning, Execution and Completion.
#Cricket Analogy#
Waterfall (Test Match) vs Iterative (ODI) Format vs Agile (T20)
#Waterfall: Test Match Format - Strategic-Phase by Phase like Innings by Innings.
Game for Specialists, Slow and Steady.
#One Day (ODI) Format : Strategic approach – First10/Middle/Slog overs.
Mix of Specialists and
All-Rounders, Result oriented.
#T20 Format: Lively,Dynamic, Full of Action. Game for All-Rounders. Changes with every over.
Highly Result oriented
Short Introduction of software engineering for bioinformatics 丈 宮本
This document provides an overview of different software engineering approaches for bioinformatics projects, including Waterfall, Agile, DevOps, eXtreme Programming, and tools like Git, GitHub, Jenkins, Docker, and Fabric. Waterfall is not well-suited for bioinformatics due to lack of flexibility, while Agile and DevOps methodologies allow for iterative development and integration of code changes. eXtreme Programming focuses on code maintainability through practices like test-driven development and continuous integration. Version control with Git/GitHub and configuration tools like Docker and Fabric can help manage reproducibility and infrastructure as code.
The document discusses software development life cycles (SDLC) and software testing. It describes several SDLC models - waterfall, spiral, V, and agile methodology. The waterfall model involves sequential phases from requirements to maintenance. Agile methodology values individuals, working software, customer collaboration, and responding to change. The document also outlines the roles, principles, and process flow of agile development including user stories, iterations, daily stand-ups, and continuous integration.
Using flow approaches to effectively manage agile testing at the enterprise l...Yuval Yeret
Slides from my upcoming LSSC11 talk:
More and more organizations want to become more agile these days. When the theory hits the shores of reality, few organizations can get to an idealistic agile feature team that does all testing within sprints, has no need for release-level processes, and where everything is fully automated continuous deployment style. Usually the testing organization is in the eye of the storm when talking about Big Batches, Wastes, ineffective handoffs and mountains of rework, as well as high transaction costs. I’ve recently been using Lean/Kanban flow based approaches to provide a way to evolve testing organizations to a more effective way of working, so that they can better support earlier feedback and higher flexibility. I will present this work as well as case studies from enterprise-level product development companies that are starting to use these approaches.
We will deal with the following challenges:
* Complex environments when it is not realistic to finish all required work within a sprint
* How to visualize and reduce testing batch sizes within sprints/releases using CFD
* How to deal with the testing bottleneck so common in product development organizations – practical suggestions and how to deal with the mindset issues
* How to run stabilization/hardening periods using Flow-based thinking
http://lssc11.crowdvine.com/talks/18074
Practical DevOps & Continuous Delivery – A Webinar to learn in depth on DevO...Hugo Messer
After the grant success of the C-level event "I/O: Intelligent Outsourcing", Bridge Global is conducting a free webinar under BEAM (Bridge Events And Meets) on September 6th, 2017.
We designed this webinar as a must-attend event for those who are looking for a kick-start moment to lead their organization into the DevOps environment. It attracted several attendees from all parts of the world. They all sat back and learned valuable insights on DevOps culture and practices.
People are tired of hearing the countless amount of suggestions and opinions while contemplating to start their DevOps journey. This webinar helped its attendees in getting rid of all kinds of apprehensions related to the topic.
Topics Covered
DevOps vs. Traditional Approach.
Addressing the Delivery Challenges.
Why Continuous Integration and Continuous Delivery is so relevant?
DevOps vs Release Management.
Best Practices.
Recently I was asked to explain what dev-ops is at a large enterprise software vendor undergoing transformation.
In these slides, I present the concepts, tools and mindset that drive DevOPS.
6 Principles for Enabling Build/Measure/Learn: Lean Engineering in ActionBill Scott
Presented at Lean Day West - Portland, OR. Sept. 17, 2013
How do you take a gigantic organization like PayPal and begin to transform the experiences? Engineering is often the key blocker in being able to achieve a high rate of innovation. In this talk, Bill Scott will give specific examples on implemented Lean UX in a 13,000 person company, re-factored the technology stack and changed the way engineers work with design & product partners. In addition, Bill will provide additional examples that go back to his early days writing one of the first Macintosh games to his more recent work at Netflix and the power of treating the user interface layer as the experimentation layer.
The document discusses various software development life cycle models. It describes the iterative and incremental model in detail, noting that it involves developing the software in increments with each increment applying the classical waterfall phases of requirements, analysis, design, implementation and testing on a portion of the software. Each iteration can be viewed as a small waterfall model. The model allows for risks to be addressed early and working versions to be delivered frequently for feedback. Other models discussed include waterfall, rapid prototyping, agile processes, synchronize-and-stabilize and spiral. The document concludes no single model is best and a hybrid approach may be most effective.
Similar to Patterns of agility, how to recognize and agile project when you see one (20)
Cobis and Oikosofy 5 Innovation shots for the banking industryVasco Duarte
Banking is here to stay, but Banks may not. The incoming wave of technology companies dedicated to banking requires banks to consider what innovation strategy, and execution framework they will implement in the coming 5 years. SAFe - an Agile framework for the Enterprise - provides a proven approach to align teams, management, deploy strategy quickly and help teams and organizations focus on the high impact opportunities. This one-hour workshop will introduce the SAFe framework and explain how it can be used as a blueprint for building a culture of innovation that provides a proven method to implement strategies in an agile manner, and develop competitive businesses. From strategy definition to day-to-day execution.
What am I going to get from this course?
• What does a “Culture of Innovation” mean?
The Basics of what it is & how it works
• What are the Key Ingredients for building a culture of innovation?
Building teams, and teams of teams to scale adaptability and agility
Structured and proven approach, based on learnings in the banking industry all over the world
Understanding your customers wants, needs and aspirations
Measuring success and learning quickly with the right framework to speed up learning
• Creating an Innovation Strategy
From an idea to a real-life product in mere weeks. With a method that helps execute, and adapt
Innovation accounting, a radical approach to testing new products, services in a cost-effective and high impact mannero
Motivating innovation contributions at all levels of the organization with a method that empowers all employees to make a difference
Fast time-to-market with the framework to help measure the results and adapt based on near real-time market feedback
No estimates - 10 new principles for testingVasco Duarte
This document outlines 10 principles for software development without estimates. It begins by discussing trusting or changing your process (Principle 1) and shortening feedback cycles (Principle 2). Data is presented showing estimates are often inaccurate, with 80% of projects being late or over budget. Principle 3 states to believe data over estimates. Alternatives to estimate-driven decision making are suggested in Principle 4. Principles 5-8 discuss testing for value, measuring progress with working software, and understanding predictable system outputs. Principle 9 advocates using methods with proven track records over hoping estimates will improve. The transformation begins with individuals, per Principle 10.
No estimates - a controversial way to improve estimation with results-handoutsVasco Duarte
Often we hear that estimating a project is a must. "We can't make decisions without them" we hear often.
In this session I'll present examples of how we can predict a release date of a project without any estimates, only relying on easily available data.
I'll show how we can follow progress on a project at all times without having to rely on guesswork, and we will review how large, very large and small projects have already benefited from this in the past.
At the end of the session you will be ready to start your own
#NoEstimates journey.
Changing business of testing - Testing Assembly Helsinki 2014Vasco Duarte
Testing jobs will move to cheaper countries unless the role of testing changes. This is a trend that is happening already, we see large teams of testers being moved to other countries, simply because it is cheaper to do bad testing there!
Testing is a critical part of the product and software development process, and if we don't change its role it will slowly become obsolete. The fact is, that the traditional view of testing endangers testing jobs: now here, and later also in cheaper countries.
I propose a different view of testing. I propose that testing is about enabling business results, not just technical quality. I propose that the tester's job goes far beyond finding issues to track, but also finding users to acquire, finding methods to succeed in the software business. Testing in my view is about making businesses succeed, not about avoid failures in software.
In this presentation I'll describe how a very simple change can profoundly transform the role of testing in a way that it directly enables and supports our businesses! Testing is about making our businesses succeed!
The road ahead is not easy, and not every tester is ready to embrace this view of testing. But the road ahead is inevitable. And we have to start on that journey now!
Agile localization as a business advantage workshopVasco Duarte
Was the release of your project ever delayed when localization problems were found too late? Or worst, delayed subsequent products because of this delay? Or the fact that UI specifications quickly get out of date, leaving us with very poor quality testing by localization testing vendors. In most projects localization is still done in “waterfall” mode. Localization teams are typically involved at a very late stage of the development cycle.
We have lived through many of these problems, and we believe that Localization and Agile software development were born to be together
A quick trip to the future land of no estimatesVasco Duarte
Why do we estimate? What are the benefits we want to obtain with that practice? In this talk we'll explore the nature of estimates and offer an alternative: #NoEstimates. We'll look at some examples of how we can predict a release date of a project without any estimates, only relying on easily available data. Finally, we'll see how we can follow progress on a project at all times without having to rely on guesswork, and we will review how large, very large as well as small projects have already benefited from this in the past. At the end of the session you will be ready to start your own #NoEstimates journey, the next step in the #Agile journey.
Agile Innovation - Product Management in Turbulent timesVasco Duarte
In today’s world we are constantly confronted with the message that the competition is breeding down our necks, that the market and environment are changing and we need to change with them. And most importantly, we are told that we need to listen to our customers to be able to provide the right products.
We as a Product Managers need to be able to see beyond the basic product decisions, e.g. do we add feature A or feature B? We need to think beyond the silo of our function.
LKNL12: Kanban for the whole value streamVasco Duarte
You’ve been there before. You know better, you have a good idea to support your agile transition. Work starts, things work well at first, but then you bump against organizational barriers. Sales, Marketing, Support all have a different language and a different view into the value stream. How can we start an organizational change without a shared model of how the company should be organized?
Those are all symptoms of a gap in our Agile community: we lack a organizational model for company-wide Agile adoption and company-wide continuous improvement. Examples of this include: no company-wide flow-model (kanban) from idea to sales to idea and so on; we have no way to evaluate where the bottlenecks are the moment they are not in “our silo”. We lack a theoretical model for designing software organizations.
A theory is something that informs day-to-day decisions and experiments (e.g. PDCA). In this talk we will explain an
organizational design concept developed over several years, and use concrete examples to describe a model that you can use in support of - not only your agile adoption - but your company improvement process and your new organizational design.
Agile Beyond the Hype! – What You Really Need to Know Before You Jump In Vasco Duarte
Many companies adopt Agile because it is the natural thing to do. But do they know what they are getting into? In this talk we will use some anecdotes and lessons learned from Agile adoption to build a model that will hopefully help our companies adopt Agile in a way that affects positively their business.
Questions we try to address will include: How does Agile affect functions outside development? How to bring the benefits of Agile to non-development functions? What can Agile affect my bottom line?
Story points considered harmful - or why the future of estimation is really i...Vasco Duarte
Story points are commonly used for estimating software projects, but this document argues they are flawed and an alternative approach using number of items completed provides a better measure of progress. The document analyzes several claims made to justify using story points and finds them lacking. Data from nine real projects shows a very high correlation between story points and number of items, indicating they measure the same underlying information. Additionally, the number of items metric more accurately predicted the actual project outcomes over multiple sprints in one example project. Overall, the document argues the number of items approach provides equivalent information to story points but with less overhead and greater accuracy.
Story Points considered harmful – a new look at estimation techniquesVasco Duarte
The document discusses alternatives to using story points for estimating work in agile software development projects. It analyzes claims made about the benefits of story points and finds limited evidence to support these claims. The document proposes using the number of completed backlog items per sprint as a simpler and more efficient metric for planning, tracking progress, and estimating release dates. Correlation data from multiple projects shows story points and number of items completed tend to provide similar information about the amount of work done.
The document discusses lessons learned from adopting Agile practices in R&D organizations. It recommends starting with pilot projects to introduce Agile and learn how it impacts the organization. When expanding Agile, organizations must consider how it affects the entire R&D process and synchronize projects. Product management should be included to ensure teams develop products, not just software. Finally, adopting Agile requires optimizing the whole business system by aligning goals, sharing visions, and addressing problems that adoption uncovers in other areas of the business. The key is taking a holistic, business-oriented approach to adoption rather than focusing only on R&D.
Vasco Duarte presented on how Agile scales while Waterfall does not. He defined scaling as when the effort to manage a project increases at a slower pace than the amount of work being managed. With Waterfall requirements management, the effort to manage requirements that have dependencies increases faster than the number of requirements. However, with Agile requirements organized into user stories, features, and epics, the effort increases at a slower pace than the number of requirements. This allows Agile processes and requirements management to scale for larger projects.
From an Idea to a Vision you can implement - Vision workshopVasco Duarte
You've been there. You are tasked with implementing a product that someone else cooked up. What do do next? Follow the spec you say? Wrong!
Developing a product without this Vision is not just waste, it is bad business for you and for your customer.
Before we start implementing any product we must explore it's reason to exist, what customers it benefits and ultimately how it can help your customers (not you!) make money.
In this workshop we will take an example and go through a simple process that helps us explore a product idea to the point that a spec is just a reference, but the product comes alive in the minds of the team members.
Business Agility - taking advantage of an agile R&DVasco Duarte
Many companies have jumped on the Agile bandwagon. That's good, but what for? In this talk we explore the consequences and possible benefits of adopting Agile for your Business. It's not enough to benefit your R&D, we need to learn how Agile can help our whole company.
A paradigm shift for testing - how to increase productivity 10x!Vasco Duarte
European IT industry need to deal with a huge salary gap with developing countries.
How can we increase our productivity and quality to compensate for the salary differences? This is a systems-thinking / Lean based approach to that problem
Agile is easy! It's making it work with your business that is hardVasco Duarte
A talk about the next level of Agile adoption. How do we make it work for our business? How does Agile adoption affect our R&D, our sales, our product management and ultimately our business success?
We need proof! - Talk at Agile Estonia's Agile SaturdayVasco Duarte
This is a call to action for all Agilists out there. It is not enough to see and experience the success of Agile. For our industry to truly evolve we need to start publishing data, figures, proof that it is indeed a better approach.
Check out the companion blog post here: http://softwaredevelopmenttoday.blogspot.com/2010/02/we-need-proof-for-better-understanding.html
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.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
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.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...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 automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
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!
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
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.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
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.
23. Currently an Agile Coach in Nokia, Vasco Duarte is an experienced product and project manager, having worked in the software industry since 1997. Vasco has also been an Agile practitioner since 2004, he is one of the leaders and a catalyst in the adoption of Agile methods and an Agile culture at Nokia and previously at F-Secure. Vasco's contributions to the improvement of the software development profession can be read in his blog: http://softwaredevelopmenttoday.blogspot.com. You can follow Vasco on twitter: @duarte_vasco