Hands-On Continuous Integration and Delivery

Lack of proper documentation

The documentation needs to be written at the very moment that any requirements are defined and must be updated with additional information continuously while the feature is being worked on. It is only when everything is defined and stated as clearly as possible that you can start writing a plan to implement a specific feature. If a developer encounters an issue and requires clarification from a customer, then the answer needs to be put directly in the requirements for future reference.

Avoid having multiple documents with requirements information, but instead have one document with the requirements information, or else you risk having out-of-date information; or worse, having different requirements scattered in ...