Submit Search
Upload
Agile survival kit
•
1 like
•
2,785 views
Stefano Gallotti
Follow
Agile Survival kit A short description of main concepts referring to Agile Thinking
Read less
Read more
Technology
Report
Share
Report
Share
1 of 11
Recommended
Introduzione alle metodologie di sviluppo agile
Introduzione alle metodologie di sviluppo agile
Stefano Valle
Learn Scrum Engineering in 5 minutes
Learn Scrum Engineering in 5 minutes
guest035e0d
Scrum e a Crise Mundial
Scrum e a Crise Mundial
Marcos Garrido
Agile Executive Briefing - Situational Assessment + 50k Ft View
Agile Executive Briefing - Situational Assessment + 50k Ft View
Michael Sahota
Lean vs scrum
Lean vs scrum
Pavel Dabrytski
Agile Delivery Powerpoint Presentation Slides
Agile Delivery Powerpoint Presentation Slides
SlideTeam
Agile Estimating
Agile Estimating
Intelliware Development Inc.
Certified Scrum Product Owner Training
Certified Scrum Product Owner Training
guest74599
Recommended
Introduzione alle metodologie di sviluppo agile
Introduzione alle metodologie di sviluppo agile
Stefano Valle
Learn Scrum Engineering in 5 minutes
Learn Scrum Engineering in 5 minutes
guest035e0d
Scrum e a Crise Mundial
Scrum e a Crise Mundial
Marcos Garrido
Agile Executive Briefing - Situational Assessment + 50k Ft View
Agile Executive Briefing - Situational Assessment + 50k Ft View
Michael Sahota
Lean vs scrum
Lean vs scrum
Pavel Dabrytski
Agile Delivery Powerpoint Presentation Slides
Agile Delivery Powerpoint Presentation Slides
SlideTeam
Agile Estimating
Agile Estimating
Intelliware Development Inc.
Certified Scrum Product Owner Training
Certified Scrum Product Owner Training
guest74599
Flavours of agile software engineering
Flavours of agile software engineering
Zeeshan Masood S
Agile Development Brown Bag Lunches Slides
Agile Development Brown Bag Lunches Slides
guesta1c5d7
Going Agile With Helix ALM
Going Agile With Helix ALM
Perforce
10 differences between SAFe and LeSS
10 differences between SAFe and LeSS
Stanislaw Matczak
Agile product development
Agile product development
Scrum Asia Pasifik
What is agile
What is agile
Marco Trincardi
PMBOK and Scrum: Best of both worlds
PMBOK and Scrum: Best of both worlds
Silvana Wasitova, Scrum & Agile Coach
Scrum og kanban af Gitte Klitgaard Hansen, IBM
Scrum og kanban af Gitte Klitgaard Hansen, IBM
InfinIT - Innovationsnetværket for it
Starting out with Scrum
Starting out with Scrum
Joshua Partogi
Introduction to product development flow
Introduction to product development flow
Yuval Yeret
PMBoK and Scrum: can we be friends?
PMBoK and Scrum: can we be friends?
Silvana Wasitova, Scrum & Agile Coach
Scrum & Waterfall: Friend or Foe?
Scrum & Waterfall: Friend or Foe?
Silvana Wasitova, Scrum & Agile Coach
Understanding the Agile Release and Sprint Planning Process
Understanding the Agile Release and Sprint Planning Process
John Derrico
You think you know agile
You think you know agile
Nathan Gloyn
Journey of Agile
Journey of Agile
Tathagat Varma
Waterfall vs Agile : A Beginner's Guide in Project Management
Waterfall vs Agile : A Beginner's Guide in Project Management
Jonathan Donado
Agile Testing - Pruebas en Ágiles
Agile Testing - Pruebas en Ágiles
Valeria Vásquez
Scrum and agile principles
Scrum and agile principles
Ruben Canlas
Lean Software Development
Lean Software Development
Christopher Grant
Introduction to Agile Project Management and Scrum
Introduction to Agile Project Management and Scrum
Voximate
BAAgileQA
BAAgileQA
Digital leverage Consulting Services,Hyderabad
Agile_basics
Agile_basics
Mithilesh Singh
More Related Content
What's hot
Flavours of agile software engineering
Flavours of agile software engineering
Zeeshan Masood S
Agile Development Brown Bag Lunches Slides
Agile Development Brown Bag Lunches Slides
guesta1c5d7
Going Agile With Helix ALM
Going Agile With Helix ALM
Perforce
10 differences between SAFe and LeSS
10 differences between SAFe and LeSS
Stanislaw Matczak
Agile product development
Agile product development
Scrum Asia Pasifik
What is agile
What is agile
Marco Trincardi
PMBOK and Scrum: Best of both worlds
PMBOK and Scrum: Best of both worlds
Silvana Wasitova, Scrum & Agile Coach
Scrum og kanban af Gitte Klitgaard Hansen, IBM
Scrum og kanban af Gitte Klitgaard Hansen, IBM
InfinIT - Innovationsnetværket for it
Starting out with Scrum
Starting out with Scrum
Joshua Partogi
Introduction to product development flow
Introduction to product development flow
Yuval Yeret
PMBoK and Scrum: can we be friends?
PMBoK and Scrum: can we be friends?
Silvana Wasitova, Scrum & Agile Coach
Scrum & Waterfall: Friend or Foe?
Scrum & Waterfall: Friend or Foe?
Silvana Wasitova, Scrum & Agile Coach
Understanding the Agile Release and Sprint Planning Process
Understanding the Agile Release and Sprint Planning Process
John Derrico
You think you know agile
You think you know agile
Nathan Gloyn
Journey of Agile
Journey of Agile
Tathagat Varma
Waterfall vs Agile : A Beginner's Guide in Project Management
Waterfall vs Agile : A Beginner's Guide in Project Management
Jonathan Donado
Agile Testing - Pruebas en Ágiles
Agile Testing - Pruebas en Ágiles
Valeria Vásquez
Scrum and agile principles
Scrum and agile principles
Ruben Canlas
Lean Software Development
Lean Software Development
Christopher Grant
Introduction to Agile Project Management and Scrum
Introduction to Agile Project Management and Scrum
Voximate
What's hot
(20)
Flavours of agile software engineering
Flavours of agile software engineering
Agile Development Brown Bag Lunches Slides
Agile Development Brown Bag Lunches Slides
Going Agile With Helix ALM
Going Agile With Helix ALM
10 differences between SAFe and LeSS
10 differences between SAFe and LeSS
Agile product development
Agile product development
What is agile
What is agile
PMBOK and Scrum: Best of both worlds
PMBOK and Scrum: Best of both worlds
Scrum og kanban af Gitte Klitgaard Hansen, IBM
Scrum og kanban af Gitte Klitgaard Hansen, IBM
Starting out with Scrum
Starting out with Scrum
Introduction to product development flow
Introduction to product development flow
PMBoK and Scrum: can we be friends?
PMBoK and Scrum: can we be friends?
Scrum & Waterfall: Friend or Foe?
Scrum & Waterfall: Friend or Foe?
Understanding the Agile Release and Sprint Planning Process
Understanding the Agile Release and Sprint Planning Process
You think you know agile
You think you know agile
Journey of Agile
Journey of Agile
Waterfall vs Agile : A Beginner's Guide in Project Management
Waterfall vs Agile : A Beginner's Guide in Project Management
Agile Testing - Pruebas en Ágiles
Agile Testing - Pruebas en Ágiles
Scrum and agile principles
Scrum and agile principles
Lean Software Development
Lean Software Development
Introduction to Agile Project Management and Scrum
Introduction to Agile Project Management and Scrum
Similar to Agile survival kit
BAAgileQA
BAAgileQA
Digital leverage Consulting Services,Hyderabad
Agile_basics
Agile_basics
Mithilesh Singh
Introduction to Agile & scrum
Introduction to Agile & scrum
Elad Sofer
Advanced Web Development in PHP - Understanding Project Development Methodolo...
Advanced Web Development in PHP - Understanding Project Development Methodolo...
Rasan Samarasinghe
Agile Software Development with Scrum_ A Complete Guide to The Steps in Agile...
Agile Software Development with Scrum_ A Complete Guide to The Steps in Agile...
Fibonalabs
ME135A Agile lean workshop101414
ME135A Agile lean workshop101414
spikol
Agile.docx
Agile.docx
ssusere4c6aa
CampusSDN2017 - Jawdat: Product Management and Agile Development
CampusSDN2017 - Jawdat: Product Management and Agile Development
JawdatTI
Agile & SCRUM basics
Agile & SCRUM basics
Arun R
Agile, not just for software
Agile, not just for software
John Paz
The Importance of Agile Methodology in Software Development
The Importance of Agile Methodology in Software Development
ultroNeous Technologies
Agile Overview
Agile Overview
Stephen Albright
Ag02 agile practices - dnc14 handouts
Ag02 agile practices - dnc14 handouts
DotNetCampus
Agile intro resources
Agile intro resources
Anwar Sadat
Scrum with Asana
Scrum with Asana
James G. Boram Kim
Agile Software Development
Agile Software Development
Tathagat Varma
Agile Project Management
Agile Project Management
Giampiero Bonifazi
Scrumhub scrum-guide-2016
Scrumhub scrum-guide-2016
Veeresh Yadrami
Reading Summary - Software Agile Development + Scrum
Reading Summary - Software Agile Development + Scrum
Artemisa Yescas Engler
Venkatraman l
Venkatraman l
PMI2011
Similar to Agile survival kit
(20)
BAAgileQA
BAAgileQA
Agile_basics
Agile_basics
Introduction to Agile & scrum
Introduction to Agile & scrum
Advanced Web Development in PHP - Understanding Project Development Methodolo...
Advanced Web Development in PHP - Understanding Project Development Methodolo...
Agile Software Development with Scrum_ A Complete Guide to The Steps in Agile...
Agile Software Development with Scrum_ A Complete Guide to The Steps in Agile...
ME135A Agile lean workshop101414
ME135A Agile lean workshop101414
Agile.docx
Agile.docx
CampusSDN2017 - Jawdat: Product Management and Agile Development
CampusSDN2017 - Jawdat: Product Management and Agile Development
Agile & SCRUM basics
Agile & SCRUM basics
Agile, not just for software
Agile, not just for software
The Importance of Agile Methodology in Software Development
The Importance of Agile Methodology in Software Development
Agile Overview
Agile Overview
Ag02 agile practices - dnc14 handouts
Ag02 agile practices - dnc14 handouts
Agile intro resources
Agile intro resources
Scrum with Asana
Scrum with Asana
Agile Software Development
Agile Software Development
Agile Project Management
Agile Project Management
Scrumhub scrum-guide-2016
Scrumhub scrum-guide-2016
Reading Summary - Software Agile Development + Scrum
Reading Summary - Software Agile Development + Scrum
Venkatraman l
Venkatraman l
Recently uploaded
Data governance with Unity Catalog Presentation
Data governance with Unity Catalog Presentation
Knoldus Inc.
Bridging Between CAD & GIS: 6 Ways to Automate Your Data Integration
Bridging Between CAD & GIS: 6 Ways to Automate Your Data Integration
marketing932765
How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.
Curtis Poe
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
LoriGlavin3
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
LoriGlavin3
The Future Roadmap for the Composable Data Stack - Wes McKinney - Data Counci...
The Future Roadmap for the Composable Data Stack - Wes McKinney - Data Counci...
Wes McKinney
A Journey Into the Emotions of Software Developers
A Journey Into the Emotions of Software Developers
Nicole Novielli
UiPath Community: Communication Mining from Zero to Hero
UiPath Community: Communication Mining from Zero to Hero
UiPathCommunity
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
LoriGlavin3
Genislab builds better products and faster go-to-market with Lean project man...
Genislab builds better products and faster go-to-market with Lean project man...
Farhan Tariq
Testing tools and AI - ideas what to try with some tool examples
Testing tools and AI - ideas what to try with some tool examples
Kari Kakkonen
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
Nikki Chapple
So einfach geht modernes Roaming fuer Notes und Nomad.pdf
So einfach geht modernes Roaming fuer Notes und Nomad.pdf
panagenda
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
Mark Goldstein
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
itnewsafrica
Emixa Mendix Meetup 11 April 2024 about Mendix Native development
Emixa Mendix Meetup 11 April 2024 about Mendix Native development
Pim van der Noll
Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024
Hiroshi SHIBATA
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
LoriGlavin3
TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024
Lonnie McRorey
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
Inflectra
Recently uploaded
(20)
Data governance with Unity Catalog Presentation
Data governance with Unity Catalog Presentation
Bridging Between CAD & GIS: 6 Ways to Automate Your Data Integration
Bridging Between CAD & GIS: 6 Ways to Automate Your Data Integration
How AI, OpenAI, and ChatGPT impact business and software.
How AI, OpenAI, and ChatGPT impact business and software.
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Role of FIDO in a Cyber Secure Netherlands: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Fit for Passkeys for Employee and Consumer Sign-ins: FIDO Paris Seminar.pptx
The Future Roadmap for the Composable Data Stack - Wes McKinney - Data Counci...
The Future Roadmap for the Composable Data Stack - Wes McKinney - Data Counci...
A Journey Into the Emotions of Software Developers
A Journey Into the Emotions of Software Developers
UiPath Community: Communication Mining from Zero to Hero
UiPath Community: Communication Mining from Zero to Hero
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
Digital Identity is Under Attack: FIDO Paris Seminar.pptx
Genislab builds better products and faster go-to-market with Lean project man...
Genislab builds better products and faster go-to-market with Lean project man...
Testing tools and AI - ideas what to try with some tool examples
Testing tools and AI - ideas what to try with some tool examples
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
Microsoft 365 Copilot: How to boost your productivity with AI – Part one: Ado...
So einfach geht modernes Roaming fuer Notes und Nomad.pdf
So einfach geht modernes Roaming fuer Notes und Nomad.pdf
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
Emixa Mendix Meetup 11 April 2024 about Mendix Native development
Emixa Mendix Meetup 11 April 2024 about Mendix Native development
Long journey of Ruby standard library at RubyConf AU 2024
Long journey of Ruby standard library at RubyConf AU 2024
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
Merck Moving Beyond Passwords: FIDO Paris Seminar.pptx
TeamStation AI System Report LATAM IT Salaries 2024
TeamStation AI System Report LATAM IT Salaries 2024
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
[Webinar] SpiraTest - Setting New Standards in Quality Assurance
Agile survival kit
1.
1 Agile Survival Kit Gallotti
Stefano © - http://www.galoz.it
2.
Stiamo scoprendo modi
migliori di creare software, sviluppandolo e aiutando gli altri a fare lo stesso. Grazie a questa attività siamo arrivati a considerare importanti: Gli individui e le interazioni più che i processi e gli strumenti Il software funzionante più che la documentazione esaustiva La collaborazione col cliente più che la negoziazione dei contratti Rispondere al cambiamento più che seguire un piano 2 Manifesto per lo Sviluppo Agile di Software Ovvero, fermo restando il valore delle voci a destra,consideriamo più importanti le voci a sinistra. I principi sottostanti al Manifesto Agile • La nostra massima priorità è soddisfare il cliente rilasciando software di valore, fin da subito e in maniera continua. • Accogliamo i cambiamenti nei requisiti, anche a stadi avanzati dello sviluppo. I processi agili sfruttano il cambiamento a favore del vantaggio competitivo del cliente. • Consegniamo frequentemente software funzionante, con cadenza variabile da un paio di settimane a un paio di mesi, preferendo i periodi brevi. • Committenti e sviluppatori devono lavorare insieme quotidianamente per tutta la durata del progetto. • Fondiamo i progetti su individui motivati. Diamo loro l'ambiente e il supporto di cui hanno bisogno e confidiamo nella loro capacità di portare il lavoro a termine. • Una conversazione faccia a faccia è il modo più efficiente e più efficace per comunicare con il team ed all'interno del team. • Il software funzionante è il principale metro di misura di progresso. • I processi agili promuovono uno sviluppo sostenibile. Gli sponsor, gli sviluppatori e gli utenti dovrebbero essere in grado di mantenere indefinitamente un ritmo costante. • La continua attenzione all'eccellenza tecnica e alla buona progettazione esaltano l'agilità. • La semplicità - l'arte di ottimizzare la quantità di lavoro non svolto - è essenziale. • Le architetture, i requisiti e la progettazione migliori emergono da team che si auto-organizzano. • A intervalli regolari il team riflette su come diventare più efficace, dopodiché regola e adatta il proprio comportamento di conseguenza. http://agilemanifesto.org/ Gallotti Stefano © - http://www.galoz.it
3.
3 The Scrum Framework
in 30 seconds • A product owner creates a prioritized wish list called a product backlog. • During sprint planning, the team pulls a small chunk from the top of that wishlist, a sprint backlog, and decides how to implement those pieces. • The team has a certain amount of time, a sprint, to complete its work - usually two to four weeks - but meets each day to assess its progress (daily scrum). • Along the way, the ScrumMaster keeps the team focused on its goal. • At the end of the sprint, the work should be potentially shippable, as in ready to hand to a customer, put on a store shelf, or show to a stakeholder. • The sprint ends with a sprint review and retrospective. • As the next sprint begins, the team chooses another chunk of the product backlog and begins working again. Gallotti Stefano © - http://www.galoz.it
4.
4 Scrum terminology We've introduced
some new terms in describing the Scrum framework. Let's look at them in more detail. Scrum is made up of three roles, four ceremonies, and three artifacts. Three roles Product owner: responsible for the business value of the project ScrumMaster: ensures that the team is functional and productive Team: self-organizes to get the work done Four ceremonies Sprint planning: the team meets with the product owner to choose a set of work to deliver during a sprint Daily scrum: the team meets each day to share struggles and progress Sprint reviews: the team demonstrates to the product owner what it has completed during the sprint Sprint retrospectives: the team looks for ways to improve the product and the process. Three artifacts Product backlog: ordered list of ideas for the product Sprint backlog: set of work from the product backlog that the team agrees to complete in a sprint, broken into tasks Product Increment: required result of every sprint. It is an integrated version of the product, kept at high enough quality to be shippable. Gallotti Stefano © - http://www.galoz.it
5.
5 What is Kanban Kanban
is a new technique for managing a software development process in a highly efficient way. Kanban underpins Toyota's "just-in- time" (JIT) production system. Although producing software is a creative activity and therefore different to mass-producing cars, the underlying mechanism for managing the production line can still be applied. A software development process can be thought of as a pipeline with feature requests entering one end and improved software emerging from the other end. Inside the pipeline, there will be some kind of process which could range from an informal ad hoc process to a highly formal phased process. We assume a simple phased process of: (1) analyze the requirements, (2) develop the code (3) test it works. The Effect of Bottlenecks A bottleneck in a pipeline restricts flow. The throughput of the pipeline as a whole is limited to the throughput of the bottleneck. Using development pipeline as an example: if the testers are only able to test 5 features per week whereas the developers and analysts have the capacity to produce 10 features per week, the throughput of the pipeline as a whole will only be 5 features per week because the testers are acting as a bottleneck. If the analysts and developers aren't aware that the testers are the bottleneck, then a backlog of work will begin to pile up in front of the testers. The effect is that lead times go up. And, like warehouse stock, work sitting in the pipeline ties up investment, creates distance from the market, and drops in value as time goes by. Inevitably, quality suffers. To keep up, the testers start to cut corners. The resulting bugs released into production cause problems for the users and waste future pipeline capacity. If, on the other hand, we knew where the bottleneck was, we could redeploy resources to help relieve it. For example, the analysts could help with testing and the developers could work on test automation. But how do we know where the bottleneck is in any given process? And what happens when it moves? Gallotti Stefano © - http://www.galoz.it
6.
6 Kanban Example Kanban reveals
bottlenecks dynamically Kanban is incredibly simple, but at the same time incredibly powerful. A kanban system consists of a big board on the wall with cards or sticky notes placed in columns with numbers at the top. The cards represent work items as they flow through the development process represented by the columns. The numbers at the top of each column are limits on the number of cards allowed in each column. The limits are the critical difference between a kanban board and any other visual storyboard. Limiting the amount of work-in-progress (WIP), at each step in the process, prevents overproduction and reveals bottlenecks dynamically so that you can address them before they get out of hand. The board shows a situation where the developers and analysts are being prevented from taking on any more work until the testers free up a slot and pull in the next work item. At this point the developers and analysts should be looking at ways they can help relieve the burden on the testers. We’ve split some of the columns in two, to indicate items being worked on and those finished and ready to be pulled by the downstream process. There are several different ways you can layout out the board. This is a fairly simple way. The limits at the top of the split columns cover both the "doing" and "done" columns. Once the testers have finished testing a feature, they move the card and free up a slot in the "Test" column Now the empty slot in the "Test" column can be filled by one of the cards in the development "done" column. That frees up a slot under "Development" and the next card can be pulled from the "Analysis" column and so on. Gallotti Stefano © - http://www.galoz.it
7.
7 What move us
to think about something else… The model most frequently applied in project management is called Waterfall (composed of 6 steps) 1. Description (vague and rough) of project requirements 2. Evaluation and estimation of effort and resources required 3. MONETARY OFFER TO THE CUSTOMER (often "out of the box", all inclusive and without variations possible) 4. Functional analysis (where you begin to understand what was wrong in step 2) 5. Architectural analysis (where the doubts of phase 4 become certainty) 6. Development & Test (where the disaster assumes irreparable proportions) If for a moment we make the assumption of being able to do without the “Estimation", we can imagine a process of Project Costing & Estimation effective and, above all, beneficial for all parties (win-win). This process is an iterative process that takes place within a "sprint" of time. Gallotti Stefano © - http://www.galoz.it
8.
8 Move to Sprints Gallotti
Stefano © - http://www.galoz.it
9.
9 Grooming A well-groomed product
backlog facilitates the development of a successful product: It incorporates the team’s learning, and provides items that are ready to be implemented. But when should grooming take place? Option 1: Grooming Takes Place before New Development Starts Groom the product backlog before any new development work starts. This includes obtaining feedback from users and customers, analysing it, integrating the learning into the backlog, and getting the product backlog ready. Option 2: Grooming Takes Place after New Development has Started Continue the development work while you are collecting and analysing the user feedback. Choose this option if you do not require the user data to continue developing your product, doing more coding without having first analysed the user feedback does not imply a significant risk of taking your product in the wrong direction.. Gallotti Stefano © - http://www.galoz.it
10.
10 Curve your Enthusiasm Gallotti
Stefano © - http://www.galoz.it
11.
11 Let’s start to
do it Gallotti Stefano © - http://www.galoz.it