Appendix
A - Scope, Approach and Methodology
Include detailed implementation procedures, training and technical expertise. Include detailed information on how data is collected/analyzed, and/or moderated. Specify whether the work is automated, done manually, or a combination thereof. This section should include a description of each major type of work being requested of the vendor. All information that is provided will be held in strict confidence. The proposal should reflect each of the sections listed below of the sections listed below
The intended approach to this project is to develop a .NET web-based application that will integrate and communicate with the various modules and systems needed within the client’s infrastructure. This approach will go through JIG’s software development lifecycle process.
JIG’s process has been developed and refined from years of experience. Our approach is a culmination of leading project management and engineering methodologies. JIG’s process is broken up into five phases: Discovery, Requirements, Development, Deployment and Maintenance. Below is a general outline of approach each phase.
Discovery Phase
This is where the project is defined at a high level. This includes a project charter, an evaluation of the clients’ needs and some preliminary discussion regarding possible technology and design options. This is meant to set expectations, scope and project organization so that the execution runs smoothly.
The first step of this process is to develop a project charter to analyze and properly scope the project. This is a necessary and important step in the process as it sets the tone and ensures both parties understand what is to be accomplished and where the project will go. This phase begins with a kick-off meeting and finalized shortly thereafter.
The next step is to identify key users and workflows related to the system to be built. Once these key elements are identified, the users of the system will be interviewed to determine their common tasks and current ways of performing these tasks. As well, input with regards to what works and does not work for each user will be requested and documented. This interview process will result in a business use case/workflow document outlining the key business functions performed by the target audiences. As well, sitemap, audience lenses or other high level information architecture deliverables may be included as part of this phase.
This stage is where the initial requirements are flushed out in detail. This might include exercises such as the systematic design of workflow, input/output, user interface and database designs. As well, overall system architectures, and application development environments will be architected during this phase. This is facilitated by tools such as site maps, network diagrams, business use cases and storyboards.
From a creative side, there are several components used to help drive the overall look of the website. The input from the previous phase helps provide a creative exploration document to specify style guidelines and further refine the desired brand. Typically, JIG starts with a few design concepts and we then narrow down to a single finalized design that applies to the entire site.
This phase entails continual communication with the client to gather the necessary requirements. JIG defines the processes required to ensure timely and appropriate generation, collection and storage of project information using the following:
- Communication Planning: who will need to know what and when
- Information Management: providing information available to the stakeholders
- Performance Reporting: status reporting, progress measurements, issues etc
The final details and technology options will be analyzed and finalized during this phase. These options will be outlined to show the benefits and disadvantages of each choice. Each option will be allocated a price and timeline for implementation. Once the report is complete a review with the key stakeholders will be conducted to discuss the best move forward plan or to address any outstanding issues.
During this phase, cost management efforts can be put in place as well. The project manager from JIG will be responsible for incorporating the tasks into the plan. Techniques such as the budgeted cost of work performed (BCWP) and the budgeted cost of work scheduled (BCWS) may be used. The BCWP is a percentage of the total budget equal to the percentage of the work actually completed. The BCWS is the portion of the approved cost estimate planned to be spent on the activity during a given period.
At the end of this phase both parties will have a very clear understanding of every detail of the system. In summary, we develop the entirety of the solution on paper before we start developing system components. This ensures all details are worked out and costly code/site development iterations are avoided.
The first draft of the test plan shall also be prepared during this phase. Based on the requirements from the contract documents and discovered during the requirements phase, the test plan addresses the high-level requirements also the methodology of testing is described. For example, regression testing, code inspection, etc., may be used as methodologies. Detail test procedures and test cases would be generated based on the test plan.
The development phase is where the application is built and/or configured. This includes the graduated implementation of application features and it allows the client to see actual project development in the staging area. JIG verifies all features are covered and developed within the timelines. During this process the client has the means to verify and give feedback on the progress being made. Communication through weekly status reports, bug tracking and change request logs are used to keep the client informed.
The web pages will be put through Quality Assurance cycles which will test against use cases and procedures generated for the project. Given that the test cases and procedures naturally flow from the QA plan, JIG can guarantee a complete coverage of all requirements with known testing and acceptance methodologies agreed upon by both the client and JIG. A QA report shall be generated at the conclusion of all tests for the client to inspect. If so desired, the client may contribute to the Quality Assurance by participating in the user acceptance segment of the test plan.
Change Management procedures are used to ensure timely and effective decisions to requests for changes (i.e. scope, time, and resources) and deliverables (e.g., requirements, design, specifications). These procedures will determine and communicate the steps for receipt and estimating of the Change/Work Request.
These procedures are meant to ensure that:
- A clear statement of the requested change is established
- The change is logged and communicated to impacted parties
- Firm estimates are established for effort, possible delay and impact on other activities for any set release
- Any pre- or post-requisites are identified
- The appropriate approvals are received
For further details about the planning and reporting during the development phase please see Appendix D – Project Planning Details below.
Deployment is done in a controlled and organized fashion with the facilitation of a staging environment that is identical to production. Nothing will be deployed until it has been fully approved by the client on the staging site. This is done to ensure that all software deployed acts in a reliable fashion. During this phase documentation and training will be provided. JIG’s repository of documentation will be modified and tailored to suit the clients needs. Documentation and training will be provided so the client can run and manage the developed application with very little support. However, JIG is available to provide any support required.
During this phase, a web-based bug and issue tracking system will be provided to both the client and the internal JIG team so all issues are logged, tracked and signed off by the originator before being considered closed. This allowed for real-time reports of issue status and the ability to easily monitor and escalate issues with historical details when needed.
During this phase JIG will run an after-launch review to ensure the client is satisfied with the results. As well, JIG will provide all services to update, support and extend the application as needed.
B - About JIG
JIG has been developing websites and applications since 2001. Originally JIG started as a web developer designing and developing online applications for bank accounts and insurance for large financial institutions. We have since grown to service all kinds of clients in healthcare, small business, not for profits, logistics and more. In 2004, JIG launched its managed service practice to manage servers, networks and more for clients.
Who Are We?
We are a full-service IT Engineering and Development company with a staff of top quality experts. Our experts include software and system engineers, creative designers, network security analysts and business analysts. We are a low overhead company whose primary focus is listening to our customer’s requirements and getting the job done right.
What Can We Do For You?
We will translate your website vision into a reality. It is important to us that we provide you with engineered IT solutions that emphasize your brand and reflect your enterprise accurately. As well, we will ensure full website integration into your existing databases and provide secure access throughout the data network. JIG will deliver these services seamlessly and provide the best possible technology solutions for Ontario Nonprofit Network.
Why Are We Different?
Diverse Talents - We are able to provide engineering, security and design services with the top talent in the industry. Instead of building several relationships with multiple vendors and trying to get them to work together you can coordinate all your branding and technology efforts with one company. This will save you the cost, time and hassle of juggling multiple vendors.
We Listen - We produce high quality appropriate solutions to fit your needs and budget. Many of our competitors have trouble matching our effectiveness because we have an extremely efficient no-frills organizational structure of experienced employees. This allows us to adapt to our client’s needs quickly without the unnecessary bureaucracy.
Experience - JIG Technologies uses a well-formulated and proven process to ensure that we understand and develop according to your immediate needs and long-term goals. Needless iterations are prevented by the experience of our reputable professionals. This translates into the reliable execution and delivery of your project.
Adaptable - JIG Technologies has been developing top quality internet solutions, designs, software products since 2001 and we continue to grow. Our experience and expertise has allowed us to successfully build complex software solutions for large firms and government agencies. The efficiency of our processes has allowed us to extend our services to smaller organizations that require simpler solutions such as Toronto Foundation, Crohn’s Colitis Canada, Elemental Marketing, Legacy Leaders, Ontario College of Family Physicians, Roberta Bondar Foundation/Enterprises
Mission Statement
Simplifying technology to help businesses grow.
To Achieve this Mission JIG Promises…
- To provide in writing a strategic plan on how we will utilize software and technology to accomplish the business goals of the organization.
- To track and follow the plan created and provide progress reports using KPIs to the organization.
- To consistently strive for innovative, cost-effective solutions that provide value and return on investment to our clients.
- To ensure communication is always open, honest and timely.
Our Core Values
- Work Honestly Hard
- Support Each Other’s Happiness
- Be Endlessly Curious
JIG Technologies Inc (JIG) implements an in-house Quality Management System (QMS) to ensure high quality work is consistently produced. By following a defined and repeatable QMS process we can ensure consistent quality. JIG’s QMS process utilizes the following standard:
Quality management systems – Requirements (ISO 9001:2000)
The QMS establishes a baseline for quality practices to be followed on all major projects. If the needs arise, a specific quality program based on the QMS will be developed for each project, and documented in the project Quality System Plan (QSP).
Other standards and references that have also contributed significantly to the development of the JIG QMS are:
ISO 9001: Quality systems – model for quality assurance in design/development, production, installation and servicing, 1994
ISO 9000-3: Guidelines for the Application of ISO 9001:1994 to the Development, Supply, Installation and Maintenance of Computer Software
JIG will follow the in-house QMS consistently. If the complexity of the contract warrants a tailored version of its QMS or the contract authority of the client of the contract demands a project specific QSP, one will be produced and followed consistently. A project specific QSP will be approved by the technical authority of the specific contract.
The JIG in-house QMS is created from the management directive that the management processes, the development process, and the support processes must adhere to established procedures and rules to ensure quality to our clients.
The JIG QMS is followed by all employees and contractors. The responsibility of ensuring quality flows from management to project managers to subordinates with QA ensuring consistent implementation of established processes. QA department reports to management to ensure any deviations and exceptions are dealt with in a timely manner. In addition, the QA department is responsible for gathering performance metrics and submitting recommendations on process improvements and modifications.
The QMS processes are documented in the Generic Quality System Plan (QSP). The document serves as the basis of project specific QSP. The document is under Configuration Management (CM) control and is updated upon the recommendations of QA department. Specific procedures on various processes are documented in the Operation Manual (OM). The procedures can be references to existing documentations and standards utilized by the company. All changes of quality system documents are controlled by CM. Formal Configuration Control Board (CCB) procedures are needed for document updates. All procedures are reviewed by QA at least once every two years. QA meets with management formally at least once every six months to update the management on the latest quality related issues within the company.
The quality system covers the operations entire organization. Particularly, the procedures for the engineering and client support operations are well documented in the QSP.
The QSP and the OM are available to all employees. When a new QA approved version becomes available, the document is made available online in our internal network, and employees and contractors are notified of the new version. Project-specific QSP is also controlled by CM with the content modification approved by QA and project manager. It is available to all project staff and when a new version becomes available, all staff will be notified. Also, a list of current documents, including the QSP, with the latest approved version numbers, is posted on the internal project website to ensure users always have the latest version of all project documents.
All audit reports and related documents are kept for 5 years or 5 years after the conclusion of a project whichever is later. When specific contract dictates a longer documentation preservation period, QA records for the contract along with other project documents will be kept per contract requirements.
On all JIG’s proposal, our customers are made known of our quality system. Our employees and contractors are briefed on all QA, CM procedures upon the association with JIG and all employees are briefed on a yearly basis on updates to ensure all our dealing with our clients are in compliance with our procedures.
The objective of the quality system is to meet the expectations of our client proactively and ensure government regulations compliance in all jurisdictions that JIG carries out its business.
Quality related documentations
CRs are used for formally documenting problems, proposing changes, and keeping track of the status and implementation of the changes.
In general, CRs are used for items under the highest levels of control (e.g., delivered documents, systems under formal test) while PRs are used during development.
PRs are also used during the warranty period, because they are easy for the customer to access and use. An umbrella CR should be used to summarize a group of PRs raised informally on an item now ready for formal update and re-release.
The problem described in a CR may affect more than one software component and/or document. When more than one document/component is affected, the original CR spawns sibling CRs - one for each affected document/component. The original CR becomes the parent CR.
When the CR affects only one component, but possibly more than one software module, the original CR should be sufficient to track the changes that are made.
Problem Report: PRs (Centralized Web Based Problem Tracking)
PRs are used for documenting issues and problems existing in a project. Any user, including the client, can raise a PR through a web interface. This report is tracked through a custom enhanced software named, MANTIS. Once raised, PRs are monitored by the project manager or any stakeholder who has been given the appropriate privileges. All opened PRs within a project are reviewed during the monthly progress meeting to ensure all PRs are being followed up.
Some of the system features beyond a typical report/bug system include:
- Automated email reminders for “stale” tickets
- Email interface to submit tickets by email.
- Automated task assignment based upon category
- Project based workflow customizations (can have different states and workflows depending on project)
- Comprehensive reporting and statistics.
PRs are also used in-house to keep track of any issues raised by clients related to the project. However, specification changes are tracked by Engineering Change Proposal (ECP) and Specification Change Notice (SCN) with actual impacts of the changes are tracked by CR’s.
C - Testimonials
“Our firm has been with JIG for many years now. The quality of services has always been beyond expectation. JIG technologies is in charge of our workflow platform and even helped us to design it. JIG is also in continuous relationship with our technical service and they are always there when we need them most.”
Louis-Daniel Bernier, MBA Manager, FFA Expertise
“Working with JIG over the past few years has been an exceptional experience. What I admire most about JIG is they provide a solution to every problem thrown at them. From the initial call with Shawn to working with the development team, JIG has always provided solutions to our business needs.”
Adil Ebrahim, Operations Manager, Centrade Inc. & CTI International Limited
"Excellence, particularly the transference of business requirements into a viable technology solution...In many areas, the JIG team has gone above and beyond to deliver."
Jacquie Bukaluk, Senior Manager, Deloitte & Touche
“My company hired JIG Technologies as a subcontractor to develop a fairly extensive web-based database application for an electrical utility. Features included integrated context-sensitive online help, customized reporting, a flexible security scheme, images, etc. I developed the specifications, wrote the online help, worked very closely with their developers, and drove the testing/debug/user acceptance work. Their work was consistently high quality, the company was very responsive, and their pricing was quite reasonable. They always went the extra mile to make sure that the client was satisfied. I would highly recommend them to others”
Tim Kelly, President, Aberdeen Technical Services
"JIG Technologies were able to lead us through a systematic and comprehensive process to help us determine a realistic time frame, identify key components and translate our needs into reality. It has been a pleasure to do work with JIG Technologies and we would highly recommend them."
Carol Timlin, Executive Director, VCCS
“JIG has provided superior ongoing development and support for my company for almost 20 years. They have continually met and surpassed my expectations and played an integral role in helping grow my business and keeping our technology relevant in the marketplace. I highly recommend this company.”
Laurie Fenos, Owner, JCLD Online
“JIG Technologies is amazing. I had the opportunity to work with them as both a development partner, building custom software and as our in-house IT support.
As a developer JIG has a way of just making things work. They inherited a massive web platform created by our previous supplier in Drupal and had the unenviable task of repairing and maintaining it. Not only that, the platform was shared by five separate community foundations across Canada, each plugging in and skinning the site for their own market. A massive technical and political project that they managed with ease.
Beyond this, JIG helped us recreate our corporate website and develop a microsite to house the Toronto's Vital Signs Report and all of the past-year issues of the report. The beautiful part about the microsite was the ease in which each year a new site could be created and the past year easily archived for research purposes.
Ultimately, the best thing I can say about JIG technologies is that I knew before I picked up the phone with a new idea that they would always come back to me with a novel way to make my ideas happen, often with a better solution than I had first imagined.”
Michael Salem, Creative Services & Marketing Manager, Toronto Foundation
“JIG is an excellent provider of custom software development and support. They are very easy to work with and very professional. They take the time to work with clients to understand individual needs. I would highly recommend them.”
Sarah Page, Account Manager, Marshall Fenn
