jayrbolton · September 5, 2018 16:43
diff --git a/agile-notes.txt b/agile-notes.txt
 - ability to iterate on anything in late stages - being able to deploy small updates to a late-stage tool
  without bottlenecks. this requires a lot of technical things in place (ie. modularity,
  versioning, CI). Eg: how can we add (or remove) a feature from the SDK and deploy that new
  version to users within a week or two?
 - developers should work (and communicate) directly with users
 - don't prioritize process tools and let devs choose those tools
 - most of agile is not about process or ritual but about technical requirements such as modularity, versioning, CI, etc
 - make sure you can refactor internals without breaking the interface (eg. versioning and dependency management in apps)
 - don't add features to software until you find that you need them
 - define the product, not the project
	- ability to iterate on anything in late stages - being able to deploy small updates to a late-stage tool
	without bottlenecks. this requires a lot of technical things in place (ie. modularity,
	versioning, CI). Eg: how can we add (or remove) a feature from the SDK and deploy that new
	version to users within a week or two?
	- developers should work (and communicate) directly with users
	- don't prioritize process tools and let devs choose those tools
	- most of agile is not about process or ritual but about technical requirements such as modularity, versioning, CI, etc
	- make sure you can refactor internals without breaking the interface (eg. versioning and dependency management in apps)
	- don't add features to software until you find that you need them
	- define the product, not the project