The document summarizes E.F. Schumacher's criticisms of modern economics and his proposed solutions. It outlines that Schumacher argued that the current economic model focuses only on profits and growth without considering environmental and social impacts. This has led to issues like overuse of non-renewable resources and pollution from large-scale production. Schumacher's solution was to advocate for small-scale production using intermediate technology that is less harmful, more sustainable, and creates local jobs. He believed "small is beautiful" and that economics should value people and the environment, not just profits and growth.
We don't have all the answers. We don't know the best way to build software in the right way. But we do know one thing: the right way doesn't involve mindlessly following practices just because some "self-proclaimed expert" says you need to.
In this workshop we'll take a critical look at various "agile" practices and try to highlight the dogma and ceremony that has creeped in. We'll also question if the practices defined a decade ago are still applicable? If yes, have they evolved since? What are some of the original creators of these processes practicing today? And so on...
Making Sense Through Action by Dave SnowdenNaresh Jain
In order to successful scale any method or practice, it has to have some basis in theory. This presentation will use insights from complex adaptive systems theory and the cognitive sciences to lay a foundation for that theory. Seeing software development as a problem of knowledge management, the theory will elaborate a understanding of applications as the emergent property of a co-evolutionary interactions between technology capability and unarticulated user requirements.
Having established a basic theory a range of methods and tools will be elaborated. These include:
- Narrative based approaches to requirements capture (not to be confused with Story telling or story boarding) which gather thousands of fragmented self-signified anecdotes relating to real and imagined needs within a user community and allow interpretation and integration into project planning.
- Approaches to project planning and implementation that focus on the creation of self-organising teams of specialists and users to create novel approaches, supported by evidence to previously intractable problems. This is particularly relevant to the 5-10% of any major project which creates 95-90% of the grief.
- The integration of tools such as blogs, wiki's etc into the development environment. Too often corporate environments over-constrain those tools into over rigid structures which destroy their utility.
Future Shock by Alvin Toffler, published in 1970, discusses how rapid technological changes can psychologically impact individuals unprepared for the future. The book argues that society is moving faster than people's ability to adapt, causing "future shock." It examines how new technologies have modernized and accelerated communication, information sharing, and learning, but that people must learn to keep pace with an increasingly technology-driven world in order to avoid feelings of disorientation from constant change.
This document defines and discusses the concepts of economies and diseconomies of scale. It begins by defining economies of scale as the cost advantages that firms obtain due to expansion. There are two types of economies of scale: internal, experienced by individual firms, and external, experienced by entire industries. Internal economies include labor, managerial, marketing, financial, technical, and risk-bearing economies. External economies include localization, information, by-product, and transportation/marketing economies. The document also discusses diseconomies of scale, which are higher costs due to overexpansion. Internal diseconomies include technical, risk-taking, administrative, managerial, and labor issues. External diseconomies arise from increased competition and scarcity of
Game on: 16 design patterns for user engagementNadya Direkova
The document discusses 16 design patterns for using game mechanics to create user engagement in social web applications. It covers patterns for attracting first-time users ("Come and Try It") like visual storytelling, tutorials, and reward schedules. Patterns for building community ("Bring Your Friends") include forming teams, social feedback, and sharing milestones. Patterns for repeat visits ("Come Back") consist of advanced user paths, content unlocks over time, quest queues, and using scarcity and time pressure. The document stresses measuring the effects of these patterns and iterating based on metrics.
The document summarizes E.F. Schumacher's criticisms of modern economics and his proposed solutions. It outlines that Schumacher argued that the current economic model focuses only on profits and growth without considering environmental and social impacts. This has led to issues like overuse of non-renewable resources and pollution from large-scale production. Schumacher's solution was to advocate for small-scale production using intermediate technology that is less harmful, more sustainable, and creates local jobs. He believed "small is beautiful" and that economics should value people and the environment, not just profits and growth.
We don't have all the answers. We don't know the best way to build software in the right way. But we do know one thing: the right way doesn't involve mindlessly following practices just because some "self-proclaimed expert" says you need to.
In this workshop we'll take a critical look at various "agile" practices and try to highlight the dogma and ceremony that has creeped in. We'll also question if the practices defined a decade ago are still applicable? If yes, have they evolved since? What are some of the original creators of these processes practicing today? And so on...
Making Sense Through Action by Dave SnowdenNaresh Jain
In order to successful scale any method or practice, it has to have some basis in theory. This presentation will use insights from complex adaptive systems theory and the cognitive sciences to lay a foundation for that theory. Seeing software development as a problem of knowledge management, the theory will elaborate a understanding of applications as the emergent property of a co-evolutionary interactions between technology capability and unarticulated user requirements.
Having established a basic theory a range of methods and tools will be elaborated. These include:
- Narrative based approaches to requirements capture (not to be confused with Story telling or story boarding) which gather thousands of fragmented self-signified anecdotes relating to real and imagined needs within a user community and allow interpretation and integration into project planning.
- Approaches to project planning and implementation that focus on the creation of self-organising teams of specialists and users to create novel approaches, supported by evidence to previously intractable problems. This is particularly relevant to the 5-10% of any major project which creates 95-90% of the grief.
- The integration of tools such as blogs, wiki's etc into the development environment. Too often corporate environments over-constrain those tools into over rigid structures which destroy their utility.
Future Shock by Alvin Toffler, published in 1970, discusses how rapid technological changes can psychologically impact individuals unprepared for the future. The book argues that society is moving faster than people's ability to adapt, causing "future shock." It examines how new technologies have modernized and accelerated communication, information sharing, and learning, but that people must learn to keep pace with an increasingly technology-driven world in order to avoid feelings of disorientation from constant change.
This document defines and discusses the concepts of economies and diseconomies of scale. It begins by defining economies of scale as the cost advantages that firms obtain due to expansion. There are two types of economies of scale: internal, experienced by individual firms, and external, experienced by entire industries. Internal economies include labor, managerial, marketing, financial, technical, and risk-bearing economies. External economies include localization, information, by-product, and transportation/marketing economies. The document also discusses diseconomies of scale, which are higher costs due to overexpansion. Internal diseconomies include technical, risk-taking, administrative, managerial, and labor issues. External diseconomies arise from increased competition and scarcity of
Game on: 16 design patterns for user engagementNadya Direkova
The document discusses 16 design patterns for using game mechanics to create user engagement in social web applications. It covers patterns for attracting first-time users ("Come and Try It") like visual storytelling, tutorials, and reward schedules. Patterns for building community ("Bring Your Friends") include forming teams, social feedback, and sharing milestones. Patterns for repeat visits ("Come Back") consist of advanced user paths, content unlocks over time, quest queues, and using scarcity and time pressure. The document stresses measuring the effects of these patterns and iterating based on metrics.
Outside In - Behaviour Driven Development (BDD)Naresh Jain
The BDD Workshop offers a comprehensive, hands-on introduction to behavior driven development via an interactive-demo.
Over the past decade, eXtreme Programming practices like Test-Driven Development (TDD) and Behaviour Driven Development (BDD) have fundamentally changed software development processes and inherently how engineers work. Practitioners claim that it has helped them significantly improve their collaboration with business, development speed, design & code quality and responsiveness to changing requirements. Software professionals across the board, from Internet startups to medical device companies to space research organizations, today have embraced these practices.
This workshop explores the foundations of TDD & BDD with the help of various patterns, strategies, tools and techniques.
This document summarizes Muhammad Shoaib's first presentation at Iqra University on self-management skills. The presentation covered topics like career planning, self-esteem, positive thinking, stress management, time management, communication skills, team building, conflict management, negotiation, setting goals, and stress management. Shoaib learned from each chapter and how to apply the skills to his daily life and future objectives. The conclusion expresses gratitude for the opportunity to present and learn.
Economies of scale refer to cost advantages that businesses obtain from increased scale of production. When a business expands, it can spread fixed costs over more units, lowering average costs. Diseconomies of scale occur when a business grows too large and average costs begin increasing due to issues like difficulty controlling operations and communication problems. Internal economies come from a single business growing, while external economies arise from industry-wide growth, such as improved infrastructure or specialized suppliers. Common sources of internal economies include bulk purchasing discounts, marketing efficiencies, and specialized management.
Value Driven Development by Dave Thomas Naresh Jain
Agile, OOP... are like good hygiene in the kitchen, it results in meals with consistent quality and predictable prep and service times. It doesn't result in great meals nor substantially impact the ROI! Lean Thinking clearly shows that the only way to make a significant impact is to improve the value chain by improving flow. If everyone is following best practices no one has competitive advantage. Major improvements in the value chain depend on continued disruptive innovations. Innovations leverage people and their ideas. We use case studies to illustrate the different business and technical innovations and their impact. We conclude with a discussion of how to build and leverage an innovation culture versus a sprint death march when dealing with high value time to market projects.
More details: https://confengine.com/agile-india-2017/proposal/3608/value-driven-development-maximum-impact-maximum-speed
The document discusses self-management strategies for changing one's own behavior. It defines self-management and explains that it involves using behavior modification techniques to control a target behavior. The document outlines several self-management strategies including goal setting, self-monitoring, antecedent manipulation, behavioral contracting, consequences, social support, and self-instructions. It provides details on how to develop a self-management plan, selecting the appropriate strategy, evaluating progress, and maintaining behavior change over time.
This document describes a self-management intervention to increase daily flossing. The student was not flossing regularly and wanted to improve their gum health. A contingency plan was created where the student would lose the use of their iPod for a day if they did not floss each night. Graphs show that flossing increased under this intervention compared to baseline levels. Some problems occurred after the student moved, like misplacing their floss. The intervention was adapted by adding a contingency to purchase new floss daily if needed. Overall, the intervention successfully increased the student's daily flossing behavior.
1. The document summarizes Mati ur Rehman's first presentation at Iqra University on topics related to self-management skills including career planning, self-esteem, positive thinking, stress management, and time management.
2. Mati ur Rehman achieved gaining different perspectives on each topic presented and learning how to apply the lessons to achieving goals and handling limitations.
3. Future topics that would be covered include team building & management, conflict management, and negotiation. Maintaining a positive mindset and taking action are emphasized as keys to achieving goals.
The document discusses managerial competencies and their importance for effective management. It defines competency as a combination of knowledge, skills, behaviors and attitudes that contribute to effectiveness. Managerial competencies are sets of abilities needed to be effective in various positions and organizations. Six core competencies are identified: communication, planning and administration, teamwork, strategic action, multicultural awareness, and self-management. Each competency is then defined and its components or foundations are explained.
Open educational resources (oer) power pointrobinec
Open educational resources (OER) are teaching and learning materials that are freely available online for anyone to use, adapt and share. OER include full courses, textbooks, modules, videos and other materials. There are several advantages to using OER, such as reducing costs for students, increasing accessibility of educational resources worldwide, and allowing for customization and incorporation of updated content. However, some disadvantages include the effort required to evaluate and validate large volumes of OER materials, lack of funds to support ongoing updates and maintenance, and potential issues with attribution, copyright and access to technology for disadvantaged students.
This document discusses self-management and time management techniques. It begins by defining SMART goals, which are goals that are specific, measurable, attainable, relevant, and time-bound. It provides examples of setting SMART goals in different areas of life including personal development, education, health, and career. Regarding time management, it notes that time is a limited resource and provides strategies for effective time management such as getting organized, prioritizing tasks, avoiding procrastination, balancing work and personal life, and planning for contingencies. The overall document provides guidance on goal setting and time management to help with self-management.
The Agile Scaling Model (ASM) provides the context and advice for effectively tailoring agile techniques. It describes how to extend the agile construction life cycle into a full-fledged disciplined agile delivery life cycle. It then describes how to tailor agile practices to address scaling factors which an agile team may face, including team size, physical distribution, organizational distribution, regulatory compliance, organizational complexity, technical complexity, and enterprise disciplines (such as enterprise architecture, reuse, and portfolio management).
The document discusses scaling agile practices from Scrum to larger projects and organizations. It introduces IBM's Agile Scaling Model which includes core agile development, Disciplined Agile Delivery, and Agility@Scale. Key practices that need to be scaled include product backlogs, roles, release planning, sprint planning, and sprint demos to address factors like large team sizes, geographic distribution, and organizational complexity. Case studies are provided on how organizations have successfully scaled agile.
This document provides an overview of Lean and Agile concepts from Innovel LLC. It discusses Lean as a way to minimize waste and maximize value delivery to customers. Agile is described as an approach for incremental delivery of products and services that minimizes risk. Scrum is presented as a project management framework for incremental delivery. The relationship between Lean, Agile and Scrum is explored, and examples of companies using these approaches are provided. Key Lean concepts like value streams, forms of waste and continuous improvement are summarized.
AGILE PM A trade-off between proactivity and reactivityEmiliano Soldi
An exponential increase in complexity, a strong reduction of a product's lifecycle and market time frames are drastically challenging projects and their success.
In a context like this, what tools and techniques can be used by project management?
A proactive approach would seem to be highly effective.
But, is trying to anticipate any decision of an unpredictable future the best solution?
Alternatively, a reactive approach puts less effort on planning and greater attention in tackling any change.
But, are we sure that we can be completely reliant on this way?
The document discusses the role of business analysts in agile software development. It argues that business analysts play an important role in helping agile teams meet business needs, either as the product owner or by supporting the product owner. When adopting agile, teams should initially focus on becoming more effective before emphasizing requirements or the business analyst's role. Over time, the business analyst should take a more prominent role in reducing unnecessary work through improved requirements analysis. Adopting agile processes does not remove the need for requirements; it changes the nature of requirements from push to pull based on business needs.
The Agile PMO: Ensuring visibility and governanceMatt Holitza
The document discusses how an agile project management office (PMO) can help ensure visibility and governance of agile projects. It outlines some pitfalls that can jeopardize a traditional PMO and attributes of a successful PMO. The document then discusses how agile benefits PMOs by helping them align projects to goals, improve success rates over time, enhance competence, develop standards, promote a collaborative tone, and encourage continuous learning. An agile PMO can achieve these benefits through practices like a whole team approach, transparency, integrated tooling, and continuous process improvement.
Agile Marketing for SEO - SMX West 2013 - Dave Lloyd, AdobeDave Lloyd
Slides from SMX West presentation. Covers in-house SEO, project management, Agile methodology, maturity model for Agile adoption, and how to execute on Agile internally. Follow me at @davelloyd1
Agile and lean product development the fundamentalsRussell Pannone
The document discusses delivering value early and often through agile development practices to gain competitive advantages. It emphasizes cross-functional collaboration, continuous delivery of working software increments, early defect discovery, eliminating waste, and frequent feedback to improve. The goal is satisfying customers through adaptive teams that can sustain a constant development pace.
This document discusses challenges and best practices for distributed agile project management. It begins by defining agile project management and explaining why agile practices are needed in today's business environment. It then notes that distributed teams are increasingly common due to globalization and outsourcing. However, agile projects and distributed teams have some incompatible elements, such as lack of face-to-face communication and difficulty building trust over distance. The document outlines challenges like communication breakdowns, infrastructure issues, and fear of failure on distributed agile projects. It concludes by recommending best practices for distributed agile projects, including focusing on people relationships, improving communication structures and tools, establishing clear roles and responsibilities, and ensuring proper infrastructure.
The document discusses effective project management. It argues that being "agile" is less important than being effective. Projects should be viewed as releasing products, and a project's success is determined by how well its processes align with the product's maturity. The document outlines a 5-step approach: 1) Don't focus on being agile but on being effective; 2) View projects as releasing products; 3) Align a project's processes with a product's maturity to determine if it is born a winner or loser; check a project's "DNA".
Lean Software Development Alan ShallowayValtech UK
The document discusses extending lean principles from manufacturing to software product development. It notes that software development is more like product development, which involves discovery, rather than manufacturing. It argues for redefining lean based on principles of product development flow and systems thinking. The document advocates applying lean thinking throughout the enterprise to achieve business agility, portfolio management, team agility, proper management, and technical skills in order to achieve enterprise agility.
This document provides an overview of a webcast presentation given by Scott W. Ambler from IBM on busting myths about agile development. The presentation explores results from several surveys on agile practices. Some key findings presented include that agile teams have around a 70% success rate compared to 66% for traditional teams, and that agile is being used for teams of all sizes, with distributed teams, and in regulated environments. The presentation provides context using the Agile Scaling Model and examines myths around scaling agile. It aims to show that agile can work for many different situations beyond just small, co-located teams on simple projects.
Outside In - Behaviour Driven Development (BDD)Naresh Jain
The BDD Workshop offers a comprehensive, hands-on introduction to behavior driven development via an interactive-demo.
Over the past decade, eXtreme Programming practices like Test-Driven Development (TDD) and Behaviour Driven Development (BDD) have fundamentally changed software development processes and inherently how engineers work. Practitioners claim that it has helped them significantly improve their collaboration with business, development speed, design & code quality and responsiveness to changing requirements. Software professionals across the board, from Internet startups to medical device companies to space research organizations, today have embraced these practices.
This workshop explores the foundations of TDD & BDD with the help of various patterns, strategies, tools and techniques.
This document summarizes Muhammad Shoaib's first presentation at Iqra University on self-management skills. The presentation covered topics like career planning, self-esteem, positive thinking, stress management, time management, communication skills, team building, conflict management, negotiation, setting goals, and stress management. Shoaib learned from each chapter and how to apply the skills to his daily life and future objectives. The conclusion expresses gratitude for the opportunity to present and learn.
Economies of scale refer to cost advantages that businesses obtain from increased scale of production. When a business expands, it can spread fixed costs over more units, lowering average costs. Diseconomies of scale occur when a business grows too large and average costs begin increasing due to issues like difficulty controlling operations and communication problems. Internal economies come from a single business growing, while external economies arise from industry-wide growth, such as improved infrastructure or specialized suppliers. Common sources of internal economies include bulk purchasing discounts, marketing efficiencies, and specialized management.
Value Driven Development by Dave Thomas Naresh Jain
Agile, OOP... are like good hygiene in the kitchen, it results in meals with consistent quality and predictable prep and service times. It doesn't result in great meals nor substantially impact the ROI! Lean Thinking clearly shows that the only way to make a significant impact is to improve the value chain by improving flow. If everyone is following best practices no one has competitive advantage. Major improvements in the value chain depend on continued disruptive innovations. Innovations leverage people and their ideas. We use case studies to illustrate the different business and technical innovations and their impact. We conclude with a discussion of how to build and leverage an innovation culture versus a sprint death march when dealing with high value time to market projects.
More details: https://confengine.com/agile-india-2017/proposal/3608/value-driven-development-maximum-impact-maximum-speed
The document discusses self-management strategies for changing one's own behavior. It defines self-management and explains that it involves using behavior modification techniques to control a target behavior. The document outlines several self-management strategies including goal setting, self-monitoring, antecedent manipulation, behavioral contracting, consequences, social support, and self-instructions. It provides details on how to develop a self-management plan, selecting the appropriate strategy, evaluating progress, and maintaining behavior change over time.
This document describes a self-management intervention to increase daily flossing. The student was not flossing regularly and wanted to improve their gum health. A contingency plan was created where the student would lose the use of their iPod for a day if they did not floss each night. Graphs show that flossing increased under this intervention compared to baseline levels. Some problems occurred after the student moved, like misplacing their floss. The intervention was adapted by adding a contingency to purchase new floss daily if needed. Overall, the intervention successfully increased the student's daily flossing behavior.
1. The document summarizes Mati ur Rehman's first presentation at Iqra University on topics related to self-management skills including career planning, self-esteem, positive thinking, stress management, and time management.
2. Mati ur Rehman achieved gaining different perspectives on each topic presented and learning how to apply the lessons to achieving goals and handling limitations.
3. Future topics that would be covered include team building & management, conflict management, and negotiation. Maintaining a positive mindset and taking action are emphasized as keys to achieving goals.
The document discusses managerial competencies and their importance for effective management. It defines competency as a combination of knowledge, skills, behaviors and attitudes that contribute to effectiveness. Managerial competencies are sets of abilities needed to be effective in various positions and organizations. Six core competencies are identified: communication, planning and administration, teamwork, strategic action, multicultural awareness, and self-management. Each competency is then defined and its components or foundations are explained.
Open educational resources (oer) power pointrobinec
Open educational resources (OER) are teaching and learning materials that are freely available online for anyone to use, adapt and share. OER include full courses, textbooks, modules, videos and other materials. There are several advantages to using OER, such as reducing costs for students, increasing accessibility of educational resources worldwide, and allowing for customization and incorporation of updated content. However, some disadvantages include the effort required to evaluate and validate large volumes of OER materials, lack of funds to support ongoing updates and maintenance, and potential issues with attribution, copyright and access to technology for disadvantaged students.
This document discusses self-management and time management techniques. It begins by defining SMART goals, which are goals that are specific, measurable, attainable, relevant, and time-bound. It provides examples of setting SMART goals in different areas of life including personal development, education, health, and career. Regarding time management, it notes that time is a limited resource and provides strategies for effective time management such as getting organized, prioritizing tasks, avoiding procrastination, balancing work and personal life, and planning for contingencies. The overall document provides guidance on goal setting and time management to help with self-management.
The Agile Scaling Model (ASM) provides the context and advice for effectively tailoring agile techniques. It describes how to extend the agile construction life cycle into a full-fledged disciplined agile delivery life cycle. It then describes how to tailor agile practices to address scaling factors which an agile team may face, including team size, physical distribution, organizational distribution, regulatory compliance, organizational complexity, technical complexity, and enterprise disciplines (such as enterprise architecture, reuse, and portfolio management).
The document discusses scaling agile practices from Scrum to larger projects and organizations. It introduces IBM's Agile Scaling Model which includes core agile development, Disciplined Agile Delivery, and Agility@Scale. Key practices that need to be scaled include product backlogs, roles, release planning, sprint planning, and sprint demos to address factors like large team sizes, geographic distribution, and organizational complexity. Case studies are provided on how organizations have successfully scaled agile.
This document provides an overview of Lean and Agile concepts from Innovel LLC. It discusses Lean as a way to minimize waste and maximize value delivery to customers. Agile is described as an approach for incremental delivery of products and services that minimizes risk. Scrum is presented as a project management framework for incremental delivery. The relationship between Lean, Agile and Scrum is explored, and examples of companies using these approaches are provided. Key Lean concepts like value streams, forms of waste and continuous improvement are summarized.
AGILE PM A trade-off between proactivity and reactivityEmiliano Soldi
An exponential increase in complexity, a strong reduction of a product's lifecycle and market time frames are drastically challenging projects and their success.
In a context like this, what tools and techniques can be used by project management?
A proactive approach would seem to be highly effective.
But, is trying to anticipate any decision of an unpredictable future the best solution?
Alternatively, a reactive approach puts less effort on planning and greater attention in tackling any change.
But, are we sure that we can be completely reliant on this way?
The document discusses the role of business analysts in agile software development. It argues that business analysts play an important role in helping agile teams meet business needs, either as the product owner or by supporting the product owner. When adopting agile, teams should initially focus on becoming more effective before emphasizing requirements or the business analyst's role. Over time, the business analyst should take a more prominent role in reducing unnecessary work through improved requirements analysis. Adopting agile processes does not remove the need for requirements; it changes the nature of requirements from push to pull based on business needs.
The Agile PMO: Ensuring visibility and governanceMatt Holitza
The document discusses how an agile project management office (PMO) can help ensure visibility and governance of agile projects. It outlines some pitfalls that can jeopardize a traditional PMO and attributes of a successful PMO. The document then discusses how agile benefits PMOs by helping them align projects to goals, improve success rates over time, enhance competence, develop standards, promote a collaborative tone, and encourage continuous learning. An agile PMO can achieve these benefits through practices like a whole team approach, transparency, integrated tooling, and continuous process improvement.
Agile Marketing for SEO - SMX West 2013 - Dave Lloyd, AdobeDave Lloyd
Slides from SMX West presentation. Covers in-house SEO, project management, Agile methodology, maturity model for Agile adoption, and how to execute on Agile internally. Follow me at @davelloyd1
Agile and lean product development the fundamentalsRussell Pannone
The document discusses delivering value early and often through agile development practices to gain competitive advantages. It emphasizes cross-functional collaboration, continuous delivery of working software increments, early defect discovery, eliminating waste, and frequent feedback to improve. The goal is satisfying customers through adaptive teams that can sustain a constant development pace.
This document discusses challenges and best practices for distributed agile project management. It begins by defining agile project management and explaining why agile practices are needed in today's business environment. It then notes that distributed teams are increasingly common due to globalization and outsourcing. However, agile projects and distributed teams have some incompatible elements, such as lack of face-to-face communication and difficulty building trust over distance. The document outlines challenges like communication breakdowns, infrastructure issues, and fear of failure on distributed agile projects. It concludes by recommending best practices for distributed agile projects, including focusing on people relationships, improving communication structures and tools, establishing clear roles and responsibilities, and ensuring proper infrastructure.
The document discusses effective project management. It argues that being "agile" is less important than being effective. Projects should be viewed as releasing products, and a project's success is determined by how well its processes align with the product's maturity. The document outlines a 5-step approach: 1) Don't focus on being agile but on being effective; 2) View projects as releasing products; 3) Align a project's processes with a product's maturity to determine if it is born a winner or loser; check a project's "DNA".
Lean Software Development Alan ShallowayValtech UK
The document discusses extending lean principles from manufacturing to software product development. It notes that software development is more like product development, which involves discovery, rather than manufacturing. It argues for redefining lean based on principles of product development flow and systems thinking. The document advocates applying lean thinking throughout the enterprise to achieve business agility, portfolio management, team agility, proper management, and technical skills in order to achieve enterprise agility.
This document provides an overview of a webcast presentation given by Scott W. Ambler from IBM on busting myths about agile development. The presentation explores results from several surveys on agile practices. Some key findings presented include that agile teams have around a 70% success rate compared to 66% for traditional teams, and that agile is being used for teams of all sizes, with distributed teams, and in regulated environments. The presentation provides context using the Agile Scaling Model and examines myths around scaling agile. It aims to show that agile can work for many different situations beyond just small, co-located teams on simple projects.
The document describes the Situational Innovation Transfer (SIT) method for fostering innovation and creative thinking. SIT has five core layers: tools, principles, facilitation, project management, and organizational innovation. The core tools and principles form the basis of the method. Facilitation helps apply the tools and principles effectively in multidisciplinary teams. Project management ensures ideas are implemented. Organizational innovation embeds the method across an organization to sustain innovation culture. In total, SIT provides a systematic and layered approach to innovation through unique thinking tools, mindsets, skills, and organizational structures.
The document provides an overview of agile principles and practices. It discusses what agile is, principles behind the agile manifesto like satisfying customers through early delivery, welcoming changing requirements, having business and developers work together daily, and using face-to-face conversation. It also covers agile practices like Scrum, Kanban, and product backlogs. Challenges of adopting agile like managing projects and contracting are addressed as well as common causes of failed agile projects like lack of management support and understanding of agile.
This document provides an introduction to the Eclipse Process Framework Composer tool. It discusses how the tool can be used to manage libraries of reusable method content and assemble customized processes for projects. The tool addresses the needs of aligning flexible development processes with business processes and supporting modern agile development practices. It separates reusable method content from its application in processes to provide a knowledge base and process engineering capabilities.
Kuali OLE: Deep Library Collaboration and the Release of a Community-Sourced ...Robert H. McDonald
This document summarizes a presentation about Kuali OLE, an open source library management system created through collaboration between multiple universities. It describes the journey to create a collaborative community to develop the system, including establishing functional councils, technical architecture choices, and community organization. It also discusses plans for deployment, creating an ecosystem of vendors, investing in the community, and expanding globally.
The document provides an overview of Agile software development. It defines Agile as a collection of principles and practices aimed at improving collaboration, reducing documentation overhead, and making development teams more responsive to changes. The document discusses Agile methods like Scrum and Extreme Programming. It also covers Agile concepts such as user stories, velocity, and retrospectives. The document aims to help attendees understand what Agile is, its benefits, and how it differs from traditional waterfall methods. Training and certification options in Agile are also listed.
The document discusses the Project Management Institute's views on agile and lean methods. It notes that while companies are unfamiliar with agile practices, agile uses self-managing techniques and effective communication. Within the PMI, some believe agile is only for software development, not general project management. However, agile proponents are creating a community within PMI to improve traditional practices. Both agile and lean methods aim to reduce unnecessary overhead and focus on efficiency.
1. BDD is an approach to software development that focuses on implementing applications by describing their behavior from the perspective of stakeholders.
2. BDD originated from limitations in test-driven development (TDD), where the focus on testing at a granular level led to emergent rather than intentional design.
3. Key principles of BDD include focusing on delivering stakeholder value, describing everything in terms of behavior, and practicing outside-in development.
Session Description:
Mobile technology and social media are straining the resources of information companies. On top of their regular responsibilities, Editorial is expected to work with a wider range of media types, such as blogs and videos, some of which they have no experience in. Development needs to syndicate content to an array of smartphones and tablets.
This session offers a portfolio approach to creating successful, profitable mobile and social products. It presents frameworks for:
*Evaluating and supplementing existing talent, content and technology,
*Structuring the organization to be responsive and effective,
*Evaluating and funding new business ideas,
*Prioritizing initiatives so that the most promising are not starved of resources and the “”moonshots”" get a fighting chance, and
*Avoiding the pitfalls that arise from “”not knowing what you don’t know.”"
Learning Points:
This session will address key questions and provide actionable solutions for effectively building out your content offerings for smartphones, tablets and social media:
1. Budget – Are there funds available to support a mobile initiative? What is the new product development process? What features, functions and content should be included?
2. Organization – Is the current organizational structure conducive to creating mobile offerings?
3. Publishing – Can I use or augment my existing streams or do I need new ones?
4. Talent – Do I have the talent I need? If not, should I hire or outsource or train?
Similar to Small Is Beautiful by Sanjiv Augustine (20)
Problem Solving Techniques For Evolutionary DesignNaresh Jain
In this workshop, Naresh Jain explains what are the core techniques one should master to effectively practice evolutionary design while solving real-world problems. To summarize:
1. Eliminate Noise - Distill down the crux of the problem
2. Divide and Conquer to prioritize and focus on the most important part
3. Add constraints to future simplify the problem
4. Come up with a simple design to incrementally build your solution
5. Refactor: Pause, look for a much simpler alternative
6. Be ready to throw away your solution & start again
Agile India 2019 Conference Welcome NoteNaresh Jain
We are super excited to announce the 15th edition of Agile India 2019, Asia's Largest and Premier International conference on Leading Edge Software Development Methods. Agile India is hosted by Agile Alliance and organized by Agile Software Community of India, a non-profit registered society founded in 2004 with a vision to evangelize new, better ways of building products & services that delight the users.
Over the last 15 years, we've organized 57 conferences across 13 cities in India. We've hosted 1,000+ speakers from 38 countries, who have delivered 1,200+ sessions to 10,000+ attendees. We continue to be a non-profit, volunteer-run community conference.
Agenda
* Agile Coach Camp - March 17th
* Pre-Conference Workshops – March 18th
* Conference Days
** Agile Mindset Day - March 19th
** Business Agility Day - March 20th
** Design Innovation Day - March 21st
** Continuous Delivery and DevOps Day - March 22nd
* Post-Conference Workshops – March 23rd and 24th
More details: https://2019.agileindia.org
A resilient organizational can not only adapt and respond to incremental change but more importantly, can respond to sudden disruptions and also, be the source of disruption in order to prosper and flourish.
The traditional risk management approach focuses too much on defensive (stopping bad things happen) thinking versus a more progressive (making good things happen) thinking. Being defensive requires consistency across the organization and this is where methodologies like Plan-Do-Check-Act (PDCA) come in. However, PDCA approach does not bake in the required progressive thinking and flexibility required for a fast company organization which operates in a volatile environment.
Professor David Denyer of Cranfield University has recently published a very interesting research report on Organizational Resilience. He has identified the following four quadrants across to help us think about organizational resilience:
* preventative control (defensive consistency)
* mindful action (defensive flexibility)
* performance optimization (progressive consistency)
* adaptive innovation (progressive flexibility)
In this talk, I'll share my personal experience of using this thinking to help an organization to scale their product to Millions of users. I've dive deep into how we structured our organization for Structural Agility and how we set-up a very lightweight governance model using OKRs to drive the necessary flexible and progressive thinking.
More details: https://confengine.com/agile-india-2019/proposal/8216/organisational-resilience-design-your-organisation-to-flourish-not-merely-survive
Conference Link: https://2019.agileindia.org
Looking to move to Continuous Delivery? Worried about the quality of your the code? Helping your developers understand clean-code practices and getting the right testing strategy in place can take a while. What should you do to control the quality of the incoming code till then? This talk shares our experience of using PRRiskAdvisor to gradually educate and influence developers to write better code and also help the code reviewer to be more effective at their reviews.
Every time a developer raises a pull-request, PRRiskAdvisor analyzes the files that were changed and publishes a report on the pull request itself with the overall risk associated with this pull request and also risk associated with each file. It also runs static code analysis using SonarQube and publishes the configured violations as comments on the pull request. This way the reviewer just has to look at the pull request to get a decent idea of what it means to review this pull request. If there are too many violations, then PRRiskAdvisor can also automatically reject the pull request.
By doing this, we saw our developers starting paying more attention to clean code practices and hence the overall quality of the incoming code improved, while we worked on putting the right engineering practices and testing strategy in place.
More details: https://confengine.com/last-conference-canberra-2018/proposal/7294/improving-the-quality-of-incoming-code
Conference Link: https://2019.agileindia.org
Here is a quick summary of Agile India 2018 Conference, Asia's Largest and Premier Conference on Business Agility, Design Innovation, Digital Transformation, Continuous Delivery, DevOps, Agile, Scrum, eXtreme Programming, Lean, Kanban, Enterprise Agile, Lean Startup, Research, and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 4 - 11 March 2018 at Taj West End, Bangalore. More details: https://2018.agileindia.org
We are very excited to announce the 14th edition of Agile India Conference (https://2018.agileindia.org/) with brand new themes and a fabulous lineup of speakers. Agile India is Asia's Largest & Premier International conference on Leading Edge Software Development Methods.
Meet:
* Alan Cooper - The Father of Visual Basic, Creator of Goal-directed Design methodology and inventor of the Persona concept
* Steve Denning - Author of several books on Management, Leadership, Innovation and Organizational Storytelling
* Linda Rising - Author of four books, most recently the Fearless Change
* Gregor Hohpe - Author of Enterprise Integration Patterns. Technical Director at Google Cloud Computing
* James Stewart - Co-founder of the Government Digital Service and x-Deputy CTO of the UK Government
* Bjarte Bogsnes - Author of Implementing Beyond Budgeting, Chairman of Beyond Budgeting Roundtable and Senior Advisor Performance Framework at Statoil
* Dr. Denis Bauer - Team Leader and Research Scientist in Cloud Computing in Transformational Bioinformatics at CSIRO
* Jeff Patton - Author of User Story Mapping and the person responsible for bringing user-centered design thinking to Agile world
* Peter Jacobs - Chief Information Officer and board member of ING Bank Netherlands
* Nils Kappeyne - VP & CIO for Integrated Gas & New Energies at Shell
* And 70 more thought leaders from 16 countries - https://2018.agileindia.org/speakers/
The program spreads across 8 days (March 4-11th 2018, Bengaluru) with two pre-conference plus two post-conference workshop days and four days of conferences in between:
* March 4-5th: Pre-Conference Workshops from our international experts
* March 6th: Business Agility Day - Hosted by Agile Alliance
* March 7th: Design Innovation Day - Hosted by Cooper
* March 8th: Digital Transformation Day
* March 9th: DevOps and Continuous Delivery Day - Hosted by Red Hat
* March 10-11th: Post-Conference Workshops from our international experts
Schedule
========
Check out conference schedule for the lineup of workshops and speakers. https://confengine.com/agile-india-2018/schedule
Tickets
=======
Conference registration is now open and Smart Price offers are going away soon. Register now for best deals!! https://confengine.com/agile-india-2018/register
Check out the exciting offers for bulk registrations - https://2018.agileindia.org/agile-india-2018-bulk-booking-offers/.
Sponsors
========
We thank Agile Alliance, Cooper, RedHat, Scrum.org, Shell, AddTeq/Atlassian, Scaled Agile, ICAgile and Scrum Alliance for sponsoring the conference. If your organization wants to support this non-profit, volunteer-run conference, please check out sponsorship options https://confengine.com/agile-india-2018/sponsor#guide
Agile India 2018 Conference is Asia's Largest and Premier Conference on Business Agility, Design Innovation, Digital Transformation, Continuous Delivery, DevOps, Agile, Scrum, eXtreme Programming, Lean, Kanban, Enterprise Agile, Lean Startup, Research, and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 4 - 11 March 2018 at Taj West End, Bangalore. More details: https://2018.agileindia.org
Agile India 2018 Conference is Asia's Largest and Premier Conference on Business Agility, Design Innovation, Digital Transformation, Continuous Delivery, DevOps, Agile, Scrum, eXtreme Programming, Lean, Kanban, Enterprise Agile, Lean Startup, Research, and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 4 - 11 March 2018 at Taj West End, Bangalore. More details: https://2018.agileindia.org
Pilgrim's Progress to the Promised Land by Robert VirdingNaresh Jain
When migrating to Elixir/OTP from other languages and systems a number of issues will always crop up. The trick is to make sure that these issues don't become problems. This talk will look at some of the more common ones and what to do about them to make sure they don't become problems.
More details: https://confengine.com/functional-conf-2017/proposal/5138/pilgrims-progress-to-the-promised-land
Conference: https://functionalconf.com
Concurrent languages are Functional by Francesco CesariniNaresh Jain
The document discusses concurrency in functional programming languages. It explains that there are two approaches to concurrency: mutable state and immutable state. Immutable state avoids issues with corrupt state that can occur with mutable state. Functional languages with immutable state and message passing, like Erlang, allow for easy distribution across computing resources from embedded devices to high-performance supercomputers. The document emphasizes how immutability, concurrency, and distribution enable scalability, reliability, and parallelism.
Erlang from behing the trenches by Francesco CesariniNaresh Jain
Erlang is a programming language designed for the Internet Age, although it pre-dates the Web. It is a language designed for multi-core computers, although it pre-dates them too. It is a “beacon language”, to quote Haskell guru Simon Peyton-Jones, in that it more clearly than any other language demonstrates the benefits of concurrency-oriented programming. In this talk, I will introduce Erlang from behind the trenches. By introducing the major language constructs, describe their benefits and discuss the problems Erlang is ideal to solve. I will be doing so from a personal prospective, with anecdotes from my time as an intern at the Ericsson computer science lab at a time when the language was being heavily influenced and later when working on the OTP R1 release.
More details: https://confengine.com/functional-conf-2017/proposal/4787/an-introduction-to-erlang-from-behind-the-trenches
Anatomy of an eCommerce Search Engine by Mayur DatarNaresh Jain
This document discusses search architecture and optimization for e-commerce platforms. It describes how search is a critical feature that powers recommendations and sales. Key challenges include large catalogs that change frequently, diverse user needs like geo-specific ranking, and balancing multiple objectives. The document outlines the technical infrastructure supporting search, including serving architecture, indexing workflows, and approaches to improve quality like query understanding and personalization.
Setting up Continuous Delivery Culture for a Large Scale Mobile AppNaresh Jain
Hike is a mobile-first, messaging platform that is used by 100 million users to exchange 40 billion messages/month. Hike app is available on Android, iOS and Windows phone. On the back-end, we’ve 100+ macro-services in Java, Python, Ruby, Go and Elixir. While setting up a Continuous Delivery pipeline, we ran into a series of technical challenges. However it was more important to address the organisational/behavioural challenges to ensure a sustainable culture shift in the company.
In this talk, I cover how we went about:
* Setup a trunk-based development model
* Decentralised our build & test environments using Docker and Jenkins
* Segregated and containerised our macro-services
* Refactored the mobile apps to be more container friendly
* Setup a mobile device farm using STF
* Improved the quality of code-reviews using PRBuilder & PRRiskAdvisor
* Created different kinds of automated tests to align with our CI Pipeline and get rapid feedback
* Finally how we used C3 to visualise the health of our code-base
Towards FutureOps: Stable, Repeatable environments from Dev to ProdNaresh Jain
Modern human history is a story of humans inventing new tools to do more with less. "Doing more" has allowed most of us to no longer worry about producing our own food, collecting water, planning long journeys, etc. Instead, we’re able to specialize, buy what we need for less, and to some extent explore ourselves a lot more.
We're far from done, and of course humanity is far from perfect. In this talk, Mitchell Hashimoto discusses the role that automations and computers play in building a brighter future.
More details: https://confengine.com/agile-india-2017/proposal/3618/towards-futureops-stable-repeatable-environments-from-dev-to-prod
No Silver Bullets in Functional Programming by Brian McKennaNaresh Jain
We are constantly presented with trade-offs when writing software. What are the trade-offs when applying functional programming? What costs arise? When is it not worth doing? When should pragmatism kick in and when should we start using side-effects?
This talk will give you some tools to be able to answer the above questions for both functional programming and types. The tools have been refined over many professional years of both doing and not doing purely functional programming.
More details: https://confengine.com/functional-conf-2016/proposal/3137/no-silver-bullets-in-functional-programming
The document outlines the agenda for a Functional Conference taking place from October 13th to 16th. It includes pre-conference and post-conference workshops on the 13th and 16th, and the main two-day conference on the 14th and 15th. Details provided include the number of attendees from 10 countries, 23 speakers also from 10 countries, and sessions on mobile apps, birds of a feather discussions, and sponsors.
Agile India 2017 Conference is Asia's Largest and Premier Conference on Agile, Scrum, eXtreme Programming, Lean, Kanban, DevOps, Enterprise Agile, Lean Startup, Continuous Delivery, Research and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 6 - 12 March 2017 at ITC Gardenia, Bangalore. More details: http://2017.agileindia.org
This talk will explain the secret of the success of the Eclipse Platform team. The Eclipse Way is an agile software development process that we started right at the beginning when we started to develop Eclipse back in 1999. It was and is used by the Eclipse Platform team and got continuously improved over time. During the session you will hear about all our practices, like milestones, early and iterative planning, continuous integration and the endgame. I will also reveal some of the history behind the Eclipse top-level project.
More details: https://confengine.com/eclipse-summit-2016/proposal/2386/the-eclipse-way
Unleashing the Power of Automated Refactoring with JDTNaresh Jain
Refactoring is a series of small steps, each of which changes the program’s internal structure without changing its external behaviour. Refactoring, as a tool, to automate behaviour-preserving transformations to source code are not only very popular in agile development environments, but have been widely established as a cornerstone of the daily software development process, regardless of the methodology being used. Most major development environments such as Eclipse offer a set of powerful refactoring to substantially increase development productivity.
In this live demo, I’ll show
* the real value of refactoring,
* how we practice it safely,
* when and why we refactor,
* the power of refactoring tools and
* when we avoid refactoring.
I’ll be using two real-world examples of refactoring and sharing what I’ve learned about this important practice of the last 15 years.
Getting2Alpha: Turbo-charge your product with Game Thinking by Amy Jo KimNaresh Jain
Do you want to harness the deeper power of games – the power to drive long-term engagement? Are you ready to look beyond the silver bullets & Skinner boxes – and learn to think like a game designer? In this talk, you’ll learn the foundations of Game Thinking - brought to life with front-line stories from eBay, Ultima Online, The Sims, Rock Band, Covet Fashion, Happify, Lumosity and Slack. You’ll come away with a smarter approach to innovative product design - and practical, actionable design tips you can use right away to turbo-charge your path towards product/market fit.
More details: https://confengine.com/agile-india-2016/proposal/1961/getting2alpha-turbo-charge-your-product-with-game-thinking
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.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
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.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
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.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
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
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.