Extreme programming practices ( xp )
•Download as PPTX, PDF•
1 like•438 views
Extreme programming, founded by Kent Beck one of the original signatories of Agile Manifesto is a lightweight agile methodology of agile software development and engineering .
Report
Share
Report
Share
Recommended
Hiep le - xp should be dead! here is why.
This slide was presented as at Global Scrum Gathering 2017. Extreme Programing (XP) is 20 years old. It discuss psychological and technological reasons why Extreme Programming should be considered "dead" and should become a normal regular software development approach.
XXLWEB
This document discusses database scalability. It defines scalability and distinguishes it from performance. It describes two methods of scaling databases: vertical scaling by adding resources to a single node, and horizontal scaling by adding new nodes and using sharding to distribute data. It provides examples of MySQL Cluster and MongoDB for horizontal scaling, noting advantages and disadvantages of each. Caching techniques are also presented as a way to reduce load on databases and enable scaling.
National Museums Scotland: An Application Upgrade
• Background to project
• Planning and making it happen
• Considering dependencies and impact
• It’s all about the data!
• The Good, the Bad and the Ugly
Pam Babes, Collections Information Manager,
Jo Macrae, Collections Information Officer &
Angus Kneale, Collections Information Systems Manager
National Museums of Scotland
Halfbrick Keynote Sydney Customer Appreciation Day
Halfbrick is a game studio founded in Brisbane, Australia in 2001 that has 5 game teams, 60 staff, and has released over 30 games. They wanted to get their games onto Facebook but needed hosting and user data storage capabilities. Amazon Web Services (AWS) was an obvious choice due to its competitive pricing, flexibility, and scalability. AWS has helped Halfbrick manage rapid user growth, build agile and flexible solutions, and cut costs. AWS acts as a partner by giving advice, helping with issues, and taking feedback to improve.
Xp exterme-programming-model
Extreme Programming (XP) is a software development methodology intended to improve quality and responsiveness to changing requirements. It involves 5 activities - planning, managing, designing, coding, and testing. Planning includes writing user stories, release planning, and frequent small releases. Managing involves dedicated workspace, stand-up meetings, and measuring velocity. Design focuses on simplicity, metaphors, CRC cards, and refactoring. Coding uses pair programming, tests first, and integration testing. All code must have unit tests that pass before release.
Extreme Programming (XP)
Extreme Programming (XP) is an agile software development methodology that focuses on customer satisfaction, rapid and frequent delivery of working software, simplicity, communication, and feedback. It consists of 12 core practices including planning game, small releases, simple design, refactoring, testing, pair programming, collective ownership, and continuous integration. XP values principles like communication, simplicity, feedback, courage, and quality work and aims to adapt to changing requirements, encourage teamwork, and facilitate collaboration between customers and developers.
Agile methods series (xp)
In the Agile Methods Series, we explore different Agile Methods. In this meetup you will understand what is XP Framework? Discover how important is applying XP in your organization and how it helps in your Agile adaptation.
============== Follow us ==============
Website: http://xpdays.org
Linked In: https://www.linkedin.com/company/xpdays
Facebook: https://www.facebook.com/xpdaysorg
Twitter: https://twitter.com/xpdaysorg
It's XP, Stupid
The document outlines Mike Harris's presentation on eXtreme Programming (XP). It begins by introducing the structure of the presentation, which will explain why XP is important and outline some of its key development practices. It then provides two case studies of projects, one that was underperforming and one that appeared high performing but had similar underlying issues. The document dives into what XP is, outlining its values, principles and practices. It concludes by discussing outcomes the speaker found when applying XP practices.
Recommended
Hiep le - xp should be dead! here is why.
This slide was presented as at Global Scrum Gathering 2017. Extreme Programing (XP) is 20 years old. It discuss psychological and technological reasons why Extreme Programming should be considered "dead" and should become a normal regular software development approach.
XXLWEB
This document discusses database scalability. It defines scalability and distinguishes it from performance. It describes two methods of scaling databases: vertical scaling by adding resources to a single node, and horizontal scaling by adding new nodes and using sharding to distribute data. It provides examples of MySQL Cluster and MongoDB for horizontal scaling, noting advantages and disadvantages of each. Caching techniques are also presented as a way to reduce load on databases and enable scaling.
National Museums Scotland: An Application Upgrade
• Background to project
• Planning and making it happen
• Considering dependencies and impact
• It’s all about the data!
• The Good, the Bad and the Ugly
Pam Babes, Collections Information Manager,
Jo Macrae, Collections Information Officer &
Angus Kneale, Collections Information Systems Manager
National Museums of Scotland
Halfbrick Keynote Sydney Customer Appreciation Day
Halfbrick is a game studio founded in Brisbane, Australia in 2001 that has 5 game teams, 60 staff, and has released over 30 games. They wanted to get their games onto Facebook but needed hosting and user data storage capabilities. Amazon Web Services (AWS) was an obvious choice due to its competitive pricing, flexibility, and scalability. AWS has helped Halfbrick manage rapid user growth, build agile and flexible solutions, and cut costs. AWS acts as a partner by giving advice, helping with issues, and taking feedback to improve.
Xp exterme-programming-model
Extreme Programming (XP) is a software development methodology intended to improve quality and responsiveness to changing requirements. It involves 5 activities - planning, managing, designing, coding, and testing. Planning includes writing user stories, release planning, and frequent small releases. Managing involves dedicated workspace, stand-up meetings, and measuring velocity. Design focuses on simplicity, metaphors, CRC cards, and refactoring. Coding uses pair programming, tests first, and integration testing. All code must have unit tests that pass before release.
Extreme Programming (XP)
Extreme Programming (XP) is an agile software development methodology that focuses on customer satisfaction, rapid and frequent delivery of working software, simplicity, communication, and feedback. It consists of 12 core practices including planning game, small releases, simple design, refactoring, testing, pair programming, collective ownership, and continuous integration. XP values principles like communication, simplicity, feedback, courage, and quality work and aims to adapt to changing requirements, encourage teamwork, and facilitate collaboration between customers and developers.
Agile methods series (xp)
In the Agile Methods Series, we explore different Agile Methods. In this meetup you will understand what is XP Framework? Discover how important is applying XP in your organization and how it helps in your Agile adaptation.
============== Follow us ==============
Website: http://xpdays.org
Linked In: https://www.linkedin.com/company/xpdays
Facebook: https://www.facebook.com/xpdaysorg
Twitter: https://twitter.com/xpdaysorg
It's XP, Stupid
The document outlines Mike Harris's presentation on eXtreme Programming (XP). It begins by introducing the structure of the presentation, which will explain why XP is important and outline some of its key development practices. It then provides two case studies of projects, one that was underperforming and one that appeared high performing but had similar underlying issues. The document dives into what XP is, outlining its values, principles and practices. It concludes by discussing outcomes the speaker found when applying XP practices.
Agile and Scrum 101 –PMI Central Indiana Chapter - Michael Nir - Slide deck
Agile and Scrum 101 –PMI Central Indiana Chapter - Michael Nir - Slide deckMichael Nir Business Agility Speaker and Coach
Agile and Scrum 101 – basics of Agile and Scrum
Scrum in 100 words:
• Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
• It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).
• The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.
• Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
In the presentation we discuss the basics of Agile and Scrum, the roles, ceremonies and artifacts. We add from our, from the trenches, lessons learned and better practices.
It's XP Stupid (2019)
We’re all doing Agile nowadays, aren’t we? We’ll all delivering software in an Agile way. But what does that mean? Does it mean sprints and stand-ups? Kanban even? But what about Extreme Programming? If as a development team we’re not using pair programming, test driven development, continuous integration, and other XP practices, then we’re not really doing Agile software development and we may be on a march to frustration, or even failure.
I’m going to look at why the current trend of companies and projects adopting Scrum, calling themselves Agile, but not transitioning their development to XP, is a recipe for disaster. I’d like to cover the main practices of XP as well as other good practices that can really help a team deliver quality software, whether they’re doing two-week sprints, Kanban, or even Waterfall.
https://www.youtube.com/watch?v=aZgnY9fAHOA
More XP-rience
More XP-rience
Video: https://youtu.be/DoFrzbpECCY
Thu, August 25, 4:00pm – 4:30pm
First Name: Niall
Last Name: Ross
Email Address: nross@cincom.com
Title: More XP-rience
Type: Talk
Abstract: In the 15 years since I last presented my 'XP-rience' of
eXtreme Programming to ESUG, I've had a lot more experience: of
working in partly and wholly not-colocated teams; of how I and others
actually think while doing XP; of the disadvantages and positive
advantages of non-colocation; of what is most used and most needed in
tools. This talk will let you (and me) discover if I've learned
anything in the last decade and a half.
Bio: Niall ended his undergraduate career with two intellectual
interests: computing and the theory of relativity. A quick check of
how much commercial work was available to relativity and gravitation
theorists made him decide to do academic research in that field and
then seek a commercial job in computing, rather than the other way
round. Niall started working commercially in IT in 1985. At first, he
was assigned to designing and implementing software engineering
process improvements; only after three years did he begin significant
writing and delivery of commercial software. This experience taught
him that intelligent people can form foolish ideas about software
engineering if they have not worked at the coding coalface of real,
large commercial projects.
Learning from this, Niall spent the nineties working on software to
manage complex, rapidly changing telecoms networks. A side effect of
this work was that it taught him much about how scale and rate of
change affects software. Early in the nineties, he discovered
Smalltalk. The more he used it the more he came to recognize its power
in this area. This perception was strengthened when he spent a year
delivering a telecoms management system in Java.
At the end of the decade, Niall formed his own software company to
offer consultancy in meta-data system design, Smalltalk and agile
methods. Over the next decade, he worked on a variety of
meta-data-driven systems, mostly in the financial domain.
Niall joined the Cincom Smalltalk Engineering Team nearly eight years
ago. His first task was to lead the team that does the weekly
VisualWorks builds - an experience he likened to doing brain surgery
on yourself every Friday (e.g., "Prepare new memory for insertion,
remove old memory … uh, I can't remember what I was going to do
next!").
Currently, he leads the Glorp and Database team. He also leads the
Custom Refactoring open-source project, which he co-founded, and the
SUnit open-source project.
XP should be dead. Here is why!
XP (which stands for eXtreme programming) was introduced in 1990s. However, things evolve and so does agile software development. Here is our colleague Lê Trọng Hiệp speaking at Global Scrum Gathering in Singapore in 2017.
22-AnOverviewOfScrum.pptx
Scrum is an agile process that focuses on delivering the highest priority features in short iterations called sprints. During a sprint, a self-organizing team works on user stories from the product backlog and meets daily to track progress. At the end of a sprint, working software is demoed to stakeholders. Scrum uses roles like product owner, ScrumMaster, and team as well as artifacts like product backlog, sprint backlog, and burn down charts to help deliver value quickly.
Introduction To Agile Refresh Savannah July20 2010 V1 4
The document provides an introduction to Agile software development methods. It discusses some of the limitations of traditional waterfall development approaches and why Agile methods have become more popular. It summarizes some of the core values and practices of Extreme Programming (XP), one of the earliest and most commonly used Agile methods. These include user stories, weekly iterations, test-driven development, pair programming, and continuous integration. The document also briefly discusses Scrum and other Agile methodologies.
What Is XP
XP, or Extreme Programming, is a lightweight software development method based on principles of communication, feedback, simplicity, and courage. It is designed for small teams developing quality software quickly in an environment of changing requirements. Key concepts include short iteration cycles, retrospectives, test-driven development, collective code ownership, on-site customers, and frequent small releases. The core practices are on-site customers, planning games, small releases, simple design, testing, refactoring, pair programming, and collective ownership. XP aims to address issues like business misunderstandings, changing requirements, schedule delays, adding unnecessary features, and misaligned priorities between business and development.
Kanban VS Scrum
Presentation from IT Jam conference (Kiev 2009) about basics of Kanban process and comparison analysis of Scrum and Kanban.
Extreme Programming (XP): Revisted
In his recent book, Clean Agile, Robert C "Uncle Bob" Martin chooses Extreme Programming (XP) for the basis of his explanation of Agile because "of all the Agile processes, XP is the best defined, the most complete, and the least muddled."
So why is it that in my professional life I only hear us speaking about Agile in terms of Scrum, Sprints, and possibly Kanban? Often I mention XP and people are not sure what I mean. Am I sure myself?
Coined in 1999 by Kent Beck and Ward Cunningham, XP has been with us for twenty years, but may of its practices have been with us for much longer. Many of them will be familar to you, but did you know they came from XP?
This talk aims to take us back to what XP is, how it fits in the Agile world, how it sits alongside other methodologies, and why, like Uncle Bob, I believe it is the best defined methodology, and what we should all be talking about.
The talk is based on a heavily refactored talk that Mike gave previously at Agile on the Beach conference, updated for 2020.
Given at Ox:Agile Meetup on February 11th 2020: https://www.meetup.com/OXAGILE/events/nxrdmrybcdbpb/
Scaling Scrum Without Crushing Its Soul - Patricia Kong - Agile NZ 2017
At the core of Scrum is the empowered self-organised team. However, when organisations scale, if they are not careful, they can disempower teams and destroy self-organisation. When they do, they don't get what they are looking for and the teams end up feeling defeated and unmotivated.
About Patricia Kong:
Patricia Kong is co-author of The Nexus Framework for Scaling Scrum published by Pearson. She is also a public speaker and mentor. Patricia is the Product Owner of the Scrum.org enterprise solutions program which includes the Nexus Framework, Evidence-based Management, Scrum Studio and Scrum Development Kit. She also created and launched the Scrum.org Partners in Principle Program.
Patricia is a people advocate fascinated by organisational behaviour and misbehaviours. She emerged through the financial services industry and has led product development, product management and marketing for several early-stage companies in the US and Europe. At Forrester Research, Patricia worked with their largest clients focusing on business development and delivery engagements. Patricia lived in France and now lives in her hometown of Boston. She is fluent in four languages.
Executing for Every Screen: Build, launch and sustain products for your custo...
The document discusses principles and best practices for designing products and interfaces that work across multiple screens and platforms. It emphasizes starting with principles, designing for user needs rather than specific platforms, building shared features and services first before customizing interfaces, and continuously evolving products based on data and user feedback.
Farhan's CV - Final
Syed Farhan Shah is a Pakistani national with over 15 years of experience in IT and software development. He has extensive skills in programming languages like ASP.NET, C#, PHP, and databases like SQL Server and MySQL. He has worked as an IT manager, software designer, and quality assurance specialist on various projects. He holds a Bachelor's degree in Computer Science and is seeking a challenging position to further develop his technical abilities.
Software architecture : From project management to deployment
In this video I have shared the areas we should think as a software architect when we design a software system
Intro to Scrum - Balance Internet
This document provides an introduction and overview of Scrum, an agile framework for managing product development projects. It describes the origins of Scrum and its key characteristics such as self-organizing cross-functional teams, sprints of 1-4 weeks to deliver working software, and artifacts like the product and sprint backlogs. The roles of Product Owner, Scrum Master, and Team are explained. Ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives are outlined. Finally, the document shows how the Scrum framework brings together its roles, ceremonies, and artifacts to guide a team's work within a sprint.
Crash Course Scrum - handout
A 1 Day training that shows you all you need to know about Scrum, the afternoon contains a practical part where we perform several sprints using Lego as our means of production
Machine Learning in SurveyMonkey
The document discusses Machine Learning at SurveyMonkey. It outlines current ML models like survey scoring, spam detection, and churn prediction. It then describes the ML platform and infrastructure using Python, Docker, and tools like Jupyter Notebook, SKLearn and TensorFlow. Future work includes improving the data pipeline and retraining scheduling. The document concludes by mentioning open ML engineer roles in Ottawa.
Going extreme-with-extreme-programming
I recently gave a talk at Architecting Innovation about going extreme with Extreme Programming. In these slides, I give a brief history of Extreme Programming, what are some of the guiding principles of Extreme Programming and why an organization might want to choose Extreme Programming over other software development methodologies.
A Brief Introduction to Kanban
Mike Harris is the Software Engineering Lead for SSRN (Social Science Research Network), which allows researchers to share pre-print papers. His team is using Agile techniques like Scrum, Lean, and Kanban to build out new microservices on AWS and migrate the existing platform. Key aspects of their approach include daily stand-ups, frequent retrospectives, using Kanban boards with work-in-progress limits to visualize work, and emphasizing practices like test-driven development, pair programming, and keeping technical debt low.
"How To Race Squirrels" at Develop Conference in Brighton, 21st July 2011
The document outlines Rob Davis's process for designing and producing commissioned games at his company Playniac. The process involves several stages: developing briefs and proposals, concept development and a written specification, wireframing using use cases and static/interactive wireframes, paper testing, creating game assets, user testing for feedback, balancing the game mechanics, and wrapping up the project. Each stage provides important inputs and refinements to help design fun and balanced games that meet the client's needs.
Agile Methods - An Overview - Marc Bless - 2009
The document provides an overview of agile methods. It discusses the motivation for agile approaches due to failures of traditional waterfall planning. Key aspects of agile history and principles are outlined, including the Agile Manifesto which values individuals, working software, customer collaboration and responding to change over processes, documentation, contract negotiation and following a plan. Specific agile methods like Scrum, Extreme Programming and Feature Driven Development are also mentioned.
Incident management with jira
Incident management in Jira focuses on short-term solutions to unplanned interruptions in systems or services. The Jira Service Desk template includes an incident workflow that guides users to log, diagnose, and resolve incidents. This process involves service members reporting issues, the service desk logging and categorizing incidents, prioritizing response, escalating if needed, resolving the underlying problem, verifying the fix, and closing the incident. Postmortem reports and incident response reports provide documentation and analysis after significant incidents.
The myth of 'real javascript developer'
The document repeats the same line "Jyaasa : We Design, Build and Develop Products" 20 times without providing any other context or information. It does not have a clear topic or message that can be summarized in 3 sentences or less.
More Related Content
Similar to Extreme programming practices ( xp )
Agile and Scrum 101 –PMI Central Indiana Chapter - Michael Nir - Slide deck
Agile and Scrum 101 –PMI Central Indiana Chapter - Michael Nir - Slide deckMichael Nir Business Agility Speaker and Coach
Agile and Scrum 101 – basics of Agile and Scrum
Scrum in 100 words:
• Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.
• It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).
• The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.
• Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.
In the presentation we discuss the basics of Agile and Scrum, the roles, ceremonies and artifacts. We add from our, from the trenches, lessons learned and better practices.
It's XP Stupid (2019)
We’re all doing Agile nowadays, aren’t we? We’ll all delivering software in an Agile way. But what does that mean? Does it mean sprints and stand-ups? Kanban even? But what about Extreme Programming? If as a development team we’re not using pair programming, test driven development, continuous integration, and other XP practices, then we’re not really doing Agile software development and we may be on a march to frustration, or even failure.
I’m going to look at why the current trend of companies and projects adopting Scrum, calling themselves Agile, but not transitioning their development to XP, is a recipe for disaster. I’d like to cover the main practices of XP as well as other good practices that can really help a team deliver quality software, whether they’re doing two-week sprints, Kanban, or even Waterfall.
https://www.youtube.com/watch?v=aZgnY9fAHOA
More XP-rience
More XP-rience
Video: https://youtu.be/DoFrzbpECCY
Thu, August 25, 4:00pm – 4:30pm
First Name: Niall
Last Name: Ross
Email Address: nross@cincom.com
Title: More XP-rience
Type: Talk
Abstract: In the 15 years since I last presented my 'XP-rience' of
eXtreme Programming to ESUG, I've had a lot more experience: of
working in partly and wholly not-colocated teams; of how I and others
actually think while doing XP; of the disadvantages and positive
advantages of non-colocation; of what is most used and most needed in
tools. This talk will let you (and me) discover if I've learned
anything in the last decade and a half.
Bio: Niall ended his undergraduate career with two intellectual
interests: computing and the theory of relativity. A quick check of
how much commercial work was available to relativity and gravitation
theorists made him decide to do academic research in that field and
then seek a commercial job in computing, rather than the other way
round. Niall started working commercially in IT in 1985. At first, he
was assigned to designing and implementing software engineering
process improvements; only after three years did he begin significant
writing and delivery of commercial software. This experience taught
him that intelligent people can form foolish ideas about software
engineering if they have not worked at the coding coalface of real,
large commercial projects.
Learning from this, Niall spent the nineties working on software to
manage complex, rapidly changing telecoms networks. A side effect of
this work was that it taught him much about how scale and rate of
change affects software. Early in the nineties, he discovered
Smalltalk. The more he used it the more he came to recognize its power
in this area. This perception was strengthened when he spent a year
delivering a telecoms management system in Java.
At the end of the decade, Niall formed his own software company to
offer consultancy in meta-data system design, Smalltalk and agile
methods. Over the next decade, he worked on a variety of
meta-data-driven systems, mostly in the financial domain.
Niall joined the Cincom Smalltalk Engineering Team nearly eight years
ago. His first task was to lead the team that does the weekly
VisualWorks builds - an experience he likened to doing brain surgery
on yourself every Friday (e.g., "Prepare new memory for insertion,
remove old memory … uh, I can't remember what I was going to do
next!").
Currently, he leads the Glorp and Database team. He also leads the
Custom Refactoring open-source project, which he co-founded, and the
SUnit open-source project.
XP should be dead. Here is why!
XP (which stands for eXtreme programming) was introduced in 1990s. However, things evolve and so does agile software development. Here is our colleague Lê Trọng Hiệp speaking at Global Scrum Gathering in Singapore in 2017.
22-AnOverviewOfScrum.pptx
Scrum is an agile process that focuses on delivering the highest priority features in short iterations called sprints. During a sprint, a self-organizing team works on user stories from the product backlog and meets daily to track progress. At the end of a sprint, working software is demoed to stakeholders. Scrum uses roles like product owner, ScrumMaster, and team as well as artifacts like product backlog, sprint backlog, and burn down charts to help deliver value quickly.
Introduction To Agile Refresh Savannah July20 2010 V1 4
The document provides an introduction to Agile software development methods. It discusses some of the limitations of traditional waterfall development approaches and why Agile methods have become more popular. It summarizes some of the core values and practices of Extreme Programming (XP), one of the earliest and most commonly used Agile methods. These include user stories, weekly iterations, test-driven development, pair programming, and continuous integration. The document also briefly discusses Scrum and other Agile methodologies.
What Is XP
XP, or Extreme Programming, is a lightweight software development method based on principles of communication, feedback, simplicity, and courage. It is designed for small teams developing quality software quickly in an environment of changing requirements. Key concepts include short iteration cycles, retrospectives, test-driven development, collective code ownership, on-site customers, and frequent small releases. The core practices are on-site customers, planning games, small releases, simple design, testing, refactoring, pair programming, and collective ownership. XP aims to address issues like business misunderstandings, changing requirements, schedule delays, adding unnecessary features, and misaligned priorities between business and development.
Kanban VS Scrum
Presentation from IT Jam conference (Kiev 2009) about basics of Kanban process and comparison analysis of Scrum and Kanban.
Extreme Programming (XP): Revisted
In his recent book, Clean Agile, Robert C "Uncle Bob" Martin chooses Extreme Programming (XP) for the basis of his explanation of Agile because "of all the Agile processes, XP is the best defined, the most complete, and the least muddled."
So why is it that in my professional life I only hear us speaking about Agile in terms of Scrum, Sprints, and possibly Kanban? Often I mention XP and people are not sure what I mean. Am I sure myself?
Coined in 1999 by Kent Beck and Ward Cunningham, XP has been with us for twenty years, but may of its practices have been with us for much longer. Many of them will be familar to you, but did you know they came from XP?
This talk aims to take us back to what XP is, how it fits in the Agile world, how it sits alongside other methodologies, and why, like Uncle Bob, I believe it is the best defined methodology, and what we should all be talking about.
The talk is based on a heavily refactored talk that Mike gave previously at Agile on the Beach conference, updated for 2020.
Given at Ox:Agile Meetup on February 11th 2020: https://www.meetup.com/OXAGILE/events/nxrdmrybcdbpb/
Scaling Scrum Without Crushing Its Soul - Patricia Kong - Agile NZ 2017
At the core of Scrum is the empowered self-organised team. However, when organisations scale, if they are not careful, they can disempower teams and destroy self-organisation. When they do, they don't get what they are looking for and the teams end up feeling defeated and unmotivated.
About Patricia Kong:
Patricia Kong is co-author of The Nexus Framework for Scaling Scrum published by Pearson. She is also a public speaker and mentor. Patricia is the Product Owner of the Scrum.org enterprise solutions program which includes the Nexus Framework, Evidence-based Management, Scrum Studio and Scrum Development Kit. She also created and launched the Scrum.org Partners in Principle Program.
Patricia is a people advocate fascinated by organisational behaviour and misbehaviours. She emerged through the financial services industry and has led product development, product management and marketing for several early-stage companies in the US and Europe. At Forrester Research, Patricia worked with their largest clients focusing on business development and delivery engagements. Patricia lived in France and now lives in her hometown of Boston. She is fluent in four languages.
Executing for Every Screen: Build, launch and sustain products for your custo...
The document discusses principles and best practices for designing products and interfaces that work across multiple screens and platforms. It emphasizes starting with principles, designing for user needs rather than specific platforms, building shared features and services first before customizing interfaces, and continuously evolving products based on data and user feedback.
Farhan's CV - Final
Syed Farhan Shah is a Pakistani national with over 15 years of experience in IT and software development. He has extensive skills in programming languages like ASP.NET, C#, PHP, and databases like SQL Server and MySQL. He has worked as an IT manager, software designer, and quality assurance specialist on various projects. He holds a Bachelor's degree in Computer Science and is seeking a challenging position to further develop his technical abilities.
Software architecture : From project management to deployment
In this video I have shared the areas we should think as a software architect when we design a software system
Intro to Scrum - Balance Internet
This document provides an introduction and overview of Scrum, an agile framework for managing product development projects. It describes the origins of Scrum and its key characteristics such as self-organizing cross-functional teams, sprints of 1-4 weeks to deliver working software, and artifacts like the product and sprint backlogs. The roles of Product Owner, Scrum Master, and Team are explained. Ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives are outlined. Finally, the document shows how the Scrum framework brings together its roles, ceremonies, and artifacts to guide a team's work within a sprint.
Crash Course Scrum - handout
A 1 Day training that shows you all you need to know about Scrum, the afternoon contains a practical part where we perform several sprints using Lego as our means of production
Machine Learning in SurveyMonkey
The document discusses Machine Learning at SurveyMonkey. It outlines current ML models like survey scoring, spam detection, and churn prediction. It then describes the ML platform and infrastructure using Python, Docker, and tools like Jupyter Notebook, SKLearn and TensorFlow. Future work includes improving the data pipeline and retraining scheduling. The document concludes by mentioning open ML engineer roles in Ottawa.
Going extreme-with-extreme-programming
I recently gave a talk at Architecting Innovation about going extreme with Extreme Programming. In these slides, I give a brief history of Extreme Programming, what are some of the guiding principles of Extreme Programming and why an organization might want to choose Extreme Programming over other software development methodologies.
A Brief Introduction to Kanban
Mike Harris is the Software Engineering Lead for SSRN (Social Science Research Network), which allows researchers to share pre-print papers. His team is using Agile techniques like Scrum, Lean, and Kanban to build out new microservices on AWS and migrate the existing platform. Key aspects of their approach include daily stand-ups, frequent retrospectives, using Kanban boards with work-in-progress limits to visualize work, and emphasizing practices like test-driven development, pair programming, and keeping technical debt low.
"How To Race Squirrels" at Develop Conference in Brighton, 21st July 2011
The document outlines Rob Davis's process for designing and producing commissioned games at his company Playniac. The process involves several stages: developing briefs and proposals, concept development and a written specification, wireframing using use cases and static/interactive wireframes, paper testing, creating game assets, user testing for feedback, balancing the game mechanics, and wrapping up the project. Each stage provides important inputs and refinements to help design fun and balanced games that meet the client's needs.
Agile Methods - An Overview - Marc Bless - 2009
The document provides an overview of agile methods. It discusses the motivation for agile approaches due to failures of traditional waterfall planning. Key aspects of agile history and principles are outlined, including the Agile Manifesto which values individuals, working software, customer collaboration and responding to change over processes, documentation, contract negotiation and following a plan. Specific agile methods like Scrum, Extreme Programming and Feature Driven Development are also mentioned.
Similar to Extreme programming practices ( xp ) (20)
Agile and Scrum 101 –PMI Central Indiana Chapter - Michael Nir - Slide deck
Agile and Scrum 101 –PMI Central Indiana Chapter - Michael Nir - Slide deck
Introduction To Agile Refresh Savannah July20 2010 V1 4
Introduction To Agile Refresh Savannah July20 2010 V1 4
Scaling Scrum Without Crushing Its Soul - Patricia Kong - Agile NZ 2017
Scaling Scrum Without Crushing Its Soul - Patricia Kong - Agile NZ 2017
Executing for Every Screen: Build, launch and sustain products for your custo...
Executing for Every Screen: Build, launch and sustain products for your custo...
Software architecture : From project management to deployment
Software architecture : From project management to deployment
"How To Race Squirrels" at Develop Conference in Brighton, 21st July 2011
"How To Race Squirrels" at Develop Conference in Brighton, 21st July 2011
More from Jyaasa Technologies
Incident management with jira
Incident management in Jira focuses on short-term solutions to unplanned interruptions in systems or services. The Jira Service Desk template includes an incident workflow that guides users to log, diagnose, and resolve incidents. This process involves service members reporting issues, the service desk logging and categorizing incidents, prioritizing response, escalating if needed, resolving the underlying problem, verifying the fix, and closing the incident. Postmortem reports and incident response reports provide documentation and analysis after significant incidents.
The myth of 'real javascript developer'
The document repeats the same line "Jyaasa : We Design, Build and Develop Products" 20 times without providing any other context or information. It does not have a clear topic or message that can be summarized in 3 sentences or less.
Microservices
Microservices is an architectural style that structures an application as a collection of
loosely coupled services, which implement business capabilities.
Facade pattern in rails
The document discusses the facade pattern in Ruby on Rails applications. It describes the facade pattern as providing a unified interface to isolate complexity and hide subsystem interfaces. It then gives an example of using a facade pattern to simplify a chat room controller in Rails that was preparing a lot of data. A ChatRoomsFacade class is created that initializes the necessary data, allowing the controller to be simplified by just initializing the facade. The facade pattern hides complexity and provides a single interface, simplifying controllers in Rails especially for larger projects.
Scrum ceromonies
Scrum is an iterative and incremental agile software development framework for managing product development.
An introduction to bitcoin
a type of digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, operating independently of a central bank.
Tor network
Tor is free software that enables anonymous communication. It conceals a user's location and usage through a network of over 7,000 relays. Tor implements onion routing, which encrypts data including destination IP addresses and passes encrypted data through multiple relays, each decrypting a single layer to reveal only the next relay. This allows anonymously browsing the internet, protecting privacy and security such as from government surveillance disclosed by Edward Snowden.
Collective ownership in agile teams
What is collective code ownership in agile teams? what are its advantages? .What are the common pitfalls of it ?.
What would be the ways to implement into software development teams. If you would like to talk more on the topic feel free to email kapil@jyaasa.com
Push notification
This document discusses using Pusher for push notifications. Pusher allows sending push notifications from a backend server to user interfaces like mobile and desktop apps. It avoids problems with polling by using websockets for real-time notifications. The document explains how to set up Pusher by creating an account and app, and integrating it into server-side code using various languages like Ruby, and client-side code using JavaScript or React Native.
The Design Thinking Process
The document outlines the 5 key stages in the design thinking process: empathize, define, ideate, prototype, and test. It describes each stage in detail. Empathize involves understanding users through observation and interviews. Define brings clarity to the problem based on user needs. Ideate focuses on generating many creative solutions through brainstorming. Prototype creates artifacts to test possibilities. Test gets feedback from users to refine solutions and further learn about the user. The overall process is presented as human-centered, iterative, and solution-focused.
User story
This document discusses user stories, which are short descriptions of a desired new feature written from the perspective of users or customers. User stories should keep it simple and focus on who wants the feature, what they want to accomplish, and why. They are important because they provide precise yet spare information that is useful for planning and understandable to both technical and non-technical people.
Design sprint
A Design sprint is a time-constrained, five-phase process that uses design thinking to reduce the risk when bringing a new product, service or a feature to the market.
Data Flow Diagram
A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs and outputs. As its name indicates its focus is on the flow of information, where data comes from, where it goes and how it gets stored.
OKRs and Actions Overview
Objectives and Key Results (OKR) is a popular technique for setting and communicating goals and results in organizations. Its main goal is to connect company, team and personal objectives to measurable results, making people move together in right direction.
Vue.js
The document discusses using Vue.js to reduce complexity in web development. It introduces some key concepts in Vue.js like data binding with v-model, conditional rendering with v-if, listing data with v-for, handling events with v-on, and conditional rendering with v-if and v-show. It also provides examples of how to install Vue.js via npm, bower or CDN, and basic usage with el, data, methods. Towards the end, it mentions running a demo customer management app using Vue and Rails.
Active record in rails 5
The document discusses Active Record attributes in Rails 5. It explains that Active Record's detected attribute types can be overridden with the attribute method. The attribute method can also define a default value and specify if an attribute is an array or range. Attributes do not require a matching database column. Examples demonstrate overriding an attribute type from decimal to integer, setting default values, and defining array attributes.
Design Patern::Adaptor pattern
The adapter pattern is a software design pattern that allows the interface of an existing class to be used as another interface.
Association in rails
The document discusses various types of associations in Rails including belongs_to, has_one, has_many, has_many :through, has_one :through, has_and_belongs_to_many, and polymorphic associations. It provides examples of how to declare each association type in the model and how to set up the corresponding database migrations. It also covers choosing between different association types and using self-joins for models that associate with themselves.
Web design layout pattern
The document discusses visual hierarchy and layout patterns in web design. It describes the F-pattern and Z-pattern layouts. The F-pattern follows the shape of the letter F as users first scan horizontally across the top of the page from left to right. The Z-pattern aims to anticipate the user's needs by presenting key information like branding, calls-to-action, and structure up front. Both patterns aim to create a natural reading flow that guides users efficiently through content.
Command Pattern in Ruby
The command pattern is a behavioral design pattern in which an object is used to encapsulate all information needed to perform an action or trigger an event at a later time.
More from Jyaasa Technologies (20)
Recently uploaded
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Vitthal Shirke Java Microservices Resume.pdf
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
E-commerce Application Development Company.pdf
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
GraphSummit Paris - The art of the possible with Graph Technology
Sudhir Hasbe, Chief Product Officer, 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.
OpenMetadata Community Meeting - 5th June 2024
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Measures in SQL (SIGMOD 2024, Santiago, Chile)
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
Unveiling the Advantages of Agile Software Development.pdf
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
WhatsApp offers simple, reliable, and private messaging and calling services for free worldwide. With end-to-end encryption, your personal messages and calls are secure, ensuring only you and the recipient can access them. Enjoy voice and video calls to stay connected with loved ones or colleagues. Express yourself using stickers, GIFs, or by sharing moments on Status. WhatsApp Business enables global customer outreach, facilitating sales growth and relationship building through showcasing products and services. Stay connected effortlessly with group chats for planning outings with friends or staying updated on family conversations.
原版定制美国纽约州立大学奥尔巴尼分校毕业证学位证书原版一模一样
原版一模一样【微信：741003700 】【美国纽约州立大学奥尔巴尼分校毕业证学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
SMS API Integration in Saudi Arabia| Best SMS API Service
Discover the benefits and implementation of SMS API integration in the UAE and Middle East. This comprehensive guide covers the importance of SMS messaging APIs, the advantages of bulk SMS APIs, and real-world case studies. Learn how CEQUENS, a leader in communication solutions, can help your business enhance customer engagement and streamline operations with innovative CPaaS, reliable SMS APIs, and omnichannel solutions, including WhatsApp Business. Perfect for businesses seeking to optimize their communication strategies in the digital age.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS Security Version 1.2 was adopted in 2024. This revision strengthens support for long runnings systems adding new cryptographic algorithms, certificate revocation, and hardness against DoS attacks.
What is Master Data Management by PiLog Group
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
Using Query Store in Azure PostgreSQL to Understand Query Performance
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers. This video you can watch from my youtube channel at https://youtu.be/m-F-mZA3MkU
Using Xen Hypervisor for Functional Safety
An update on making Xen hypervisor functionally safe and enhancing its usage in automotive and industrial use cases
Recently uploaded (20)
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
GraphSummit Paris - The art of the possible with Graph Technology
GraphSummit Paris - The art of the possible with Graph Technology
Unveiling the Advantages of Agile Software Development.pdf
Unveiling the Advantages of Agile Software Development.pdf
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
SMS API Integration in Saudi Arabia| Best SMS API Service
SMS API Integration in Saudi Arabia| Best SMS API Service
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS-Security 1.2 - What's New? Stronger security for long-running systems
Using Query Store in Azure PostgreSQL to Understand Query Performance
Using Query Store in Azure PostgreSQL to Understand Query Performance
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers.pptx
Extreme programming practices ( xp )
- 2. About Me • Kapil Raj Nakhwa Shrestha • Co-founder of Jyaasa Technologies Pvt ltd. • 9 years experience working with Ruby and Ruby and rails • kapil@jyaasa.com
- 3. Origins •March 6th, 1996, Chrysler Comprehensive Compensation System ( C3) . •Kent Beck Kent Beck when he was young ( Not me )
- 4. • Instead of delivering everything you could possible want on some date in future, Xp delivers the software as you want it. • Simple yet effective environment for enabling teams to become highly productive. • Improves the way we develop software in 5 key aspects.
- 5. Xp Project Heartbeat Type to enter a caption.
- 6. XP values • Communication • Simplicity • Feedback • Respect • Courage
- 7. Xp Rules ( Practices) • Planning • Managing • Designing • Coding • Testing
- 8. Planning • User Stories • Release Plan • Iteration Plan
- 9. Planning
- 10. Managing • Sustainable Pace • Daily Stand up • Measure Project Velocity • Move people around • Fix Xp when It breaks
- 11. Designing • Simplicity ( TUBE ) • Choose a system metaphor • CRC cards for system design • Use Spike to reduce risk • YAGNI • Refactor Mercilessly
- 12. Coding • Customer is always available • Write code to agreed standard • Write unit tests first • Pair Program • Sequential Integration • Collective Ownership
- 13. Customer is always available
- 14. Testing • All code must have unit tests • All tests must pass before production • When bug is found , Create a test • Acceptance tests are run often and metrics provided to the team.
- 15. XP FlowChart
- 17. FeedBack Loops in XP
- 18. The paradox of a process If you do not use your process, It will not help you. If your process does not help you, You would not use it.
- 19. Want to discuss more on XP? • kapil@jyaasa.com • twitter: xecutioner303