Laminar leverages our Software Development Life Cycle Methodology to customize a delivery process that best suits each of our clients. This approach helps to ensure that our development process will meet client business needs and goals.

• A Project Kick-Off meeting is held to introduce all stakeholders, manage expectations, and review roles and responsibilities.
• Business Requirements are gathered and documented including project risks and mitigation plans.
• Business Requirements Review Meeting and Sign Off held.
• A level of effort is compiled after the Business Requirements have been reviewed and accepted to create accurate project and milestone schedules.
• A Communications Plan is established to ensure all stakeholders, project team members, and end users are appropriately informed.
• Weekly Project Status Reports will be submitted to you communicating the team’s continual progress. Schedule information, identified issues and risks, testing summary statistics and next steps will be noted to keep you informed throughout the software development life cycle.
• A Weekly Status Meeting is scheduled going forward. This meeting provides all attendees with the opportunity to discuss their progress, and address questions, concerns, or technical issues as they arise.

• A Technical Design Document (TDD) is drafted
• A Technical Design Document Review Meeting is held to ensure all project team members and stakeholders understand and approve of the design and architecture of the technical solution.
• Developers create and/or gain access to development and test environments.
• The technical solution is developed, code reviewed, and unit tested.

The Quality Assurance Process includes thorough requirements review and sign off, test planning, test case creation and execution, efficient defect tracking management, user acceptance test (UAT) support, and detailed testing metrics guaranteeing that a high quality product is delivered to your organization.  Depending on the technical solution implemented certain testing phases will be required to ensure quality.  The following test phases are an example of the testing Laminar provides: 

• Integration Test – The primary purpose of integration test will be to validate the individual software modules are combined and tested as a group.  This may also include the process/download of data from disparate databases or systems.

• System Test – Test cases written are based off the Business Requirements (BRD)/Functional Specification Document (FSD) will be executed to validate compliance of the delivered code with the specified requirements.  The primary purpose is to seek out defects and ensure the system delivered meets the agreed upon requirements.  In addition to validating requirements the following testing methods will be employed; Usability Testing to evaluate ease of use of new screen designs, and how much time and number of steps are required to complete a task. Performance Test to ensure the system’s response time to retrieve, update and save data is reasonable.

• User Acceptance Test – Commonly referred to as UAT, once the system is complete the Business users will be trained on the new system and be asked to execute common day-to-day business transactions.  The primary goal of UAT is to confirm the system is delivered according to the requirements and the solution provided meets the business needs.

• Beta Test – To minimize impact to the business, and gain valuable feedback of usability and performance, the system can be deployed to a subset of your organization.  Laminar will provide necessary end user training and support during Beta Test.  The primary goal of beta test is to help ensure the completed system will be successfully adopted by the end users.

Upon completion, the Laminar QA Team will work with your QA Team in a knowledge transfer so that your organization is prepared for future production support needs.  To assist in that, the following QA deliverables are provided; Overall Test Strategy and Approach, Test Plan, Test Cases, Summary of Defects Logged.

• A detailed Deployment Plan is created to ensure that the roll out of the application/system is professional and efficient with little to no downtime for existing systems and business operations.
• A Pre-Deployment Planning Meeting is held to review the plan to confirm the approach, validate deployment steps, and address and resolve any questions and/or concerns.
• The application/system is deployed to production and post-launch verification is completed.
• The application/system Reference Guide and training materials are completed.

• End users are trained on the functionality and the benefits of the new application/system.
• Technical solution and maintenance responsibilities are transferred from the Laminar project team to your technical staff.

• All project deliverables and artifacts are submitted to your organization for reference.
• A “Lessons Learned” meeting is held to review the success of the project and the results of the meeting are published for future reference.