Depending on its precision, a TIMESTAMP value may have fractional seconds. For literals, the precision is defined by the presence of a fractional part after seconds, as well as the number of digits in the fractional part. For columns, the precision is defined as an optional parameter after the name of the type in the column definition. For instance:
defines the column as a timestamp with nanosecond precision (9 digits after the decimal point). (As you have SQL Server background, you can compare this to the SQL Server
datetime2 type, which also has optional precision.)
For reference, see IBM Knowledge Center - Datetime values.
It looks likely that the column in question is defined differently between the development environment and production, the development definition being
TIMESTAMP(0) (no fractional seconds) and the production definition
TIMESTAMP(6) (or simply
TIMESTAMP, which means the same).
That explains why your developer never has to specify fractions of a second in the development environment – because the column's values cannot possibly have fractional seconds. At the same time, she may have to specify timestamps with a fractional part in the production environment because the column type there allows fractions of a second in the values and some timestamps apparently do have fractional parts.