Task Execution

Introduction

Software Development is hard, but it doesn’t need to be. If we follow the same basic pattern for all our project work and make sure we understand the details early on in the process, we can greatly reduce the friction of going from a vision of a new feature to functioning software.

Why?

One of the primary goals why Kevin Wolf started Software Logistics was to attempt to build an organization where software can be done right in a low stress environment. Stress when developing software comes from friction during the software development process. If software is delivered on time, exactly how the client wants it and without defects there would be very little friction. The project management process as documented here attempts to address those issues:

  • On Time Software Delivery

  • Functionality that meets or exceeds the user expectations

  • Deliverables that achieve the quality goals

Process and Goals

Software Logistics is a Software Company and thus the majority of the work we perform is Software Development tasks. With that in mind, our Task Execution frameworks is heavily focused on building software whether that be new features or changes to existing functionality.

The following are some of the reasons by we want to introduce some formality into our process:

  1. Make sure the client understands what they want to get done.

  2. Make sure we document our understanding of what the client needs.

  3. Providing reasonable scope of effort.

  4. Make sure the developer knows what needs to be built.

  5. Make sure that we have documented any test data or credentials that need to be used to build the software.

  6. Make sure we have a plan to verify the task has been completed.