Defining Your System Development Workflows

Many ways to build systems

Differing philosophies and incorporated methods lead to different ways to create a system.  Having simple documentation describing the steps you take when developing systems reduces confusion, saves time and keeps the whole team working together well.

Suitable scales

Each workflow has project scales where it is more suited and others where it is less suited.  For example: you may have a great workflow defined for developing that mobile application or the organization’s website but it might not payoff when developing that automated backup verification script that will take about a day to create.  By documenting when a workflow is to be used and when not, you keep your whole team on the same page.

One for each scale

Having a few workflows defined for differing scales of projects allows an organization to move forward quickly with everyone using the same process.  All you have to do when you have a new project is to estimate the time it will take, from there everyone will know which workflow to use.  It’s like corporate traveling guidelines many companies use: if less than 4 hours drive time, drive.  If over 4 hours drive time, fly.

Trev Peterson

I've been working in Communications and Technology since 1990. I've worn a lot of hats in that time, everything from Desktop Support to Custom Hardware Engineer (for a short stint) with lots of learning along the way. Some things to describe me would be:
-Believer in KISS (principle - Keep It Simple Stupid, not the band)
-Adventurous (love to push my comfort zone and try new things)
-Linux / FLOSS Fan
-Love the CLI, especially for remote support

Nothing beats working with people fired up about their projects. Passion is contagious ;)

Leave a Reply