The Top 5 Build Process Mistakes
Bookmark :
- Not doing it for the right reasons--If the only reason you are changing your current process is to satisfy management, then you will fail. If you have not realized that you have a problem, then why are you changing? As any addict will say, unless you accept that you have a problem, you will never change.
- Not realizing you have a build process--It could be just a single step to prepare the design for production like emailing the template to the admin, or refreshing a database, but regardless of the number of steps, you still have a process. Once you look at it from that perspective, even the simplest process can be made easier, less error prone, or more auditable.
- Not simplifying far enough--Before you begin to automate a build process, make sure it still makes sense. Many times people have adopted a routine that was completely relevant in say an R5 environment, but is unnecessary with an R8 environment.
- Automating things that happen only once--Only automate processes that happen the exact same way every single time you do them.
- Not including everyone in the analysis--There are probably lots of steps that can be included in the build process that you as the developer or admin don’t do yourself. In order to make sure that you don’t miss out on a piece of the process, get everyone involved together and write down everything you do from start to finish.