Few more tweaks

Author: ChrisBeeley

presentations/2025-12-04_whose_application/index.qmd

@@ -37,8 +37,8 @@ format:
 * We did everything we were supposed to and people were happy with the model. But there were issues
 * User feedback and prioritisation of developments were ad-hoc
 * Programmes of work were siloed 
-* Crucially, the needs of different bugfixes and improvements were considered in isolation
-* The connection between different deliverables was poorly understood, leading to delays and missed opportunities
+* The needs of different bugfixes and improvements were considered in isolation
+* The connection between different deliverables was poorly understood
 
 ## Where next?
 
@@ -98,10 +98,29 @@ format:
 * People work better with clear roles and clear responsibilities
 * Build a group of people who know why and a group who know how
 
-## In practice
+## What is agile
+
+* Customers talk waterfall but behave agile
+* My 2022 agile definition:
+  * Customers can't make up their minds
+  * It's hard to design software all at once
+  * Continuous delivery keeps customers happy
+
+## Some highlights from [The agile manifesto](https://agilemanifesto.org/)
+
+* "Welcome changing requirements, even late in development"
+* "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly"
+* "Continuous attention to technical excellence and good design enhances agility"
+* "Simplicity- the art of maximizing the amount of work not done- is essential"
+
+## How agile helps
+
+* Those shaping the project wanted to be able to make quick changes- and see the long term plan
+* Agility is a mindset, a mode of practice
+* Being agile is all about being able to review and make decisions frequently
+* But it isn't about changing what you're doing all the time
+* Good code and good teams are ready to change direction- whether they change or not
 
-* Agile rituals as cargo cult
-* Product