Concepts · draft 24 of 95, not in the published book · outline v1.0.0, 2018, frozen · 159 words · the 2018 file · read and review
Agile and Kanban
In 2018 this was an outline: a title and "Topics to cover and ideas". It was never in the published book, and it is shown exactly as it was left. The second edition fills it from the articles the map names.
Topics to cover and ideas
- history
- why it worked
-
agile manifesto
- https://www.agilealliance.org/agile101/the-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
- https://www.agilealliance.org/agile101/the-agile-manifesto/
-
- Not only working software , but also well-crafted software
- Not only responding to change , but also steadily adding value
- Not only individuals and interactions , but also a community of professionals
- Not only customer collaboration , but also productive partnerships
-
Anton cords
- explain concepts (with diagrams)
- how agile become dogma and created environments where agile teams where not agile at all
- processes become more important than understanding why something was being created in the first place, to much effort was put on estimates, to much focus was placed on what could be done in 2 weeks
-
Scrumbam is a nice alternative
Answered since, on the newsroom: The agent team as it runs. The map row.