Rounding / Exceptions are always an interesting topic. Everyone thinks they understand how to best implement/change the the practices, but seldom does anyone understand the full social impact (the technical side being quite simple.) These configurations in Kronos/eTime determine how people get paid and how attendance is tracked. Some basic terms need to be understood.
A key part of managing change is testing and quality assurance. This guest post was written by a dear friend of mine after finishing another arduous sprint on an Agile-run project. Here's to all our QA people out there who ensure we deliver quality Kronos projects!