Processes
Kindred Operations generally employs either an Agile or Waterfall process methodology. We can also work within your internal process if desired. The methodology used is determined by the nature and type of project and then tweaked based on the way you want the project handled.
Waterfall
Waterfall
Agile
The preferred method for most projects is the Agile process. This gives you the most flexibility with your project. It allows for situations where there are many unknowns or loosely defined requirements and the Agile process invites changes. In an Agile environment, constant communication is the key to success. Nearly every aspect of the process involves collaboration to make sure we are working on what you need.
It involves a brief design phase to get an idea of the scope of your project. Your requirements are reviewed and become descriptions of features or functionality called user stories. The user stories at this point are loosely defined with the details to be filled out during the development phase. Once the design is complete, it moves on into an iterative development phase.
In this phase, each iteration is called a “sprint” and lasts for 2 to 4 weeks, with 2 weeks being the most common. Within each sprint various user stories are detailed and worked on. Each user story goes through mini-design, development, and testing phases of its own. At the end of the sprint the work completed is shown to you for feedback, and released to you so that you can use it for any additional testing or validation. Feedback received can then be turned into additional user stories and scheduled for work in a future sprint. New features and functionality can be added and turned into user stories at any point, and user stories that have not been completed yet can be removed if they are no longer needed or wanted. The sprints continue until you say the development is done.
Once you say the development is done the project moves into the deployment phase. What tasks are done in the deployment phase is largely driven by your needs, and agreed upon deliverables. Typically, this includes things like additional “as built” documentation, final installers and final validation.
We offer a waterfall process if you want it. It is not recommended due to the inflexible nature of the process, and it is often the most expensive. Nearly every aspect of the process must be specified in the beginning. It is only suitable if you know exactly how the software should behave.
In the waterfall process the design phase is long and detailed. It begins with a review of your requirements, and then we take those requirements and derive them into technical and more detailed requirements for you to approve. Every requirement must be specified and detailed so there is no ambiguity. If something is not specified, then it is not required. If there are multiple interpretations of a requirement, then all interpretations are valid when it comes to acceptance. Extreme care must be taken to ensure the requirements are correct. Then a series of detailed software design documents are written covering the entire software solution, including any hardware or additional software interfaces. These documents are then sent to you for approval. Once approved the requirements and design are set and cannot be changed easily. Any addition, removal, or change must go through a change request process, and agreed upon.
After all the requirements and the design documents are approved development begins. It is broken down into two sub phases, code writing and code testing. The code writing portion of the phase begins when the design is complete, and the testing is done when the code writing is complete. Once the code writing and testing is done it is submitted for you to check that all specified requirements have been met.
Once the requirements have been met, the deployment phase begins. This is where the agreed upon deliverables are provided.
Your Own Process
Your Own Process
You know your process. In cases where you already have a process that works for you, be it agile, waterfall, v-model, something else, or a combination of those, we can work within your existing process to produce the solution you need.
Pricing Models
Time and Materials Projects
Fixed Price Projects
In a time and materials project, you pay for the hours worked on your project and you supply, or provide access to, hardware or other materials beyond what is considered normal for a software project.
For example, if your project requires interfacing with an ACME Widget2000, you would need to supply us with, or provide access to, an ACME Widget2000.
A fixed price project is one where the price for work is agreed upon up front. It is often more expensive than a cost and materials project since estimated risks are included in the total cost.
We only offer this pricing model for Waterfall process projects. For those projects, only the development and deployment are fixed price. The design phase is often time and materials.