Agile development and database changes

For those agile practitioners out there...

How do you manage changes to a database schema during a project? My assumption is that in an agile project the schema of any database involved will change and be refactored just as happens with the codebase.

Is this assumption correct? If so, do you have any particular tools or processes that you use to help keep things running smoothly?

Solution

AgileData.org is an excellent resource -- much more than I cram into a single response -- on Agile Database development. In particular, you might be interested in Agile Data Best Practices. If you use SQL Server, you might also be interested in SQL Compare from Red Gate software. Our DBAs have used it to help me migrate changes from QA to Production for existing applications.

How should international geographical addresses be stored in a relational database?
database - flattened out vs. normalized
Ensure uniqueness in join table with start/end dates
Does a SELECT query always return rows in the same order? Table with clustered index
Reuse Entity in Entity Framework Core
How to reduce the required storage space for large indexes and large PostgreSQL tables to improve and ensure performance?
Is better use an empty value as a '' or as NULL?
"Dynamic" tables in SQL?
How to programmatically check if row is deletable?
How does PostgreSQL enforce the UNIQUE constraint / what type of index does it use?
How do I structure data common to all users in Cloud Firestore?
Table constraint for range and null values
Calculating and saving space in PostgreSQL
How would you set up a database to handle comments for a blogging site?
How do multi user applications use databases?
Why is read repair not sufficient in making dynamo-style database linearizable?
Get table and column "owning" a sequence
Can you define a foreign key in a table from which the table with the primary key is derived?
How entity framework works for large number of records?
Do pizza toppings exist on their own in 3NF or does the column 'toppings' fail 2NF because it does rely on the pizza in practical reality?
How to generate a diagram of a very large database schema (SQL Server)
Custom cascade delete stored procedure for temporal tables in SQL Server
Database Management: Where to store old data outside the database
Saving barcode number in database that is generated with the logic
Generalizing work orders database table design
Removing a table without a unique index / constraint
Dropping column in Postgres on a large dataset
Cannot add or change a record because a related record is required in table 'COMPANY'
Consolidating tables with one-to-one relationships
How do I relate requesters of different type?