Scrum_XP_18Nov16
•Download as PPTX, PDF•
0 likes•108 views
The document discusses Scrum and eXtreme Programming (XP), two frameworks that follow the Agile Manifesto. It describes Scrum as focusing on project management with roles, meetings and cycles, while XP focuses on practical development with 12 processes like planning, testing, and pair programming. The document encourages pair programming exercises and thanks several contributors.
Report
Share
Report
Share
Recommended
Draft of mid internship presentation
The document appears to be a series of slides from mid-internship presentations given by multiple interns. The slides cover topics like adapting to scrum methodology, learning new technologies through sessions and trainings, daily stand-up meetings, tracking work using a time server and Team Foundation Server, organizing work in sprints with PBIs and tasks, agile development practices, necessary tools, getting accustomed to a professional coding environment and practices, self-assessment, handling large projects, used technologies like Visual Studio and SQL Server, and recapping one intern's contributions over three months of their internship.
Group Process by Example - a PO’s and SM’s perspective
This document summarizes a presentation given by two Scrum practitioners on their experiences with team development based on Tuckman's model of group formation. It describes the four stages - forming, storming, norming, and performing - and provides examples of how teams typically behave in each stage as well as recommendations for facilitating positive progression. Key takeaways are to build safety for open conflict in storming, give the team space to develop cohesion in norming, and empower high performance in performing. The document aims to help others understand typical group processes and how to accelerate team growth.
Agile project management with scrum
This document outlines an agenda for a course on Agile development methods. The course covers core Agile concepts like the Agile Manifesto and principles. It then details the Scrum framework, including roles like Product Owner and Scrum Master, artifacts like product and sprint backlogs, and ceremonies like sprint planning, daily standups, reviews, and retrospectives. Other topics include user stories, estimation techniques, and implementing Agile practices in Microsoft Team Foundation Server. The document provides an overview of the topics to be discussed during the course sessions.
Skalowanie Agile
The document discusses three case studies of scaling Agile practices to the enterprise level. The first case study describes challenges with a team using only Scrum practices and how adopting additional XP practices like test-driven development and continuous integration helped. The second case study explains problems that arose from multiple teams working on a shared backlog and lack of synchronization; Kanban was introduced to help. The third case study outlines issues with multiple outsourced teams and lack of integration; Kanban, additional roles, and improved coordination helped address these challenges at the portfolio level.
Scrum sprint structure workshop by Nermina Durmić
This document outlines the key elements of a Scrum sprint structure:
1. It defines common Scrum terms like user stories, sprints, product owner, and scrum master.
2. It describes the sprint flow as consisting of product backlog, backlog refinement, sprint planning, daily scrums, development, testing, sprint review, and retrospective.
3. It provides information on creating and ordering a product backlog, estimating effort using planning poker, and planning a sprint to select backlog items within the team's estimated sprint capacity.
Agile overview
Agile is a structured and iterative approach to project management and software development that focuses on collaboration between self-organizing teams. The key principles of Agile include satisfying customers through early delivery, welcoming changing requirements, frequent delivery of working software, daily collaboration between business and development teams, and trusting teams to do their work. Common Agile frameworks include Scrum, Kanban, and Extreme Programming. Roles include the Project Manager, Product Owner, and Team Members. Ceremonies like daily stand-ups, retrospectives and reviews help structure the process. Metrics like burn down charts and velocity are used to measure progress.
The Role of the Scrum Master
The document discusses the role of a Scrum Master at East Agile. As Scrum Master, they guide teams to follow the Scrum process, facilitate communication between the Product Owner and team, and help improve team productivity, engineering practices, and tools. At East Agile, the Scrum Master supports the Product Owner by training them on the agile process and helping with story breakdown and prioritization. They also support teams by facilitating daily knowledge sharing meetings and removing barriers to work.
Valerie Andrianova - Baking Boards... | Agile Delivery 2017
Valerie Andrianova's slides from Agile Delivery 2017 which took place in Farringdon on 18th October.
Recommended
Draft of mid internship presentation
The document appears to be a series of slides from mid-internship presentations given by multiple interns. The slides cover topics like adapting to scrum methodology, learning new technologies through sessions and trainings, daily stand-up meetings, tracking work using a time server and Team Foundation Server, organizing work in sprints with PBIs and tasks, agile development practices, necessary tools, getting accustomed to a professional coding environment and practices, self-assessment, handling large projects, used technologies like Visual Studio and SQL Server, and recapping one intern's contributions over three months of their internship.
Group Process by Example - a PO’s and SM’s perspective
This document summarizes a presentation given by two Scrum practitioners on their experiences with team development based on Tuckman's model of group formation. It describes the four stages - forming, storming, norming, and performing - and provides examples of how teams typically behave in each stage as well as recommendations for facilitating positive progression. Key takeaways are to build safety for open conflict in storming, give the team space to develop cohesion in norming, and empower high performance in performing. The document aims to help others understand typical group processes and how to accelerate team growth.
Agile project management with scrum
This document outlines an agenda for a course on Agile development methods. The course covers core Agile concepts like the Agile Manifesto and principles. It then details the Scrum framework, including roles like Product Owner and Scrum Master, artifacts like product and sprint backlogs, and ceremonies like sprint planning, daily standups, reviews, and retrospectives. Other topics include user stories, estimation techniques, and implementing Agile practices in Microsoft Team Foundation Server. The document provides an overview of the topics to be discussed during the course sessions.
Skalowanie Agile
The document discusses three case studies of scaling Agile practices to the enterprise level. The first case study describes challenges with a team using only Scrum practices and how adopting additional XP practices like test-driven development and continuous integration helped. The second case study explains problems that arose from multiple teams working on a shared backlog and lack of synchronization; Kanban was introduced to help. The third case study outlines issues with multiple outsourced teams and lack of integration; Kanban, additional roles, and improved coordination helped address these challenges at the portfolio level.
Scrum sprint structure workshop by Nermina Durmić
This document outlines the key elements of a Scrum sprint structure:
1. It defines common Scrum terms like user stories, sprints, product owner, and scrum master.
2. It describes the sprint flow as consisting of product backlog, backlog refinement, sprint planning, daily scrums, development, testing, sprint review, and retrospective.
3. It provides information on creating and ordering a product backlog, estimating effort using planning poker, and planning a sprint to select backlog items within the team's estimated sprint capacity.
Agile overview
Agile is a structured and iterative approach to project management and software development that focuses on collaboration between self-organizing teams. The key principles of Agile include satisfying customers through early delivery, welcoming changing requirements, frequent delivery of working software, daily collaboration between business and development teams, and trusting teams to do their work. Common Agile frameworks include Scrum, Kanban, and Extreme Programming. Roles include the Project Manager, Product Owner, and Team Members. Ceremonies like daily stand-ups, retrospectives and reviews help structure the process. Metrics like burn down charts and velocity are used to measure progress.
The Role of the Scrum Master
The document discusses the role of a Scrum Master at East Agile. As Scrum Master, they guide teams to follow the Scrum process, facilitate communication between the Product Owner and team, and help improve team productivity, engineering practices, and tools. At East Agile, the Scrum Master supports the Product Owner by training them on the agile process and helping with story breakdown and prioritization. They also support teams by facilitating daily knowledge sharing meetings and removing barriers to work.
Valerie Andrianova - Baking Boards... | Agile Delivery 2017
Valerie Andrianova's slides from Agile Delivery 2017 which took place in Farringdon on 18th October.
Working in teams vs working individually
A comparison between the software development practices: invidual developers vs development teams. Presentation for IT students at Kaunas University of Technology in Lithuania
Journey with XP a case study in embedded domain by Pradeep Kumar NR
Journey with XP a case study in embedded domain @XP conference 2016 Through this presentation, Pradeep will share his learning experience and describe his journey with XP that has been part of his life since 2 yrs. This talk also unfolds some aspects of how to adopt XP in embedded space with multiple layers involved and when there is a dependency on hardware
Extreme programming
Extreme Programming is a methodology in an Agile way for developing quality software or change stakeholder's requirements quickly by putting more focus on coding rather than design and continuous collaboration with the customer.
Scrum In 15 Minutes
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
Pair programming
Pair programming has benefits such as less bugs, better code quality, spreading knowledge across teams, and creating a learning environment through improved communication. Developers should pair when working on complex, critical, or new features, or when a team has a new member. Techniques like driver-navigator and ping-pong pairing help structure the process, with the driver writing code and the navigator providing guidance, reviews, and testing. Regularly switching roles and keeping an open dialogue are important for effective pairing.
"You Made a Game, Now What?" Week2 game production methods and realities
A presentation on production methods for game development, including overviews of iterative design, waterfall, agile, and scrum.
I don't do agile, i am agile (Barry O'Reilly)
1. The document discusses various agile frameworks like Scrum, XP, and Kanban and their associated practices.
2. It emphasizes that organizations should focus on using practices that suit their specific context rather than strictly adhering to a single framework.
3. The document advocates for a lean, adaptive approach to agile by continuously questioning practices, eliminating waste, and prioritizing delivering value over following prescriptive processes.
I don't do Agile, I AM Agile!
Too often in agile software development we tend to use methodologies and all their components simply because the rule book says so. Why not select the tool based on the context of the task your
trying to complete.
Anything that you use that does not lead towards a direct value add to the final product delivered is simply an overhead and waste.
This presentation covers discovering what
is the minimum amount of practices that are required to achieve the goal of delivering a product we desire - safely, quickly and successfully. Thus allowing us to start getting feedback and improving it.
How to Write a Winning Session Submission
This webcast is for DrupalCon sponsors on how to submit a session abstract that will resonate with the selection team.
Introduction to Agile, by J.D. Meier
A brief and visual introduction to the Agile.
Learn the Agile mindset and the big 3 (Extreme Programming, Scrum, and Kanban). Be able to whiteboard a simple view of how each one works to get things done and make things happen.
Extreme Programming 1st.pdf
Extreme Programming (XP) is an agile software development framework that aims to improve quality and developer satisfaction. It utilizes frequent small releases, customer collaboration, simple designs, testing automation, pair programming, and other practices. The core values of XP include communication, simplicity, feedback, courage, and respect. Some key practices are planning games, small releases, testing, refactoring, pair programming, on-site customers, and continuous integration. XP focuses on rapid feedback and continuous improvement through its values and lightweight practices.
No Code Past The MVP
With only ~0.5% of the world knowing to code, that shouldn’t limit you from building your own products. With the surge of no code tools like Airtable, Bubble, Zapier, Coda, Webflow, and more… the possibility of making a fully-functioning application is available to anyone with an internet connection. We're bringing in No Code expert and MakerPad founder, Ben Tossell, to show us how no code can be taken past the MVP.
Ciklum net sat12112011-vladimir gorshunov -scrum and kanban in action
Vladimir Gorshunov is a technical consultant and Agile coach with over 8 years of software development experience. He helps distributed teams implement efficient Agile practices like Scrum and Kanban to deliver business value on time and on target. While Scrum and Kanban each have their uses, Vladimir advocates using a hybrid approach that combines the two for projects with short timelines, limited resources, or other constraints that prevent strict adherence to a single methodology. He works with teams to visualize their workflow, limit work in progress, and continuously optimize processes.
Be agile: take back control over your work
When you have to manage tons of projects, several developers, challenging customers you need to re-think your organization.
Agile methodologies are the answer, but you also need tools to manage them.
Agile_SDLC_Node.js@Paypal_ppt
This document discusses Agile practices, software development lifecycles (SDLC), and the use of Node.js at PayPal. It outlines typical Agile processes like sprint planning, backlog grooming, pair programming, mob programming, and retrospectives. It also describes PayPal's SDLC pipeline and use of Git flow for source control. Finally, it summarizes how PayPal adopted Node.js in 2012 and has since open sourced frameworks like Kraken.js and tools like Nemo.js while growing a large community of Node.js developers.
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
Lær 3 agile metoder på en aften
Mangler du en pragmatisk introduktion til Scrum og Agile? Leder du efter startblokken for at komme i gang med agile projekter? Eller er dit behov essentiel viden om den agile proces, så du forstår hvad der forventes af dig?
På en aften vil du få løftet din forståelse af de tre mest udbredte agile metoder: Scrum, Kanban og XP. Du vil først få præsenteret de enkelte metoders bestanddele og hvordan de hænger sammen. Herefter skifter vi fokus til metodernes forskelle og kombinationsmuligheder. Afslutningsvis tager vi en diskussion om de udfordringer, der kan spænde ben for de agile tiltag.
Alt i alt vil du få et godt grundlag på din vej til at blive en dygtig agil praktiker.
DA 592 - Term Project Report - Berker Kozan Can Koklu
This document summarizes a data analytics project done by students for a Kaggle contest to perform demand prediction for Grupo Bimbo. Python and the XGBoost library were used to perform feature engineering, training, and predictions on a large dataset. The team achieved a top 17% score on the competition by optimizing hyperparameters and selecting important features. Challenges included analyzing a large dataset, which was overcome through data type reductions and cloud computing resources.
ITSM BKK #2: Business Simulation and Gamification for ITSM
Role of Business Simulation and Gamification for ITSM Adoption.
ITSM BKK is hosting monthly event in Bangkok about IT Service Management.
Scrum Bangalore 16th Meetup - March 5, 2016 - How to Kickstart a new Scrum Te...
Scrum Bangalore 16th Meetup - March 5, 2016 - How to Kickstart a new Scrum Team - Marudhamaran Gunasekaran - at Prowareness
More Related Content
Similar to Scrum_XP_18Nov16
Working in teams vs working individually
A comparison between the software development practices: invidual developers vs development teams. Presentation for IT students at Kaunas University of Technology in Lithuania
Journey with XP a case study in embedded domain by Pradeep Kumar NR
Journey with XP a case study in embedded domain @XP conference 2016 Through this presentation, Pradeep will share his learning experience and describe his journey with XP that has been part of his life since 2 yrs. This talk also unfolds some aspects of how to adopt XP in embedded space with multiple layers involved and when there is a dependency on hardware
Extreme programming
Extreme Programming is a methodology in an Agile way for developing quality software or change stakeholder's requirements quickly by putting more focus on coding rather than design and continuous collaboration with the customer.
Scrum In 15 Minutes
Scrum is an agile framework for managing product development that focuses on continuous delivery of working software in short cycles called sprints, typically two weeks or less. Scrum emphasizes self-organizing cross-functional teams and accountability, iterative development and progress transparency through regular inspection of working increments. Key Scrum practices include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives. Scrum can scale to large, complex projects through techniques like Scrum of Scrums.
Pair programming
Pair programming has benefits such as less bugs, better code quality, spreading knowledge across teams, and creating a learning environment through improved communication. Developers should pair when working on complex, critical, or new features, or when a team has a new member. Techniques like driver-navigator and ping-pong pairing help structure the process, with the driver writing code and the navigator providing guidance, reviews, and testing. Regularly switching roles and keeping an open dialogue are important for effective pairing.
"You Made a Game, Now What?" Week2 game production methods and realities
A presentation on production methods for game development, including overviews of iterative design, waterfall, agile, and scrum.
I don't do agile, i am agile (Barry O'Reilly)
1. The document discusses various agile frameworks like Scrum, XP, and Kanban and their associated practices.
2. It emphasizes that organizations should focus on using practices that suit their specific context rather than strictly adhering to a single framework.
3. The document advocates for a lean, adaptive approach to agile by continuously questioning practices, eliminating waste, and prioritizing delivering value over following prescriptive processes.
I don't do Agile, I AM Agile!
Too often in agile software development we tend to use methodologies and all their components simply because the rule book says so. Why not select the tool based on the context of the task your
trying to complete.
Anything that you use that does not lead towards a direct value add to the final product delivered is simply an overhead and waste.
This presentation covers discovering what
is the minimum amount of practices that are required to achieve the goal of delivering a product we desire - safely, quickly and successfully. Thus allowing us to start getting feedback and improving it.
How to Write a Winning Session Submission
This webcast is for DrupalCon sponsors on how to submit a session abstract that will resonate with the selection team.
Introduction to Agile, by J.D. Meier
A brief and visual introduction to the Agile.
Learn the Agile mindset and the big 3 (Extreme Programming, Scrum, and Kanban). Be able to whiteboard a simple view of how each one works to get things done and make things happen.
Extreme Programming 1st.pdf
Extreme Programming (XP) is an agile software development framework that aims to improve quality and developer satisfaction. It utilizes frequent small releases, customer collaboration, simple designs, testing automation, pair programming, and other practices. The core values of XP include communication, simplicity, feedback, courage, and respect. Some key practices are planning games, small releases, testing, refactoring, pair programming, on-site customers, and continuous integration. XP focuses on rapid feedback and continuous improvement through its values and lightweight practices.
No Code Past The MVP
With only ~0.5% of the world knowing to code, that shouldn’t limit you from building your own products. With the surge of no code tools like Airtable, Bubble, Zapier, Coda, Webflow, and more… the possibility of making a fully-functioning application is available to anyone with an internet connection. We're bringing in No Code expert and MakerPad founder, Ben Tossell, to show us how no code can be taken past the MVP.
Ciklum net sat12112011-vladimir gorshunov -scrum and kanban in action
Vladimir Gorshunov is a technical consultant and Agile coach with over 8 years of software development experience. He helps distributed teams implement efficient Agile practices like Scrum and Kanban to deliver business value on time and on target. While Scrum and Kanban each have their uses, Vladimir advocates using a hybrid approach that combines the two for projects with short timelines, limited resources, or other constraints that prevent strict adherence to a single methodology. He works with teams to visualize their workflow, limit work in progress, and continuously optimize processes.
Be agile: take back control over your work
When you have to manage tons of projects, several developers, challenging customers you need to re-think your organization.
Agile methodologies are the answer, but you also need tools to manage them.
Agile_SDLC_Node.js@Paypal_ppt
This document discusses Agile practices, software development lifecycles (SDLC), and the use of Node.js at PayPal. It outlines typical Agile processes like sprint planning, backlog grooming, pair programming, mob programming, and retrospectives. It also describes PayPal's SDLC pipeline and use of Git flow for source control. Finally, it summarizes how PayPal adopted Node.js in 2012 and has since open sourced frameworks like Kraken.js and tools like Nemo.js while growing a large community of Node.js developers.
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
Lær 3 agile metoder på en aften
Mangler du en pragmatisk introduktion til Scrum og Agile? Leder du efter startblokken for at komme i gang med agile projekter? Eller er dit behov essentiel viden om den agile proces, så du forstår hvad der forventes af dig?
På en aften vil du få løftet din forståelse af de tre mest udbredte agile metoder: Scrum, Kanban og XP. Du vil først få præsenteret de enkelte metoders bestanddele og hvordan de hænger sammen. Herefter skifter vi fokus til metodernes forskelle og kombinationsmuligheder. Afslutningsvis tager vi en diskussion om de udfordringer, der kan spænde ben for de agile tiltag.
Alt i alt vil du få et godt grundlag på din vej til at blive en dygtig agil praktiker.
DA 592 - Term Project Report - Berker Kozan Can Koklu
This document summarizes a data analytics project done by students for a Kaggle contest to perform demand prediction for Grupo Bimbo. Python and the XGBoost library were used to perform feature engineering, training, and predictions on a large dataset. The team achieved a top 17% score on the competition by optimizing hyperparameters and selecting important features. Challenges included analyzing a large dataset, which was overcome through data type reductions and cloud computing resources.
ITSM BKK #2: Business Simulation and Gamification for ITSM
Role of Business Simulation and Gamification for ITSM Adoption.
ITSM BKK is hosting monthly event in Bangkok about IT Service Management.
Scrum Bangalore 16th Meetup - March 5, 2016 - How to Kickstart a new Scrum Te...
Scrum Bangalore 16th Meetup - March 5, 2016 - How to Kickstart a new Scrum Team - Marudhamaran Gunasekaran - at Prowareness
Similar to Scrum_XP_18Nov16 (20)
Journey with XP a case study in embedded domain by Pradeep Kumar NR
Journey with XP a case study in embedded domain by Pradeep Kumar NR
"You Made a Game, Now What?" Week2 game production methods and realities
"You Made a Game, Now What?" Week2 game production methods and realities
Ciklum net sat12112011-vladimir gorshunov -scrum and kanban in action
Ciklum net sat12112011-vladimir gorshunov -scrum and kanban in action
DA 592 - Term Project Report - Berker Kozan Can Koklu
DA 592 - Term Project Report - Berker Kozan Can Koklu
ITSM BKK #2: Business Simulation and Gamification for ITSM
ITSM BKK #2: Business Simulation and Gamification for ITSM
Scrum Bangalore 16th Meetup - March 5, 2016 - How to Kickstart a new Scrum Te...
Scrum Bangalore 16th Meetup - March 5, 2016 - How to Kickstart a new Scrum Te...
Scrum_XP_18Nov16
- 1. Scrum & XP in Practice 18-Nov-16, Djiwandou Putro djiwandou.putro@len.co.id 11/18/2016 Djiwandou, 2016 - djiwandou.putro@len.co.id
- 2. Key Messages Scrum • Framework • Manage Mindset • Agile Manifesto • 2 shared tools, 3 roles, 4 meetings, 1 cycle XP (eXtreme Programming) • Practical level • Technical guidance • Agile Manifesto • 12 Process 11/18/2016 Djiwandou, 2016 - djiwandou.putro@len.co.id “A mature team sees ‘pair programming’ as a need” - Joshua Partogi, Scrum Coach-
- 3. 12 Process of XP 11/18/2016 Djiwandou, 2016 - djiwandou.putro@len.co.id 1. Planning Game 2. Small Release 3. System Metaphor 4. Simple Design 5. Testing 6. Refactoring 7. Pair Programming 8. Continuous Integration 9. Collective Ownership 10. On site Customer 11. 40-hour work week 12. Coding Standards
- 4. Pair Programming 11/18/2016 Djiwandou, 2016 - djiwandou.putro@len.co.id
- 5. Pair Programming exercise • Make a team of 2, choose your own role • Navigator • Driver • Choose one of the programming problems: • Mars Exploration - https://www.hackerrank.com/challenges/mars-exploration • Repeatable String - https://www.hackerrank.com/challenges/repeated-string 11/18/2016 Djiwandou, 2016 - djiwandou.putro@len.co.id • Present your analysis to the class
- 6. Thank you Tribute to: • Joshua Partogi – Manajemen Modern dengan Scrum • Putra Arri Sandhi - putra.sandhi15@imperial.ac.uk • Elko Sharhadi Eppasa - elko.s.eppasa@gmail.com References: • https://www.agilealliance.org • http://agilemethodology.org/ • http://agilemanifesto.org/ Image references: • Pixabay.com • http://anarsolutions.com/wp-content/uploads/2015/08/Pair-Programming.jpg • https://insights- images.thoughtworks.com/1020ways20pair20programming203_7a4eac1abfb725cdba521e485086d3ea.png 11/18/2016 Djiwandou, 2016 - djiwandou.putro@len.co.id