Agile xp crash_course_2010_05_21
•Download as KEY, PDF•
0 likes•665 views
This document provides an overview of Agile and eXtreme Programming (XP), including the core values and principles of the Agile Manifesto, roles and practices in XP, and how to adopt and apply XP to projects. It discusses key aspects of XP like short iterations, user stories, frequent releases, test-driven development, refactoring, collective code ownership, and more. The goal is to give the reader a crash course in Agile and XP methodologies.
Report
Share
Report
Share
Recommended
An Introduction to XP and Agile
This document provides an introduction to eXtreme Programming (XP) and agile software development methods. It discusses some common problems with traditional software development approaches such as taking too long, costing too much, and requiring too many people. XP and agile aim to address these problems through principles like rapid delivery of working software in short iterations, frequent feedback, simplicity, respect, and flexibility. The document outlines XP practices like user stories, pair programming, test-driven development, and daily standups that embody these principles. It concludes by noting that agile methods have evolved over decades to become more effective approaches to software development.
Teamleader testcon 2019
Testers, do you find yourself still siloed even after breaking down the “walls” between development and testing? Are you in a hole of never-ending test creation and maintenance, removing you from focusing on user experience? Does ad-hoc exploratory testing still happen because your tests aren’t stable enough to test the app before it gets to production?
When your team starts to adopt agile and DevOps development practices, how do you scale testing to keep up with higher release frequencies? Test automation is a big part of the solution. But beware that you’re doing it the wrong way.
In this talk I will explain how to reverse the negative impacts brought about from common – but not necessarily “good” – practices around automation tooling and QA hiring practices. I will talk about what changes you need to make to win back more time to develop and implement your test strategy. I will elevate your testing strategy from “surviving” to “thriving” in DevOps.
Pair programming demystified
Learn about problems of mature teams, about myths of pair programming and pair synergetic behaviors. How to implement pair programming in your company and how we did it in DaftCode.
Zero to tested
The document discusses strategies for improving test automation in challenging environments. It advocates for automating infrastructure provisioning using tools like Chef, Packer, Terraform and AWS to create ephemeral, automated environments. It also recommends building test code that is resilient to flakiness through techniques like retry logic, explicit waits, and logging/detecting non-determinism. The document provides a code example demonstrating how to automate infrastructure, write tests that can handle asynchronicity and other challenges, and effectively report failures to drive improvement.
Product Vs Craft
This document summarizes a talk given by Juan Delgado on the topics of product vs craft in software development. Some key points made in the document include:
- The quality and practices used in software development should be adapted based on the vision and goals of the product as well as where the product is in its lifecycle. Extreme quality may not be necessary early on.
- There is no single "right" way to build software - different approaches can both be appropriate depending on the context and needs of the product and business. Quality is contextual.
- Software teams should aim to implement "enough quality" - quality that allows for correctness and the ability to continue developing the product, but not necessarily perfect or extreme quality
The Smells Of Bad Design
The document discusses code smells that indicate issues with software design, including rigidity, fragility, immobility, viscosity, needless complexity, and opacity. It provides examples and questions to help identify when code exhibits these smells and suggests approaches to address them, such as improving reusability, reducing duplication, and employing techniques like peer review and documentation.
Scaling Agility Primer - Principles of Scaling Agility v.1
This document discusses principles of scaling agility. Scaling agility refers to applying agile principles and practices in large organizations and large teams. Some key principles for scaling agility include system thinking to optimize the whole value stream, synchronization across one product and backlog with one team, adaptive planning through frequent releases and reviews, learning across self-organizing feature teams, and transparency through information sharing. Agile is about more than just practices - the underlying values and principles are what truly enable success at large scale.
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Recommended
An Introduction to XP and Agile
This document provides an introduction to eXtreme Programming (XP) and agile software development methods. It discusses some common problems with traditional software development approaches such as taking too long, costing too much, and requiring too many people. XP and agile aim to address these problems through principles like rapid delivery of working software in short iterations, frequent feedback, simplicity, respect, and flexibility. The document outlines XP practices like user stories, pair programming, test-driven development, and daily standups that embody these principles. It concludes by noting that agile methods have evolved over decades to become more effective approaches to software development.
Teamleader testcon 2019
Testers, do you find yourself still siloed even after breaking down the “walls” between development and testing? Are you in a hole of never-ending test creation and maintenance, removing you from focusing on user experience? Does ad-hoc exploratory testing still happen because your tests aren’t stable enough to test the app before it gets to production?
When your team starts to adopt agile and DevOps development practices, how do you scale testing to keep up with higher release frequencies? Test automation is a big part of the solution. But beware that you’re doing it the wrong way.
In this talk I will explain how to reverse the negative impacts brought about from common – but not necessarily “good” – practices around automation tooling and QA hiring practices. I will talk about what changes you need to make to win back more time to develop and implement your test strategy. I will elevate your testing strategy from “surviving” to “thriving” in DevOps.
Pair programming demystified
Learn about problems of mature teams, about myths of pair programming and pair synergetic behaviors. How to implement pair programming in your company and how we did it in DaftCode.
Zero to tested
The document discusses strategies for improving test automation in challenging environments. It advocates for automating infrastructure provisioning using tools like Chef, Packer, Terraform and AWS to create ephemeral, automated environments. It also recommends building test code that is resilient to flakiness through techniques like retry logic, explicit waits, and logging/detecting non-determinism. The document provides a code example demonstrating how to automate infrastructure, write tests that can handle asynchronicity and other challenges, and effectively report failures to drive improvement.
Product Vs Craft
This document summarizes a talk given by Juan Delgado on the topics of product vs craft in software development. Some key points made in the document include:
- The quality and practices used in software development should be adapted based on the vision and goals of the product as well as where the product is in its lifecycle. Extreme quality may not be necessary early on.
- There is no single "right" way to build software - different approaches can both be appropriate depending on the context and needs of the product and business. Quality is contextual.
- Software teams should aim to implement "enough quality" - quality that allows for correctness and the ability to continue developing the product, but not necessarily perfect or extreme quality
The Smells Of Bad Design
The document discusses code smells that indicate issues with software design, including rigidity, fragility, immobility, viscosity, needless complexity, and opacity. It provides examples and questions to help identify when code exhibits these smells and suggests approaches to address them, such as improving reusability, reducing duplication, and employing techniques like peer review and documentation.
Scaling Agility Primer - Principles of Scaling Agility v.1
This document discusses principles of scaling agility. Scaling agility refers to applying agile principles and practices in large organizations and large teams. Some key principles for scaling agility include system thinking to optimize the whole value stream, synchronization across one product and backlog with one team, adaptive planning through frequent releases and reviews, learning across self-organizing feature teams, and transparency through information sharing. Agile is about more than just practices - the underlying values and principles are what truly enable success at large scale.
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Fixing Continuous Delivery For Mobile
This document discusses continuous delivery for mobile applications. It defines continuous integration, continuous delivery, and continuous deployment. It describes using tools like CircleCI for continuous integration to keep codebases clean and deployable. Continuous delivery means actually deploying deployable code, which can be challenging for mobile apps. The document then discusses how continuous deployment aligns with Agile principles and can save money. It addresses issues that can arise like long pull requests and solutions like pairing programming and automating tests. Hot pushing code changes to devices is important but existing solutions were limited so the author created Cordwood and later replaced it with using CodePush with CircleCI for per-pull request pushes.
User Stories
The document discusses planning and estimating user stories for software development. It provides guidance on writing user stories, estimating story points, determining team velocity, prioritizing stories, and planning releases using techniques like setting up buckets for "must have", "should have", and "could have" stories. The developer's responsibilities include estimating stories accurately and not giving into pressure to provide lower estimates. The customer is responsible for prioritizing stories and having visibility into risks of different priority choices.
How to be proud when you are done
Although all of us speak the same language, each of us uses different meaning of words "soon”, "fine” and "done”. That’s why for one developer "I’m done” means that just a moment ago the part of the code with implemented functionality has been successfully executed, while for another developer it means that code has been committed to repository but without checking if build is green or not on continuous integration server. At the same time "done" of developer-perfectionist means totally refactored and optimized code. And only for "black swan”-developer phrase "I'm done“ means that all tests were passed, new functionality was documented on wiki and a new feature was verified by customer on the demo server.
So if you want to decrease a risk of misunderstanding inside a team or between team and customer you should make agreement about common vision of “definition of done“ and then start using it on a daily basis. In order to prevent losing your time and stepping on the hidden rake during discussion of your done criteria we will share our knowledge about creating compact and most effective “definition of done“. We will talk about lifecycle of this document and about approaches that help you to add important items to it. We will discuss doneness on different levels (preplanning, user story and task development, sprint). And of course we won’t forget to tell you how to create “Definition of Done“ which will satisfy not only your team but your customer as well.
Why change code that works - On Technical Debt and Refactoring
The document discusses technical debt in software development. It explains that technical debt is incurred when expedient solutions are chosen that compromise quality and require extra work later. It notes the problems technical debt can cause like slow development, bugs, and employee dissatisfaction. The document recommends making technical debt visible by documenting it, analyzing and prioritizing repayments, and proactively using techniques like code reviews and automated testing to prevent new debt.
Code review
This document discusses how to improve software quality through code reviews. It begins by stating the goals of code review, such as improving code quality, sharing knowledge, and educating developers. It then discusses classification of code reviews from less to more formal. The document outlines some best practices for code reviews, including having a reviewer and author, choosing reviewers strategically, and driving the review in different ways. It provides answers to common questions about organizing effective code reviews and leaves with tips, such as tracking reviewers, using checklists, and ensuring comfortable conditions for all.
Agile development practices - How do they really work ?
Agile development practices are geared towards shorter feedback cycles and allowing teams to learn from failures. Effective practices include short daily standup meetings to communicate status, pairing programming for continuous code review and problem solving, and test-driven development which uses automated unit and acceptance tests to drive design and provide safety nets. Managing technical debt through prioritizing refactoring work and keeping stakeholders aware is also important for sustainable agile practices.
Kens Scrum Presentation
The document discusses several key aspects of Scrum:
1. Scrum is a framework based on empirical process control that was developed from lessons learned by companies like Toyota. It focuses on transparency, inspection, and adaptation.
2. Scrum provides a framework for self-organizing cross-functional teams to deliver working software frequently in short iterations with a "Done" definition.
3. Common reasons cited for Scrum failures include underlying problems in the organization already existing prior to adopting Scrum, as well as unwillingness to change engineering practices or deliver working code each iteration.
XP Injection
Nikolay Alimenkou and Aleksey Solntsev will show how to migrate from Ant project to Maven2 project and start using full power of XP engineering practices: CI, TDD, refactoring.
Why Do User Research And Usability Testing
User research and usability testing are important to remove obstacles for users and maximize benefits. Usability issues can reduce financial gains, damage a company's reputation, and lead to poor product results. While developers may think they know what users need, usability is best understood through field studies and user interviews rather than assumptions. User research should begin early in the design process to gather important insights into the interface design. Usability testing, even on a small scale, can provide valuable feedback to improve the user experience.
Agile Software Development for Non-Developers
A Crash Course Introduction into the world of Agile Software Development for people with a sparse or non-existent background in Software Development.
I held this presentation as a Brownbag session at ThoughtWorks Hamburg. The TDD part included a live coding session and the part about Continuous Integration and Continuous Delivery was backed with an example of a real Continuous Integration Server that worked on the results from the TDD live coding session.
[XP Day Vietnam 2015] XP is not windows XP
This document discusses eXtreme Programming (XP), an agile software development framework. It provides definitions and explanations of key XP practices, principles, and values. The main points are:
- XP focuses on practices like pair programming, testing, code reviews, and frequent integration that are taken "to the extreme."
- The core values of XP center on individuals, interactions, working software, customer collaboration, and responding to change.
- Key practices include sit together pairing, testing, informative workspaces, user stories, test-driven development, and more.
- Principles guide the framework and include ideas like baby steps, mutual benefit, flow, reflection, and redundancy.
Selenium as a trend
The document summarizes some key points about using Selenium for test automation:
1. Common traps to avoid include choosing Selenium solely based on trends, automating all tests without consideration for test types, and initiating automation late in the development cycle.
2. An example project story describes using Selenium with Java, Jenkins, and a page object pattern for tests of a PHP ecommerce site.
3. Issues that can arise include tests becoming difficult to maintain over time and new features breaking many existing tests. This leads to wasted effort and unhappy stakeholders.
Scrum And The Enterprise
This document discusses strategies for scaling Scrum practices within large organizations. It addresses organizing teams, integrating work across teams, managing people and skills, prioritizing work in an enterprise backlog, and delivering value through iterative development focused on the highest priority items. Key challenges include integrating work across multiple teams and layers, managing specialized skills, and ensuring continuous delivery of value at the enterprise level.
Tester vs Developer
Remind tester and developer that their ultimate goal is to maximize the value of the product and that happens only through great teamwork.
Nikolay Faletskyi - How tester can to survive in lean startup
The document discusses how testers can survive in a Lean Startup environment where their company is experimenting with the Lean Startup methodology. It suggests that testers leverage their knowledge of areas like business analysis, automation and API testing, and agile approaches. It also advises testers to familiarize themselves with documentation, prototypes, and tests that have been created. The document ends by inviting questions about Lean Startups and the tools that can be used.
Introduction to bdd
Behaviour Driven Development from the ground up. Non-technical introduction that motivates the adoption of BDD.
Best viewed as a video. Should be followed by Matt Wynne's session "BDD can save your agile"
This slide deck was orignally prepared by Steve Tooke for CukeUp AU and then modified and presented by Seb Rose to
Dave West (Tasktop Technologies) - Wizard of Oz
See more on: http://tasktop.com/resources/videos
Southern Fried Agile 2014 presentation by Dave West, Tasktop's Chief Product Officer
To listen to the audio recording of the presentation, go to: http://www.tasktop.com/resources/videos/southern-fried-agile-2014
Introduction To Extreme Programming
Extreme Programming (XP) is an agile software development methodology that focuses on rapid software development and frequent delivery of working software. It emphasizes customer collaboration, small releases, and frequent testing. Key practices of XP include writing tests first, continuous integration, pair programming, and customer involvement.
Agile Software Development Overview
This document provides an overview of agile software development. It discusses the differences between the waterfall model and agile approaches. The key principles of agile include prioritizing individuals and interactions, working software, customer collaboration, and responding to change. An example agile process used by Elsevier is described, involving roles like product owners, business analysts, developers, and quality analysts. Extreme programming is mentioned as an agile method that focuses on user stories, small releases, pair programming, unit testing, and simplicity.
xTreme Programming by Sejo Ćesić and Enis Zeherović
Introduction to eXtreme Programming (XP) with interactive and practical examples of one of its main practices: Test Driven Development (TDD).
In the first part, we will lead you through the practices of XP and make you understand why XP has been revolutionary for the software development.
After that, we will provide a more in-depth view of TDD. By sharing the best practices we will give you concrete guidelines on how to apply TDD on your projects. The session is expected to be highly interactive, you are all welcome to bring your own ideas, questions and suggestions.
Using Agile Processes on Documentum Projects
Blue Fish Founder Michael Trafton builds a case against the software development methodologies we have been using since the 80s and proposes an alternative.
Using Agile Processes on Documentum Projects
The document discusses using agile processes for Documentum projects. It provides background on the origins of agile methodologies and practices like Extreme Programming (XP). It then discusses how agile is well-suited for Documentum projects due to factors like small teams and internal projects. The document also presents a case study of how one company, Blue Fish, switched from waterfall to a hybrid agile methodology incorporating elements from RUP, XP, Scrum, and Crystal Clear. They realized benefits like higher user adoption, things getting done sooner, and improved management confidence.
More Related Content
What's hot
Fixing Continuous Delivery For Mobile
This document discusses continuous delivery for mobile applications. It defines continuous integration, continuous delivery, and continuous deployment. It describes using tools like CircleCI for continuous integration to keep codebases clean and deployable. Continuous delivery means actually deploying deployable code, which can be challenging for mobile apps. The document then discusses how continuous deployment aligns with Agile principles and can save money. It addresses issues that can arise like long pull requests and solutions like pairing programming and automating tests. Hot pushing code changes to devices is important but existing solutions were limited so the author created Cordwood and later replaced it with using CodePush with CircleCI for per-pull request pushes.
User Stories
The document discusses planning and estimating user stories for software development. It provides guidance on writing user stories, estimating story points, determining team velocity, prioritizing stories, and planning releases using techniques like setting up buckets for "must have", "should have", and "could have" stories. The developer's responsibilities include estimating stories accurately and not giving into pressure to provide lower estimates. The customer is responsible for prioritizing stories and having visibility into risks of different priority choices.
How to be proud when you are done
Although all of us speak the same language, each of us uses different meaning of words "soon”, "fine” and "done”. That’s why for one developer "I’m done” means that just a moment ago the part of the code with implemented functionality has been successfully executed, while for another developer it means that code has been committed to repository but without checking if build is green or not on continuous integration server. At the same time "done" of developer-perfectionist means totally refactored and optimized code. And only for "black swan”-developer phrase "I'm done“ means that all tests were passed, new functionality was documented on wiki and a new feature was verified by customer on the demo server.
So if you want to decrease a risk of misunderstanding inside a team or between team and customer you should make agreement about common vision of “definition of done“ and then start using it on a daily basis. In order to prevent losing your time and stepping on the hidden rake during discussion of your done criteria we will share our knowledge about creating compact and most effective “definition of done“. We will talk about lifecycle of this document and about approaches that help you to add important items to it. We will discuss doneness on different levels (preplanning, user story and task development, sprint). And of course we won’t forget to tell you how to create “Definition of Done“ which will satisfy not only your team but your customer as well.
Why change code that works - On Technical Debt and Refactoring
The document discusses technical debt in software development. It explains that technical debt is incurred when expedient solutions are chosen that compromise quality and require extra work later. It notes the problems technical debt can cause like slow development, bugs, and employee dissatisfaction. The document recommends making technical debt visible by documenting it, analyzing and prioritizing repayments, and proactively using techniques like code reviews and automated testing to prevent new debt.
Code review
This document discusses how to improve software quality through code reviews. It begins by stating the goals of code review, such as improving code quality, sharing knowledge, and educating developers. It then discusses classification of code reviews from less to more formal. The document outlines some best practices for code reviews, including having a reviewer and author, choosing reviewers strategically, and driving the review in different ways. It provides answers to common questions about organizing effective code reviews and leaves with tips, such as tracking reviewers, using checklists, and ensuring comfortable conditions for all.
Agile development practices - How do they really work ?
Agile development practices are geared towards shorter feedback cycles and allowing teams to learn from failures. Effective practices include short daily standup meetings to communicate status, pairing programming for continuous code review and problem solving, and test-driven development which uses automated unit and acceptance tests to drive design and provide safety nets. Managing technical debt through prioritizing refactoring work and keeping stakeholders aware is also important for sustainable agile practices.
Kens Scrum Presentation
The document discusses several key aspects of Scrum:
1. Scrum is a framework based on empirical process control that was developed from lessons learned by companies like Toyota. It focuses on transparency, inspection, and adaptation.
2. Scrum provides a framework for self-organizing cross-functional teams to deliver working software frequently in short iterations with a "Done" definition.
3. Common reasons cited for Scrum failures include underlying problems in the organization already existing prior to adopting Scrum, as well as unwillingness to change engineering practices or deliver working code each iteration.
XP Injection
Nikolay Alimenkou and Aleksey Solntsev will show how to migrate from Ant project to Maven2 project and start using full power of XP engineering practices: CI, TDD, refactoring.
Why Do User Research And Usability Testing
User research and usability testing are important to remove obstacles for users and maximize benefits. Usability issues can reduce financial gains, damage a company's reputation, and lead to poor product results. While developers may think they know what users need, usability is best understood through field studies and user interviews rather than assumptions. User research should begin early in the design process to gather important insights into the interface design. Usability testing, even on a small scale, can provide valuable feedback to improve the user experience.
Agile Software Development for Non-Developers
A Crash Course Introduction into the world of Agile Software Development for people with a sparse or non-existent background in Software Development.
I held this presentation as a Brownbag session at ThoughtWorks Hamburg. The TDD part included a live coding session and the part about Continuous Integration and Continuous Delivery was backed with an example of a real Continuous Integration Server that worked on the results from the TDD live coding session.
[XP Day Vietnam 2015] XP is not windows XP
This document discusses eXtreme Programming (XP), an agile software development framework. It provides definitions and explanations of key XP practices, principles, and values. The main points are:
- XP focuses on practices like pair programming, testing, code reviews, and frequent integration that are taken "to the extreme."
- The core values of XP center on individuals, interactions, working software, customer collaboration, and responding to change.
- Key practices include sit together pairing, testing, informative workspaces, user stories, test-driven development, and more.
- Principles guide the framework and include ideas like baby steps, mutual benefit, flow, reflection, and redundancy.
Selenium as a trend
The document summarizes some key points about using Selenium for test automation:
1. Common traps to avoid include choosing Selenium solely based on trends, automating all tests without consideration for test types, and initiating automation late in the development cycle.
2. An example project story describes using Selenium with Java, Jenkins, and a page object pattern for tests of a PHP ecommerce site.
3. Issues that can arise include tests becoming difficult to maintain over time and new features breaking many existing tests. This leads to wasted effort and unhappy stakeholders.
Scrum And The Enterprise
This document discusses strategies for scaling Scrum practices within large organizations. It addresses organizing teams, integrating work across teams, managing people and skills, prioritizing work in an enterprise backlog, and delivering value through iterative development focused on the highest priority items. Key challenges include integrating work across multiple teams and layers, managing specialized skills, and ensuring continuous delivery of value at the enterprise level.
Tester vs Developer
Remind tester and developer that their ultimate goal is to maximize the value of the product and that happens only through great teamwork.
Nikolay Faletskyi - How tester can to survive in lean startup
The document discusses how testers can survive in a Lean Startup environment where their company is experimenting with the Lean Startup methodology. It suggests that testers leverage their knowledge of areas like business analysis, automation and API testing, and agile approaches. It also advises testers to familiarize themselves with documentation, prototypes, and tests that have been created. The document ends by inviting questions about Lean Startups and the tools that can be used.
Introduction to bdd
Behaviour Driven Development from the ground up. Non-technical introduction that motivates the adoption of BDD.
Best viewed as a video. Should be followed by Matt Wynne's session "BDD can save your agile"
This slide deck was orignally prepared by Steve Tooke for CukeUp AU and then modified and presented by Seb Rose to
Dave West (Tasktop Technologies) - Wizard of Oz
See more on: http://tasktop.com/resources/videos
Southern Fried Agile 2014 presentation by Dave West, Tasktop's Chief Product Officer
To listen to the audio recording of the presentation, go to: http://www.tasktop.com/resources/videos/southern-fried-agile-2014
What's hot (17)
Why change code that works - On Technical Debt and Refactoring
Why change code that works - On Technical Debt and Refactoring
Agile development practices - How do they really work ?
Agile development practices - How do they really work ?
Nikolay Faletskyi - How tester can to survive in lean startup
Nikolay Faletskyi - How tester can to survive in lean startup
Similar to Agile xp crash_course_2010_05_21
Introduction To Extreme Programming
Extreme Programming (XP) is an agile software development methodology that focuses on rapid software development and frequent delivery of working software. It emphasizes customer collaboration, small releases, and frequent testing. Key practices of XP include writing tests first, continuous integration, pair programming, and customer involvement.
Agile Software Development Overview
This document provides an overview of agile software development. It discusses the differences between the waterfall model and agile approaches. The key principles of agile include prioritizing individuals and interactions, working software, customer collaboration, and responding to change. An example agile process used by Elsevier is described, involving roles like product owners, business analysts, developers, and quality analysts. Extreme programming is mentioned as an agile method that focuses on user stories, small releases, pair programming, unit testing, and simplicity.
xTreme Programming by Sejo Ćesić and Enis Zeherović
Introduction to eXtreme Programming (XP) with interactive and practical examples of one of its main practices: Test Driven Development (TDD).
In the first part, we will lead you through the practices of XP and make you understand why XP has been revolutionary for the software development.
After that, we will provide a more in-depth view of TDD. By sharing the best practices we will give you concrete guidelines on how to apply TDD on your projects. The session is expected to be highly interactive, you are all welcome to bring your own ideas, questions and suggestions.
Using Agile Processes on Documentum Projects
Blue Fish Founder Michael Trafton builds a case against the software development methodologies we have been using since the 80s and proposes an alternative.
Using Agile Processes on Documentum Projects
The document discusses using agile processes for Documentum projects. It provides background on the origins of agile methodologies and practices like Extreme Programming (XP). It then discusses how agile is well-suited for Documentum projects due to factors like small teams and internal projects. The document also presents a case study of how one company, Blue Fish, switched from waterfall to a hybrid agile methodology incorporating elements from RUP, XP, Scrum, and Crystal Clear. They realized benefits like higher user adoption, things getting done sooner, and improved management confidence.
Agile testing
1. Agile testing follows the agile manifesto which values individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan.
2. Context-driven testing principles state that the value of practices depends on their context, there are no best practices, people are most important, projects unfold unpredictably, and good testing requires judgment.
3. Agile methodologies like XP emphasize test-first programming, pair programming, short iterations, refactoring, user stories, and acceptance testing. Testers provide information to the team and find ways to set goals rather than focus on mistakes.
Large scale agile development practices
This document describes the experience of a large team developing and maintaining a large scale C# and SQL application over 15+ years using agile practices. Key aspects included:
- A team of 60 developers maintaining over 10 million lines of code
- Strict consistency enforced through architecture, naming conventions, patterns, and over 343,000 automated tests
- Continuous integration and distributed testing on developer machines to run the large test suite regularly
- A focus on reducing technical debt and making improvements that benefit all developers
Resume_Manish
This resume is for Manish Gautam, a senior software engineer with over 7 years of experience developing applications using Java/J2EE technologies. He has extensive experience designing, developing, and testing software applications for clients in telecom, healthcare and e-commerce. Some of his technical skills include Java, J2EE, Spring, Oracle, JSP, Servlets, and JBoss. He has worked as a technical lead and software engineer on various projects involving loyalty programs, document management systems, and call management.
Trends in Agile Testing by Lisa Crispin
- The document discusses trends in agile testing and how testing approaches have changed from traditional to agile methods. It focuses on practices like continuous integration, test-driven development, automating regression tests, and exploratory testing.
- Key aspects of agile testing covered include the whole team approach, collaboration between testers and developers, automating tests at different levels, and using feedback to continuously improve.
- The presentation highlights current trends like behavior-driven development, open source testing tools, and more emphasis on examples and collaboration with customers.
Agile Project Management Facing The Challenges Of Distributed Development U...
This ppt.is presented by Mayank Gupta (Globallogic) at Agile NCR 2009 Conference held on 18th July at Park Premier Hotel.
Test-Driven Development in the Corporate Workplace
What is TDD, and why is it giving traditional software development practices a run for their money? This presentation answers these questions, while focusing on a popular agile methodology, Extreme Programming (XP). It places a particular emphasis on the exploratory programming nature of XP and its testing practice, TDD. The paper also summarizes prior research on TDD and includes the results from a research survey conducted to compare TDD with traditional testing practices.
DevOps Resume of Sanu Panji
Versatile, Infrastructure Engineer (DevOps), having 4 years of experience in running successful method-oriented operations and taking initiatives for business excellence through process improvement
Esmail-Namazi-Resume
Esmaeil Namazi Aminlouei is an Oracle Fusion Middleware professional with over 15 years of experience in software engineering, development, management, and teaching. He has extensive expertise in Oracle technologies including SOA, BPM, ESB, and Java/J2EE. The document provides details on his career history, technical skills, work experience, and education.
Visual Studio ALM and DevOps Tools Walkthrough
If you're considering moving to Team Foundation Server or Visual Studio Team Services, this deck will walk you through the highlights, of which there are a TON!
The Journey to Continuous Delivery
XP teams take every iteration commitment seriously by delivering working software. Continuous Delivery of working product increments and early releasing gives concrete feedback about the state of the system at any time and also increases customer satisfaction.
Agile Software Development with XP
Extreme Programming (XP) is an agile software development methodology that focuses on rapid delivery of working software, customer satisfaction, simplicity, communication, and feedback. Key practices of XP include having working software delivered frequently in small releases, writing automated tests before code, pairing programmers, continuous refactoring, and integrating code daily. The goal of XP is to improve productivity and quality through practices like test-driven development, simple design, pair programming, and frequent feedback from customers.
Role Of Qa And Testing In Agile 1225221397167302 8
The document discusses the role of QA and testing in agile software development, describing key differences between traditional and agile testing approaches and outlining agile testing practices like test-driven development, continuous integration, regression testing, and exploratory testing. It also covers the role of testers in agile projects and provides an example of how one company, GlobalLogic, implements agile testing through a unique Velocity method and platform.
Agile Engineering Practices
Agile engineering practices from XP and FDD focusing on FDD. (Based on cultural challenges that XP faces.)
The Nuxeo Way: leveraging open source to build a world-class ECM platform
How can one create and deliver enterprise-class software, worth tens of years of R&D, with minimal capital investment? Open source can help, as well as the right context and ecosystem. This first talk will highlight the experience gained in the 8 first years of Nuxeo, and how they were applied to the latest iteration of the Nuxeo Platform.
Agile Methodology
Technology Talk at Robert Bosch and Java Conference by <a href="http://www.sureshkrishna.com">Suresh Krishna</a>
Similar to Agile xp crash_course_2010_05_21 (20)
xTreme Programming by Sejo Ćesić and Enis Zeherović
xTreme Programming by Sejo Ćesić and Enis Zeherović
Agile Project Management Facing The Challenges Of Distributed Development U...
Agile Project Management Facing The Challenges Of Distributed Development U...
Test-Driven Development in the Corporate Workplace
Test-Driven Development in the Corporate Workplace
Role Of Qa And Testing In Agile 1225221397167302 8
Role Of Qa And Testing In Agile 1225221397167302 8
The Nuxeo Way: leveraging open source to build a world-class ECM platform
The Nuxeo Way: leveraging open source to build a world-class ECM platform
Recently uploaded
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
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.Driving Business Innovation: Latest Generative AI Advancements & Success Story
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!
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
How to Get CNIC Information System with Paksim Ga.pptx
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.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
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.
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Building Production Ready Search Pipelines with Spark and Milvus
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.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Recently uploaded (20)
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Agile xp crash_course_2010_05_21
- 4. Individuals and interactions over processes and tools
- 5. Working software over comprehensive documentation
- 6. Customer collaboration over contract negotiation
- 7. Responding to change over following a plan
- 11. Roles in XP
- 12. Programmers
- 14. Product manager
- 15. (Testers)
- 16. (Coach)
- 18. (Domain experts)
- 22. Plan, Analysis, Design, Code, Test, Deploy
- 24. XP Lifecycle
- 25. Short iterations
- 26. User stories
- 28. Customer team one step ahead of technical team
- 29. XP Adoption
- 31. Colocated team
- 32. Team consensus
- 33. Team size
- 34. Use all the practices
- 35. (New project/ codebase)
- 37. Apply XP to existing project
- 38. Pay down technical debt
- 39. Setting along time for slack
- 40. ... and apply XP practices
- 41. XP Practices
- 42. Thinking
- 43. Pair programming
- 44. Energized work
- 47. Collaborating
- 48. Trust
- 52. Iteration demos
- 53. Releasing
- 54. Version Control
- 55. 10-minute build
- 57. Collective code ownership
- 58. No Bugs!
- 59. Done done
- 60. Planning
- 61. Vision
- 62. Release planning
- 63. Stories
- 65. Developing
- 67. Refactoring
- 68. Customer tests
- 69. Érdi Bálint twitter: @baaz blog: codigoergosum.com balint@codigoergosum.com http://www.meetup.com/ budapest-rb/
- 70. ?, ??, ???