- The team transitioned from Scrum to a Kanban system with no iterations to address issues like lack of continuous delivery and pressure to complete all work by the end of each sprint.
- They implemented Kanban practices like limiting work in progress, just-in-time planning, and decoupling demos from sprints. This improved focus and flow of work.
- Over time, new challenges emerged as the team grew and split into two teams, and business stakeholders had different preferences around estimating work. The engagement ended as the teams refined their Kanban approach to maintenance further.
Scrum is an agile project management framework that focuses on iterative development, self-organizing teams, and frequent inspection points. The key aspects of Scrum include roles like the product owner, Scrum master, and self-organizing development team. Events in Scrum include sprint planning meetings, daily stand-ups, sprint reviews, and retrospectives. Artifacts include the product backlog, sprint backlog, and definition of done. Scrum aims to deliver working software frequently through short iterations called sprints.
This document provides an introduction to agile requirements and user stories. It discusses key concepts such as the agile manifesto, user roles, personas, and developing user stories using the INVEST criteria. The document also covers acceptance tests and how they are used to determine if a user story is complete. It emphasizes that agile requirements focus on interaction, conversation, and confirmation rather than documentation.
This document provides an introduction to agile principles and Scrum methodology. It defines key Scrum roles like Product Owner and Scrum Master. It also explains common Scrum ceremonies such as sprint planning, daily stand-ups, sprint reviews and retrospectives. Artifacts like the product backlog, sprint backlog and burn down charts are also described. The document aims to give trainees an overview of agile and Scrum concepts to help them apply these principles.
This document provides an overview of Agile and Scrum concepts. It discusses the Shu-Ha-Ri learning model, which involves first following rules, then bending rules, and finally intuitively knowing what is right. It also covers topics like sprint backlogs, delegation levels, user stories, and the Agile manifesto principles. The goal is to help trainees understand and apply Agile frameworks.
This document provides an overview of a Scrum project that will have 2 releases over 5 sprints. It outlines the product and sprint backlogs, planning meetings, and retrospectives that will take place during each sprint. The document also introduces expectations for participants to share information about themselves and their goals for the course. Finally, it presents an initial product backlog that will be developed over the sprints, including topics like Agile philosophy, user stories, acceptance tests, and more.
Scrum kan vara svårt att använda i stor skala. Vi tittar på hur Kanban kan användas för att förstärka Scrum på företagsnivå genom att förbättra Scrum-of-Scrums, hjälpa produktägaren och stödja god beslutsfattandet på program eller avdelningsnivå.
Talare är Christophe Achouiantz från Avega Group
Scrum is a framework for developing new products that allows teams to create their own lightweight process. It emphasizes empiricism, self-organization, collaboration, prioritization, and rhythm. Scrum works best for complex problems like new product development and knowledge work. Teams of 3-7 people work in short cycles called sprints to deliver working software. They plan, execute, and reflect at the end of each sprint to continuously improve.
Scrum is an agile project management framework that focuses on iterative development, self-organizing teams, and frequent inspection points. The key aspects of Scrum include roles like the product owner, Scrum master, and self-organizing development team. Events in Scrum include sprint planning meetings, daily stand-ups, sprint reviews, and retrospectives. Artifacts include the product backlog, sprint backlog, and definition of done. Scrum aims to deliver working software frequently through short iterations called sprints.
This document provides an introduction to agile requirements and user stories. It discusses key concepts such as the agile manifesto, user roles, personas, and developing user stories using the INVEST criteria. The document also covers acceptance tests and how they are used to determine if a user story is complete. It emphasizes that agile requirements focus on interaction, conversation, and confirmation rather than documentation.
This document provides an introduction to agile principles and Scrum methodology. It defines key Scrum roles like Product Owner and Scrum Master. It also explains common Scrum ceremonies such as sprint planning, daily stand-ups, sprint reviews and retrospectives. Artifacts like the product backlog, sprint backlog and burn down charts are also described. The document aims to give trainees an overview of agile and Scrum concepts to help them apply these principles.
This document provides an overview of Agile and Scrum concepts. It discusses the Shu-Ha-Ri learning model, which involves first following rules, then bending rules, and finally intuitively knowing what is right. It also covers topics like sprint backlogs, delegation levels, user stories, and the Agile manifesto principles. The goal is to help trainees understand and apply Agile frameworks.
This document provides an overview of a Scrum project that will have 2 releases over 5 sprints. It outlines the product and sprint backlogs, planning meetings, and retrospectives that will take place during each sprint. The document also introduces expectations for participants to share information about themselves and their goals for the course. Finally, it presents an initial product backlog that will be developed over the sprints, including topics like Agile philosophy, user stories, acceptance tests, and more.
Scrum kan vara svårt att använda i stor skala. Vi tittar på hur Kanban kan användas för att förstärka Scrum på företagsnivå genom att förbättra Scrum-of-Scrums, hjälpa produktägaren och stödja god beslutsfattandet på program eller avdelningsnivå.
Talare är Christophe Achouiantz från Avega Group
Scrum is a framework for developing new products that allows teams to create their own lightweight process. It emphasizes empiricism, self-organization, collaboration, prioritization, and rhythm. Scrum works best for complex problems like new product development and knowledge work. Teams of 3-7 people work in short cycles called sprints to deliver working software. They plan, execute, and reflect at the end of each sprint to continuously improve.
This document discusses why DBAs should care about Scrum. It provides an overview of Scrum, describing it as an agile framework that utilizes self-directed cross-functional teams, short sprints, and transparency. It notes that Scrum can help reveal issues in an organization and improve outcomes compared to traditional sequential development approaches. The document encourages DBAs to stay up-to-date on new methodologies like Scrum in order to provide more value and help teams be more successful.
This document discusses how requirements are handled in Scrum projects using user stories. It explains that in Scrum, requirements are handled through ongoing conversations between stakeholders and the development team, rather than being fully defined upfront in documentation. User stories are used as placeholders to represent requirements at varying levels of detail and promote these conversations. The document outlines best practices for writing effective user stories using the "INVEST" criteria of being Independent, Negotiable, Valuable, Estimatable, Small, and Testable.
The document provides an overview of Scrum, an Agile framework. It discusses the Scrum values, roles, practices, and artifacts. The Product Owner prioritizes goals and maintains the product backlog. The Scrum Master facilitates the process and removes impediments. The cross-functional team is self-organizing. Key practices include sprint planning, daily stand-ups, sprint reviews, and retrospectives. Customers benefit from early feedback and faster delivery. Leaders gain better engagement and accountability. Team members enjoy a sustainable pace and satisfaction from delivering quality products. Learning Scrum is best done by applying practices and experiencing the process firsthand.
This document provides an overview of managing iterative software development using Scrum. It discusses how Scrum and iterative development can help reduce software project failure rates, bugs, and improve usability through closer customer interaction. Key aspects of Scrum covered include roles, artifacts like product and sprint backlogs and burn down charts, and how daily stand-up meetings work. The document also discusses how the author has adopted aspects of Scrum to manage projects while maintaining traditional project management artifacts to satisfy management.
This document discusses building high performing agile teams. It provides tips on embracing continuous improvement, managing backlogs and task boards, conducting effective story kickoffs, addressing defects early, embracing test-driven development, and constantly seeking to improve processes through lean principles. The presentation was given by Naveed Khawaja and Carl Bruiners and provides advice based on their experience helping organizations adopt agile practices.
Let's talk about Agile not because it is popular, new and amazing, but because it is a software development methodology that just works. What are the basics of Agile? How does it work? What issues you may face while adopting Agile?
The document discusses Scrum practices at Nucleus, a company following Agile principles. It describes how Nucleus uses Scrum ceremonies like daily standups and sprints. It notes the benefits of using tools to support continuous integration, tracking metrics, and managing backlogs and defects. However, it also discusses potential risks if quality practices like testing are not properly implemented. The presentation aims to showcase Nucleus' Agile practices and tools while also highlighting areas that require attention to fully achieve Agile principles.
Zend provides expert PHP delivery through best practices for development, deployment, and management. It helps improve developer productivity with tools like Zend Studio, trains developers, and ensures quality and speed through a consistent PHP stack. Zend also helps optimize performance, enable faster releases, and reduce problem resolution times.
SXSW 2013: Get Agile! Scrum for UX, Design & DevelopmentFabrique
This document discusses strategies for implementing agile Scrum practices in an agency setting. Some key points include using a "Super Sprint 0" for extensive planning before starting sprints. It also recommends fully integrating different disciplines like design and development into single teams to build products together in each sprint. Specific tips provided include customizing story templates to specify which disciplines are involved, allowing flexibility in quality standards, and using physical artifacts in shared team spaces to facilitate collaboration. Challenges of varying team composition and availability are addressed, as are roles like the Scrum Master and Product Owner.
This document summarizes a sprint process used by the Drupal Gardens engineering team at Acquia. It discusses their scrum process which includes planning, daily stand-ups, demos at the end of each sprint, and retrospectives. It outlines their definition of done and challenges including balancing perfectionism vs releasing and breaking down large features into smaller stories. Their goal is to deliver high business value as quickly as possible using agile values and processes.
This document provides an agenda for a training on Agile methodology. It begins with defining Agile and discussing the Agile Manifesto and principles. It then covers various Agile frameworks like Scrum and Extreme Programming (XP). It discusses Agile practices used across different industries like Lean, Kaizen, and Kanban. Finally, it discusses Agile groups, quality standards, strategy approaches, and standardization as they relate to Agile. The document provides a comprehensive overview of Agile concepts, frameworks, and industry applications.
Agile Anti-Patterns. Yes your agile projects can and will fail too.Sander Hoogendoorn
The document discusses various anti-patterns that can cause agile projects to fail. It notes that while many believe waterfall methods don't work, agile projects can fail too if not implemented properly. Some specific anti-patterns mentioned include blaming the methodology instead of the implementation, overreliance on documentation or rituals over outcomes, and treating agile as a one-size-fits-all approach. The document advocates for tailoring agile approaches to individual project and organization needs.
This document discusses how traditional project management approaches can fall short for complex work, and introduces Agile product development using Scrum as a framework. It explains that Scrum focuses on maximizing business value through collaborative customer engagement and empirical process improvement over comprehensive planning. Scrum is presented as a practical method for complex work where needs may change, using short development cycles called sprints to iteratively deliver working software or products.
A retrospective is a meeting where a team reflects on a past period of work to learn lessons and apply them to future projects. Without retrospectives, teams repeat the same mistakes. Effective retrospectives have preparation and follow-up. They balance conversation, agree on a focus area, and create action plans with owners and visibility. Retrospectives bridge sprints and support continuous improvement through experimentation.
In recent years, Fabrique has executed several large projects in an Agile way. Each time the methods, tools and techniques were used in a different way. I shared our war stories with the Amsterdam UX community at the Fabrique-hosted UX Cocktail Hour Amsterdam of october 15, 2009. The talk was well received and we got some great discussion out of it. Please contact me for any questions.
Pair Programming, TDD and other impractical thingsMarcello Duarte
"Why should we write our tests first? Isn't that going to slow my development?" "What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!" "Look, in the perfect world your advises are great, but I have a project to finish here." In this talk Marcello explores efficiency in contrast to effectiveness. He looks into how practices, traditionally accepted as efficient, sometimes turn out to be less effective than a few "impractical" things he has come across.
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also discusses the product and sprint backlogs and how teams work in sprints to deliver working software increments every 2-4 weeks using the Scrum framework.
This document provides an overview of the basics of Scrum, an agile project management framework. It defines key Scrum concepts like roles, activities, artifacts and processes. The document outlines that Scrum is a simple, flexible approach to managing complex projects that focuses on clarity, inspection and adaptation through short iterations and daily stand-ups. It emphasizes delivering working software frequently in sprints and adapting the backlog based on feedback.
Introduction to Agile for Digital StakeholdersMai Quay
The document provides an introduction to agile methodology. It discusses some of the key principles of agile, including welcoming change, reducing risk, and delivering value incrementally. It also compares agile to traditional waterfall methodology, noting that agile works through constant replanning and slicing work into small achievable pieces. The document suggests taking a pragmatic approach to planning by only planning for the immediate future and making decisions based on current information.
A lightning talk I gave at the South African Scrum Gathering on 14 Sep 2011 (#SGZA) in Cape Town. It examines why sprint reviews are so often awful and how we need to follow some of the rules of a retrospective if we are to achieve value from the review process
This document discusses why DBAs should care about Scrum. It provides an overview of Scrum, describing it as an agile framework that utilizes self-directed cross-functional teams, short sprints, and transparency. It notes that Scrum can help reveal issues in an organization and improve outcomes compared to traditional sequential development approaches. The document encourages DBAs to stay up-to-date on new methodologies like Scrum in order to provide more value and help teams be more successful.
This document discusses how requirements are handled in Scrum projects using user stories. It explains that in Scrum, requirements are handled through ongoing conversations between stakeholders and the development team, rather than being fully defined upfront in documentation. User stories are used as placeholders to represent requirements at varying levels of detail and promote these conversations. The document outlines best practices for writing effective user stories using the "INVEST" criteria of being Independent, Negotiable, Valuable, Estimatable, Small, and Testable.
The document provides an overview of Scrum, an Agile framework. It discusses the Scrum values, roles, practices, and artifacts. The Product Owner prioritizes goals and maintains the product backlog. The Scrum Master facilitates the process and removes impediments. The cross-functional team is self-organizing. Key practices include sprint planning, daily stand-ups, sprint reviews, and retrospectives. Customers benefit from early feedback and faster delivery. Leaders gain better engagement and accountability. Team members enjoy a sustainable pace and satisfaction from delivering quality products. Learning Scrum is best done by applying practices and experiencing the process firsthand.
This document provides an overview of managing iterative software development using Scrum. It discusses how Scrum and iterative development can help reduce software project failure rates, bugs, and improve usability through closer customer interaction. Key aspects of Scrum covered include roles, artifacts like product and sprint backlogs and burn down charts, and how daily stand-up meetings work. The document also discusses how the author has adopted aspects of Scrum to manage projects while maintaining traditional project management artifacts to satisfy management.
This document discusses building high performing agile teams. It provides tips on embracing continuous improvement, managing backlogs and task boards, conducting effective story kickoffs, addressing defects early, embracing test-driven development, and constantly seeking to improve processes through lean principles. The presentation was given by Naveed Khawaja and Carl Bruiners and provides advice based on their experience helping organizations adopt agile practices.
Let's talk about Agile not because it is popular, new and amazing, but because it is a software development methodology that just works. What are the basics of Agile? How does it work? What issues you may face while adopting Agile?
The document discusses Scrum practices at Nucleus, a company following Agile principles. It describes how Nucleus uses Scrum ceremonies like daily standups and sprints. It notes the benefits of using tools to support continuous integration, tracking metrics, and managing backlogs and defects. However, it also discusses potential risks if quality practices like testing are not properly implemented. The presentation aims to showcase Nucleus' Agile practices and tools while also highlighting areas that require attention to fully achieve Agile principles.
Zend provides expert PHP delivery through best practices for development, deployment, and management. It helps improve developer productivity with tools like Zend Studio, trains developers, and ensures quality and speed through a consistent PHP stack. Zend also helps optimize performance, enable faster releases, and reduce problem resolution times.
SXSW 2013: Get Agile! Scrum for UX, Design & DevelopmentFabrique
This document discusses strategies for implementing agile Scrum practices in an agency setting. Some key points include using a "Super Sprint 0" for extensive planning before starting sprints. It also recommends fully integrating different disciplines like design and development into single teams to build products together in each sprint. Specific tips provided include customizing story templates to specify which disciplines are involved, allowing flexibility in quality standards, and using physical artifacts in shared team spaces to facilitate collaboration. Challenges of varying team composition and availability are addressed, as are roles like the Scrum Master and Product Owner.
This document summarizes a sprint process used by the Drupal Gardens engineering team at Acquia. It discusses their scrum process which includes planning, daily stand-ups, demos at the end of each sprint, and retrospectives. It outlines their definition of done and challenges including balancing perfectionism vs releasing and breaking down large features into smaller stories. Their goal is to deliver high business value as quickly as possible using agile values and processes.
This document provides an agenda for a training on Agile methodology. It begins with defining Agile and discussing the Agile Manifesto and principles. It then covers various Agile frameworks like Scrum and Extreme Programming (XP). It discusses Agile practices used across different industries like Lean, Kaizen, and Kanban. Finally, it discusses Agile groups, quality standards, strategy approaches, and standardization as they relate to Agile. The document provides a comprehensive overview of Agile concepts, frameworks, and industry applications.
Agile Anti-Patterns. Yes your agile projects can and will fail too.Sander Hoogendoorn
The document discusses various anti-patterns that can cause agile projects to fail. It notes that while many believe waterfall methods don't work, agile projects can fail too if not implemented properly. Some specific anti-patterns mentioned include blaming the methodology instead of the implementation, overreliance on documentation or rituals over outcomes, and treating agile as a one-size-fits-all approach. The document advocates for tailoring agile approaches to individual project and organization needs.
This document discusses how traditional project management approaches can fall short for complex work, and introduces Agile product development using Scrum as a framework. It explains that Scrum focuses on maximizing business value through collaborative customer engagement and empirical process improvement over comprehensive planning. Scrum is presented as a practical method for complex work where needs may change, using short development cycles called sprints to iteratively deliver working software or products.
A retrospective is a meeting where a team reflects on a past period of work to learn lessons and apply them to future projects. Without retrospectives, teams repeat the same mistakes. Effective retrospectives have preparation and follow-up. They balance conversation, agree on a focus area, and create action plans with owners and visibility. Retrospectives bridge sprints and support continuous improvement through experimentation.
In recent years, Fabrique has executed several large projects in an Agile way. Each time the methods, tools and techniques were used in a different way. I shared our war stories with the Amsterdam UX community at the Fabrique-hosted UX Cocktail Hour Amsterdam of october 15, 2009. The talk was well received and we got some great discussion out of it. Please contact me for any questions.
Pair Programming, TDD and other impractical thingsMarcello Duarte
"Why should we write our tests first? Isn't that going to slow my development?" "What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!" "Look, in the perfect world your advises are great, but I have a project to finish here." In this talk Marcello explores efficiency in contrast to effectiveness. He looks into how practices, traditionally accepted as efficient, sometimes turn out to be less effective than a few "impractical" things he has come across.
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also discusses the product and sprint backlogs and how teams work in sprints to deliver working software increments every 2-4 weeks using the Scrum framework.
This document provides an overview of the basics of Scrum, an agile project management framework. It defines key Scrum concepts like roles, activities, artifacts and processes. The document outlines that Scrum is a simple, flexible approach to managing complex projects that focuses on clarity, inspection and adaptation through short iterations and daily stand-ups. It emphasizes delivering working software frequently in sprints and adapting the backlog based on feedback.
Introduction to Agile for Digital StakeholdersMai Quay
The document provides an introduction to agile methodology. It discusses some of the key principles of agile, including welcoming change, reducing risk, and delivering value incrementally. It also compares agile to traditional waterfall methodology, noting that agile works through constant replanning and slicing work into small achievable pieces. The document suggests taking a pragmatic approach to planning by only planning for the immediate future and making decisions based on current information.
A lightning talk I gave at the South African Scrum Gathering on 14 Sep 2011 (#SGZA) in Cape Town. It examines why sprint reviews are so often awful and how we need to follow some of the rules of a retrospective if we are to achieve value from the review process
There are several ways that current development processes can miserably fail users and the business when trying to launch your project on multiple platforms. Massive changes, blame, or simply not understanding your missed opportunities, are the usual results.
The answer is not any of these, and certainly not to try to impose a new process. Instead, encompass all the existing processes to create a new philosophy of implementation. Avoid pitfalls and gaps, and play to the strengths of your team to operationalize a functional design and development processes.
Steven will talk about methods he's devised and used with business, analysts, and developers that make everyone happy and help assure projects actually launch.
Presented at D2WC in Kansas City on 17 March 2012
The document discusses key principles of Scrum, including valuing individuals and interactions over processes, working software over documentation, and responding to change over following a plan. It describes Scrum goals of delivering working software frequently through iterations, favoring customer collaboration, and responding to changing requirements. Scrum uses self-organizing cross-functional teams, daily stand-ups, sprints, and retrospectives to deliver working increments iteratively.
Transitioning to Scrum is not easy, and for many, distributed teams are the most difficult to manage. In trying to make Scrum work with a geographically dispersed team, increasing efficiency requires adjustments to processes and effective communication and collaboration.
This webinar will provide guidance for proper planning and managing, in order to get your distributed teams working smoothly throughout the scrum processes. Dr. Kevin Thompson, cPrime’s Agile Practice Lead, will address key issues such as:
• How to have scrum meetings for distributed teams (daily scrum, sprint planning, sprint review, retrospective)
• How to cope with time-zone differences
• How to cope with language differences
• Best practices for collaborating in a distributed team
• Best practices for tools that mitigate distributed team impact
Overview of agile values
This presentation shows some core concepts that make agile software development different.
This will help your team familiar with agile concepts and start boosting your team performance.
Take advantage of new trends in agile: Iterationless Kanban and Continuous De...Atlassian
The document discusses how Dachis Group has successfully integrated Lean Startup and Lean Development methodologies. There were three key areas of focus: building the product backlog by modeling features, epics, and stories in JIRA; structuring the Kanban flow using tools like GreenHopper and custom plugins; and implementing continuous deployment using tools like Chef, Jenkins, and custom code for automated deployments. The presentation provides examples of how Dachis Group implemented these practices for their large-scale, globally distributed teams. It recommends background reading on Lean Startup, Customer Development, Kanban, and Continuous Delivery and offers contact details for further discussion.
Back to the Drawing Board, Again and Again and AgainKevin Schumacher
This document discusses improving the UX design process by adopting agile principles. It recommends designers work directly with development teams during sprints to address edge cases as they emerge, rather than fully designing prototypes before development begins. This embedded approach builds trust between teams and allows designs to evolve incrementally in response to new information. The key is for all team members, including UX practitioners, to have a servant leadership mindset focused on collaboratively solving problems rather than individual agendas.
This presentation was used in "Agile workshop for FPT Aptech Hanoi students" in December 2012.
This doc covers most of core practices of an agile developer.
This is a presentation I put together for a conference in 2011. It gives a fast, high level view of where Agile Software Development came from, its core values and principles, and its core practices. It is structured as 7 PechaKucha decks in a row, with short breaks in between, which requires high energy, intensity, and a sense of humor. :)
This master's thesis summarizes the author Tatjana Pavlenko's research on applying agile methodologies like Scrum to software design and programming. Over 4 cycles from December 2011 to April 2012, Pavlenko worked with Company Sigma, a software development team of 8 members creating iOS apps, to design an effective Scrum approach for their distributed team. Initial obstacles included the team not being self-organized and the designer being left out of Scrum practices. Through improvements like online collaboration tools, prototypes, and special Scrum methods for the designer, the final results showed a more self-organized team with the designer more involved in Scrum. The conclusion is that not forcing teams to strictly use Scrum but adapting practices to
The document provides an overview of agile software development practices compared to traditional waterfall approaches. It summarizes the author's experience transitioning from waterfall to agile development and embracing eXtreme Programming (XP) practices like test-driven development, pair programming, and continuous integration. The author then integrated XP with Scrum, the most popular agile framework. The document compares different agile methodologies and emphasizes that agile is about values and principles over prescriptive rules.
This document discusses Agile development principles and practices. It compares Scrum and Kanban methodologies. Scrum uses fixed-time sprints while Kanban uses a continuous flow approach. Both aim to deliver working software frequently and respond quickly to changes. Estimation techniques like story points and velocity help plan work. Daily stand-ups, retrospectives and product reviews provide transparency and feedback. While roles may differ, Agile requires collaboration between teams, products owners and managers to deliver value.
1. The presentation discussed using free and open source software (FOSS) for agile software development. FOSS platforms, languages, and tools can be used throughout the entire software development lifecycle.
2. Agile software development and FOSS share principles like releasing early and often, listening to customers, extensive testing, and simple designs. FOSS allows for built-in integration, quality, community collaboration, and bug/feature tracking.
3. The presenter encouraged the audience to join their local agile development community to participate in monthly talks, training courses, and discussion groups to learn more about using agile and open source methods for software projects.
SFD2012Hanoi - Duong Trong Tan - Agile and FOSS Vu Hung Nguyen
1. The presentation discussed using free and open source software (FOSS) and agile software development (ASD) approaches to improve software development.
2. FOSS and ASD share principles like releasing early and often, listening to customers, extensive testing, and keeping development teams motivated.
3. FOSS can be used as the development platform, for programming languages, and as tools to support all phases of the software development lifecycle in agile projects.
This document provides an overview of Agile project management methods. It defines Agile as emphasizing small, collaborative teams delivering frequent, incremental releases prioritized for customer need. Key aspects of Agile include iterative development, evolving requirements, and short release cycles. The document contrasts Agile with traditional plan-driven methods and notes Agile is best for uncertain, dynamic requirements while plan-driven is better for safety-critical projects. It describes common Agile methodologies and the core Agile project lifecycle of emergent, iterative processes delivering value in regular increments.
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.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
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.
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!
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.
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
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.
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
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 .
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!
2. Joakim Sundén
• Agile/Lean/Kanban Coach at Avega Group
• Developer background
• David J. Andersons personal
recommendation and endorsement as
“knowledgeable Kanban coach”
• http://www.joakimsunden.com/
2
6. We need longer
sprints...
Slack between
sprint demo and
sprint planning
6
Too much time disappears when everything stops for a day or two and then starts again.
Pressure to deliver to review/demo.
7. More note-
taking during Sprint
planning
No time to
discuss stories and
requirements
7
Developers don’t remember requirements discussed in beginning of sprint.
Pressure to deliver and not immediately available Product Owner and analyst in mid-sprint.
8. Continuous
delivery, deliver part of
stories
Finish stories before
moving on to new ones
We have to get
better at working together
on user stories
8
Working on too many stories at the same time, not delivering to test and review machine until
late in sprint.
9. How do we demo
integrations stories?
I thought that was
going to be fixed in the
‘next sprint’
9
Sometimes the stories in a sprint aren’t that interesting to busy off-site stakeholders.
Incremental delivery of features broken down to small stories makes stakeholders pay less
attention to problems (“probably delivered in the next sprint”).
11. http://leansoftwareengineering.com/
11
Read some of Corey Ladas blog posts.
There was talk about “no iterations” at an Agile Sweden conference, but no connection to
Kanban.
12. The Kanban Expert
...and David J.
Anderson
12
No close acquaintance with David J. Anderson and his work with Kanban as a method yet -
that was to come later.
14. We need longer
sprints...
Just-in-Time planning!
Slack between
sprint demo and
sprint planning
Limit work to
capacity!
14
Plan stories when needed. Eliminated negative slack and “stop & go”.
Work was pulled and limited to capacity rather than pushed. Pressure to deliver would not go
away easily though...
15. More note-
taking during Sprint
planning
Just-in-Time planning!
No time to
discuss stories and
requirements
15
Just-in-Time planning also helped keep the discussion between developers and Product
Owner and analysts fresh and on-going.
16. Continuous
delivery, deliver part of
stories
Limit work in
progress!
Finish stories before
moving on to new ones
Planning work,
We have to get Story Captain!
better at working together
on user stories
16
WIP limits formally prescribed cooperation when working with stories.
Story Captain was responsible for planning work on the story so that it was easy for others to
help finish the story when they had capacity.
17. How do we demo
integrations stories?
Decouple demo/
review from sprint!
I thought that was
going to be fixed in the
‘next sprint’
17
Review/demo only when it made sense to Product Owner and stakeholders. Typically about
every 3 to 5 weeks.
18. 18
Backlog-Development-Test-Fix. Ongoing-Ready.
Team added “Prepare” and “Good-to-go” later.
Started with with limit of 2 stories for development (made physical on board). 7-8 developer
found this a bit hard at times, increased to 3 after a few weeks. WIP limit increased further
and dropped completely when new developers joined team, ScrumMaster role became unclear
and there was a lot of pressure to deliver the first big release.
20. 20
Story in development broken down to tasks. WIP limit on tasks indicated, but not 100%
enforced, by cat and dog avatars.
Warning signs in yellow (risk of not delivering in estimated time) and red (won’t deliver in
time).
21. 21
Legend for avatars. Later changed to more immediately recognizable Southpark avatars.
22. New Scrum Board
worked well
More obvious what
people are working with
Our work was
focused and goal-oriented
Limiting parallel
work to two stories was
good
22
The result? Team was happy with changes. Soon “release chaos” ensued and discipline with
process disappeared as team focused a lot on delivering in time.
27. 27
Team split in two. [Animation of cell splitting into two cells]
28. We don’t
understand story
points T-shirt sizes and
lead times!
Smaller stories!
Bigger stories!
MMFs and stories!
28
Business side did not understand story points and wanted to communicate in days and hours.
Team settled on t-shirt sizes and date stamps on story for the different steps in the workflow
in order to calculate lead time.
Developers wanted small stories, business wanted features. Separate ideation board for
Product Owner and analyst with something similar to MMFs was proposed. Broken down into
stories in a dev step. Teams Kanban boards to be seen as expansions of this step.
29. 29
At this time my engagement with the client came to an end.
30. 30
Board for one of the teams at the start of next phase just before I left. Removed “fix” column
and let defects go into dev queue instead. Happy stories (rightmost col), technical stories that
makes devs happier when solved, to work with when idle increases understanding of less
capacity utilization when limiting WIP.
31. How can
maintenance be part
of the team?
Classes of Service!
How can Product Owner
and Requirements Analyst
work with two teams and
Kanban? Ideation board,
shared backlog!
31
Plans for the future...
Scrum team with 6-7 developers, 2 testers, 1 architect, 1 requirements analyst and 1 ScrumMaster.
Three weeks sprints.
Retrospectives. Inspect and adapt.
Too much time disappears when everything stops for a day or two and then starts again.
Pressure to deliver to review/demo.
Too much time disappears when everything stops for a day or two and then starts again.
Pressure to deliver to review/demo.
Developers don’t remember requirements discussed in beginning of sprint.
Pressure to deliver and not immediately available Product Owner and analyst in mid-sprint.
Developers don’t remember requirements discussed in beginning of sprint.
Pressure to deliver and not immediately available Product Owner and analyst in mid-sprint.
Working on too many stories at the same time, not delivering to test and review machine until late in sprint.
Working on too many stories at the same time, not delivering to test and review machine until late in sprint.
Working on too many stories at the same time, not delivering to test and review machine until late in sprint.
Sometimes the stories in a sprint aren’t that interesting to busy off-site stakeholders.
Incremental delivery of features broken down to small stories makes stakeholders pay less attention to problems (“probably delivered in the next sprint”).
Sometimes the stories in a sprint aren’t that interesting to busy off-site stakeholders.
Incremental delivery of features broken down to small stories makes stakeholders pay less attention to problems (“probably delivered in the next sprint”).
Already lean ingredients and philosophy in team.
Read some of Corey Ladas blog posts.
There was talk about “no iterations” at an Agile Sweden conference, but no connection to Kanban.
No close acquaintance with David J. Anderson and his work with Kanban as a method yet - that was to come later.
We simply called our approach “Flow”. One of the principles of lean.
Plan stories when needed. Eliminated negative slack and “stop & go”.
Work was pulled and limited to capacity rather than pushed. Pressure to deliver would not go away easily though...
Plan stories when needed. Eliminated negative slack and “stop & go”.
Work was pulled and limited to capacity rather than pushed. Pressure to deliver would not go away easily though...
Just-in-Time planning also helped keep the discussion between developers and Product Owner and analysts fresh and on-going.
WIP limits formally prescribed cooperation when working with stories.
Story Captain was responsible for planning work on the story so that it was easy for others to help finish the story when they had capacity.
WIP limits formally prescribed cooperation when working with stories.
Story Captain was responsible for planning work on the story so that it was easy for others to help finish the story when they had capacity.
Review/demo only when it made sense to Product Owner and stakeholders. Typically about every 3 to 5 weeks.
Backlog-Development-Test-Fix. Ongoing-Ready.
Team added “Prepare” and “Good-to-go” later.
Started with with limit of 2 stories for development (made physical on board). 7-8 developer found this a bit hard at times, increased to 3 after a few weeks. WIP limit increased further and dropped completely when new developers joined team, ScrumMaster role became unclear and there was a lot of pressure to deliver the first big release.
Backlog-Development-Test-Fix. Ongoing-Ready.
Team added “Prepare” and “Good-to-go” later.
Started with with limit of 2 stories for development (made physical on board). 7-8 developer found this a bit hard at times, increased to 3 after a few weeks. WIP limit increased further and dropped completely when new developers joined team, ScrumMaster role became unclear and there was a lot of pressure to deliver the first big release.
Real board.
Story in development broken down to tasks. WIP limit on tasks indicated, but not 100% enforced, by cat and dog avatars.
Warning signs in yellow (risk of not delivering in estimated time) and red (won’t deliver in time).
Legend for avatars. Later changed to more immediately recognizable Southpark avatars.
The result? Team was happy with changes. Soon “release chaos” ensued and discipline with process disappeared as team focused a lot on delivering in time.
The result? Team was happy with changes. Soon “release chaos” ensued and discipline with process disappeared as team focused a lot on delivering in time.
The result? Team was happy with changes. Soon “release chaos” ensued and discipline with process disappeared as team focused a lot on delivering in time.
The result? Team was happy with changes. Soon “release chaos” ensued and discipline with process disappeared as team focused a lot on delivering in time.
Release! Paying off technical debt “outside of process” in post release hiatus.
New challenges.
Maintenance of production system.
New team members.
Team split in two. [Animation of cell splitting into two cells]
Business side did not understand story points and wanted to communicate in days and hours. Team settled on t-shirt sizes and date stamps on story for the different steps in the workflow in order to calculate lead time.
Developers wanted small stories, business wanted features. Separate ideation board for Product Owner and analyst with something similar to MMFs was proposed. Broken down into stories in a dev step. Teams Kanban boards to be seen as expansions of this step.
Business side did not understand story points and wanted to communicate in days and hours. Team settled on t-shirt sizes and date stamps on story for the different steps in the workflow in order to calculate lead time.
Developers wanted small stories, business wanted features. Separate ideation board for Product Owner and analyst with something similar to MMFs was proposed. Broken down into stories in a dev step. Teams Kanban boards to be seen as expansions of this step.
Business side did not understand story points and wanted to communicate in days and hours. Team settled on t-shirt sizes and date stamps on story for the different steps in the workflow in order to calculate lead time.
Developers wanted small stories, business wanted features. Separate ideation board for Product Owner and analyst with something similar to MMFs was proposed. Broken down into stories in a dev step. Teams Kanban boards to be seen as expansions of this step.
Business side did not understand story points and wanted to communicate in days and hours. Team settled on t-shirt sizes and date stamps on story for the different steps in the workflow in order to calculate lead time.
Developers wanted small stories, business wanted features. Separate ideation board for Product Owner and analyst with something similar to MMFs was proposed. Broken down into stories in a dev step. Teams Kanban boards to be seen as expansions of this step.
Business side did not understand story points and wanted to communicate in days and hours. Team settled on t-shirt sizes and date stamps on story for the different steps in the workflow in order to calculate lead time.
Developers wanted small stories, business wanted features. Separate ideation board for Product Owner and analyst with something similar to MMFs was proposed. Broken down into stories in a dev step. Teams Kanban boards to be seen as expansions of this step.
At this time my engagement with the client came to an end.
Board for one of the teams at the start of next phase just before I left. Removed “fix” column and let defects go into dev queue instead. Happy stories (rightmost col), technical stories that makes devs happier when solved, to work with when idle increases understanding of less capacity utilization when limiting WIP.
Plans for the future...
Plans for the future...
Plans for the future...
Plans for the future...
Questions? E-mail joakim dot sunden at avega dot se. http://www.joakimsunden.com/