Agile: Difference between revisions
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
<nowiki>https://www.youtube.com/watch?v=5izyN66PTxs</nowiki> | <nowiki>https://www.youtube.com/watch?v=5izyN66PTxs</nowiki> | ||
[[File:Agile Metro.png|thumb|Agile Metro Map]] | |||
=== Agile Manifesto === | === Agile Manifesto === | ||
| Line 52: | Line 53: | ||
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. | At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. | ||
https://www.agilealliance.org/wp-content/uploads/2018/11/Subway-Map-to-Agile-Practices.pdf | |||
=== SAFE === | === SAFE === | ||
| Line 57: | Line 60: | ||
=== Scrum === | === Scrum === | ||
https://www.scrum.org/resources/what-scrum-module | https://www.scrum.org/resources/what-scrum-module | ||
=== TPS Toyota === | |||
https://www.youtube.com/watch?v=mX7uIL-BBq0 | |||
=== Lean / Kaizen === | === Lean / Kaizen === | ||
| Line 75: | Line 81: | ||
Don’t maximize production, if there are defects down the line | Don’t maximize production, if there are defects down the line | ||
Revision as of 04:55, 17 August 2023
Henrik Kniberg, Spotify Engineneering Culture (1 and 2)
https://www.youtube.com/watch?v=4GK1NDTWbkY
Bloomberg
https://www.youtube.com/watch?v=F5vtCRFRAK0&feature=youtu.be&t=1m6s
Axosoft
https://www.youtube.com/watch?v=R8dYLbJiTUE&feature=youtu.be&t=25s
Development That Pays
https://www.youtube.com/watch?v=5izyN66PTxs
Agile Manifesto
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Agile Principles
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity--the art of maximizing the amount of work not done--is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
https://www.agilealliance.org/wp-content/uploads/2018/11/Subway-Map-to-Agile-Practices.pdf
SAFE
For Enterprise
Scrum
https://www.scrum.org/resources/what-scrum-module
TPS Toyota
https://www.youtube.com/watch?v=mX7uIL-BBq0
Lean / Kaizen
Pull your own work, restock what’s needed
Produce Just-in-time, reduce stock
Visualize Work (backlog, todo, in progress, done)
Identify bottlenecks
Limit Work in Progress
Continuous Improvement (Kaizen)
Stop the line, prevent defects
Don’t maximize production, if there are defects down the line