Common use of Full Project Clause in Contracts

Full Project. In a full project we use what we call the ImageSoft Way. It is described below: ImageSoft can utilize Agile or Waterfall methodologies to design and deploy solutions, but we commonly use a combination of both. Our process, the “ImageSoft Way”, uses the traditional waterfall approach for Project Planning, Initiation, Business Analysis, and Design, but employs an agile approach during the Build and Unit Testing phases. Once the development is complete, the waterfall approach is used again for System Testing, Customer Training, User Acceptance Testing, and Go-Live process phases. The degree to which the Agile methodology is used will be determined based on the details of the project and Fort Bend’s comfort level with agile. ImageSoft also utilizes Use Cases to define the functionality of the solution. During the Business Analysis and Design phase, ImageSoft will create a Solution Requirements Document (SRD) that identifies the requirements of the solution in the form of Use Cases. These Use Cases are converted to Test Cases and are utilized during the System Testing and User Acceptance Testing phases of the project. ImageSoft Way Project Implementation With this hybrid Agile/Waterfall approach, the “ImageSoft Way” provides customers inclusive insight into their solutions as they are being developed on time and within scope by using an iterative mode of development, demonstration, and feedback cycles. The ImageSoft Way relies on traditional project phases but uses an iterative feedback cycle during the build phase which allows ImageSoft to demonstrate the solution to the customer, receive immediate feedback, and make adjustments to the solution. In turn, the customer doesn’t wait until the start of their testing period to see their solution for the first time; they can collaborate through the entire build process. This results in business requirements being clarified, missed requirements being identified, and ensures the best solution for the customer is delivered. The first phase is our Planning and Initiation phase. This phase allows the team to learn about the project and the solution, first by meeting with the Sales team and then with the customer. Any documentation provided to the Sales team is shared with the Project team to ensure an efficient transfer of knowledge. During this phase, the Project Manager builds an initial draft of the project schedule so the customer will know what to expect. The project kickoff meeting is scheduled and conducted and discovery is scheduled. Our second phase, Business Analysis and Design, is often called discovery. We send two experienced team members, usually the Solution Architect and a Systems Engineer, to your location to sit with the users and walk through their business process. We listen, document, and ask questions. We do not build out the solution during this time; we ensure we understand your business, your pain points, and have the right information to build you a solution that will work. When we return to our office, we design your solution. In order to ensure we understand your business rules, we draft a document called the Solutions Requirement Document (SRD). In this document, we write Use Cases to identify the steps required to complete your business process within the new solution. Once internally vetted and reviewed, we send you this draft and schedule a review with you and your business Subject Matter Experts. We review the document live with you, making corrections to the process to ensure all parties agree on what the solution will include. The Business Analysis and Design phase completes once the Solution Requirements Document is signed. With the design agreed to, the Build phase begin. While we collaborate consistently through the entire project, the Build phase is the most iterative in terms of solution reviews and feedback loops. We will establish a regular cadence with you to demonstrate the solution as it is being built. Your feedback is critical in this phase. If we can catch a misunderstanding early in the project, we can update the design and estimate early to avoid overages later in the project. Seeing the solution often also helps your users and IT team understand the solution well before it is released to test and support. Before we release a solution for user testing, we perform system testing within ImageSoft to ensure everything works as designed within the Solution Requirements Document. After this is complete, we train your users to test the solution. We provide and consult on a sample training plan that you can customize for your team, as well as provide training manuals for your solution. We follow a checklist of steps that include other templates and documents that we share with your team to make sure training is successful. Trained users are happy users. During the User Acceptance Testing (UAT) phase, we setup an issue tracking software, Jira, just for you to log your issues or enhancements. We meet with your team multiple times aweek to review the issues, work with you to prioritize, resolve, and release for retest. At the end of UAT, we send you a signoff form to permit the solution to be promoted to Production. The last phase is the Production Migration and Go Live. While it seems like we are at the end of the project lifecycle, this is a critical phase and we treat it as such. Our team will collaborate with your IT staff well in advance of migration day to review the infrastructure, apply all licenses, and prep the environment. We build a migration checklist with your IT team with tasks, assignees, and dates to make sure nothing gets missed. We are available outside of business hours so that there can be as little impact as possible to your end users. The project team is allocated post go live to provide the continued support of your solution in Production for up to 30 days. After that 30 days is up, the project team completes a checklist for our Customer Care team that evaluates whether the solution is ready to be transitioned. The Customer Care team has product and development experts available for quick issue resolution and will escalate back to the project team to expedite the resolution of issues for you. Through all phases, you will have a dedicated Project Manager working to ensure your project stays on track. Whether tracking budget, challenging design decisions that compromise scope, removing roadblocks to allow the project team to meet dates, the Project Manager is your project advocate. They also provide you status reports, identify and mitigate risks, and maintain the project plan. Regardless of which team is working on your solution, the ImageSoft Way is to be collaborative, open to feedback, and quick to respond.

