Skip to end of metadata
Go to start of metadata
You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
Version 1
Current »
- Released 5.17.0 early
- Had a stand-up meeting every day
- Code reviews complete
- Reacted quickly to user feedback/provided patches quickly
- Everyone involved with user support
What should we have done better?
Actions
- if a mathematical calculation test fails due to change in code, do not change the test to match the code without discussing with the team first
- watch in code reviews to catch where unit test values are being modified and bring to team's attention
- be very careful when modifying payroll processing code
- do not refactor unless there is adequate tests prior to the change