Process
Getting started with Latitude 40 begins with a series of conversations. This helps us to learn what business challenges you are looking to solve and enables you to ask anything you'd like about our team and our development process. We gather as much information about your project as possible so we can create a comprehensive proposal document with the best responsible work/cost estimate. This gives you an idea of how long your custom software development project will take to complete and cost.
The written proposal clearly illustrates the project breakdown in detail to give you a full understanding of what we think will be involved including requirements, project management, testing, debugging, deployment, documentation and user training. When we move forward, you are the first and most important member of the team; therefore we hope that you actively participate from start to finish. Our analysts can learn as much as they can, but nobody will ever be an adequate replacement for your knowledge of your business and vision. To learn more about your involvement and why it’s so important, click here.
For software development methodology, we prefer to keep the process open and simple by employing an agile approach. This provides flexibility and keeps overhead to a minimum. Some of our customers, however; especially larger corporations, already have their own standards. In such cases, will learn about those standards and apply them to the best of our ability.
Our preferred methodology is called “Scrum” and calls for an iterative process that creates small and constant deliverables. We’ll break the whole project down into smaller components, each to be worked through its full development cycle, one at a time. Each cycle includes requirements, design, development, testing and delivery. You will be involved in the requirements portion of each and should also be testing each component once it’s been delivered. It’s very important for you to stay involved in this fashion so you can constantly see progress, spot functionality that we may have misunderstood, spot user interface design points that you want changed, evolve requirements or add some that you didn't think about before, etc. For a concise description of Scrum, check out http://agileatlas.org/atlas/scrum.
We’ll keep the master copy (as well as backups) of the source code during development and after the project is completed in case you want further modifications or enhancements. However, since you will own that code, we can also keep another copy synchronized in any location of your choice.
When the project is completed and deployed, we’ll be more than happy to continue to maintain it for you. We’ll keep ourselves available in case you have any issues or want to plan another release with new functionality.
The written proposal clearly illustrates the project breakdown in detail to give you a full understanding of what we think will be involved including requirements, project management, testing, debugging, deployment, documentation and user training. When we move forward, you are the first and most important member of the team; therefore we hope that you actively participate from start to finish. Our analysts can learn as much as they can, but nobody will ever be an adequate replacement for your knowledge of your business and vision. To learn more about your involvement and why it’s so important, click here.
For software development methodology, we prefer to keep the process open and simple by employing an agile approach. This provides flexibility and keeps overhead to a minimum. Some of our customers, however; especially larger corporations, already have their own standards. In such cases, will learn about those standards and apply them to the best of our ability.
Our preferred methodology is called “Scrum” and calls for an iterative process that creates small and constant deliverables. We’ll break the whole project down into smaller components, each to be worked through its full development cycle, one at a time. Each cycle includes requirements, design, development, testing and delivery. You will be involved in the requirements portion of each and should also be testing each component once it’s been delivered. It’s very important for you to stay involved in this fashion so you can constantly see progress, spot functionality that we may have misunderstood, spot user interface design points that you want changed, evolve requirements or add some that you didn't think about before, etc. For a concise description of Scrum, check out http://agileatlas.org/atlas/scrum.
We’ll keep the master copy (as well as backups) of the source code during development and after the project is completed in case you want further modifications or enhancements. However, since you will own that code, we can also keep another copy synchronized in any location of your choice.
When the project is completed and deployed, we’ll be more than happy to continue to maintain it for you. We’ll keep ourselves available in case you have any issues or want to plan another release with new functionality.
Declare your independence from packaged software
For too long, you’ve been told what type of software you need for your business. Isn’t it about time someone listened to what you actually want? Schedule a no-risk consultation with the Latitude 40 team today!