Full Project. In a full project we use what we call the ImageSoft Way. It is described below: ImageSoft can utilize Agile or Waterfall methodologies to design and deploy solutions, but we commonly use a combination of both. Our process, the “ImageSoft Way”, uses the traditional waterfall approach for Project Planning, Initiation, Business Analysis, and Design, but employs an agile approach during the Build and Unit Testing phases. Once the development is complete, the waterfall approach is used again for System Testing, Customer Training, User Acceptance Testing, and Go-Live process phases. The degree to which the Agile methodology is used will be determined based on the details of the project and Fort Bend’s comfort level with agile. ImageSoft also utilizes Use Cases to define the functionality of the solution. During the Business Analysis and Design phase, ImageSoft will create a Solution Requirements Document (SRD) that identifies the requirements of the solution in the form of Use Cases. These Use Cases are converted to Test Cases and are utilized during the System Testing and User Acceptance Testing phases of the project. ImageSoft Way Project Implementation With this hybrid Agile/Waterfall approach, the “ImageSoft Way” provides customers inclusive insight into their solutions as they are being developed on time and within scope by using an iterative mode of development, demonstration, and feedback cycles. The ImageSoft Way relies on traditional project phases but uses an iterative feedback cycle during the build phase which allows ImageSoft to demonstrate the solution to the customer, receive immediate feedback, and make adjustments to the solution. In turn, the customer doesn’t wait until the start of their testing period to see their solution for the first time; they can collaborate through the entire build process. This results in business requirements being clarified, missed requirements being identified, and ensures the best solution for the customer is delivered. The first phase is our Planning and Initiation phase. This phase allows the team to learn about the project and the solution, first by meeting with the Sales team and then with the customer. Any documentation provided to the Sales team is shared with the Project team to ensure an efficient transfer of knowledge. During this phase, the Project Manager builds an initial draft of the project schedule so the customer will know what to expect. The project kickoff meeting is scheduled and conducted and discovery is scheduled. Our second phase, Business Analysis and Design, is often called discovery. We send two experienced team members, usually the Solution Architect and a Systems Engineer, to your location to sit with the users and walk through their business process. We listen, document, and ask questions. We do not build out the solution during this time; we ensure we understand your business, your pain points, and have the right information to build you a solution that will work. When we return to our office, we design your solution. In order to ensure we understand your business rules, we draft a document called the Solutions Requirement Document (SRD). In this document, we write Use Cases to identify the steps required to complete your business process within the new solution. Once internally vetted and reviewed, we send you this draft and schedule a review with you and your business Subject Matter Experts. We review the document live with you, making corrections to the process to ensure all parties agree on what the solution will include. The Business Analysis and Design phase completes once the Solution Requirements Document is signed. With the design agreed to, the Build phase begin. While we collaborate consistently through the entire project, the Build phase is the most iterative in terms of solution reviews and feedback loops. We will establish a regular cadence with you to demonstrate the solution as it is being built. Your feedback is critical in this phase. If we can catch a misunderstanding early in the project, we can update the design and estimate early to avoid overages later in the project. Seeing the solution often also helps your users and IT team understand the solution well before it is released to test and support. Before we release a solution for user testing, we perform system testing within ImageSoft to ensure everything works as designed within the Solution Requirements Document. After this is complete, we train your users to test the solution. We provide and consult on a sample training plan that you can customize for your team, as well as provide training manuals for your solution. We follow a checklist of steps that include other templates and documents that we share with your team to make sure training is successful. Trained users are happy users. During the User Acceptance Testing (UAT) phase, we setup an issue tracking software, Jira, just for you to log your issues or enhancements. We meet with your team multiple times aweek a week to review the issues, work with you to prioritize, resolve, and release for retest. At the end of UAT, we send you a signoff form to permit the solution to be promoted to Production. The last phase is the Production Migration and Go Live. While it seems like we are at the end of the project lifecycle, this is a critical phase and we treat it as such. Our team will collaborate with your IT staff well in advance of migration day to review the infrastructure, apply all licenses, and prep the environment. We build a migration checklist with your IT team with tasks, assignees, and dates to make sure nothing gets missed. We are available outside of business hours so that there can be as little impact as possible to your end users. The project team is allocated post go live to provide the continued support of your solution in Production for up to 30 days. After that 30 days is up, the project team completes a checklist for our Customer Care team that evaluates whether the solution is ready to be transitioned. The Customer Care team has product and development experts available for quick issue resolution and will escalate back to the project team to expedite the resolution of issues for you. Through all phases, you will have a dedicated Project Manager working to ensure your project stays on track. Whether tracking budget, challenging design decisions that compromise scope, removing roadblocks to allow the project team to meet dates, the Project Manager is your project advocate. They also provide you status reports, identify and mitigate risks, and maintain the project plan. Regardless of which team is working on your solution, the ImageSoft Way is to be collaborative, open to feedback, and quick to respond.