Tenders IT System

Example Evaluation High Level Headings for Implementation (each section can be given a %). Note this is not for a technical evaluation using MOSCOW for Tenders IT System requirements

1. Overall Technical Solution

The purpose of Technical Solution (TS) is to select, design, and implement solutions to requirements. Solutions, designs, and implementations encompass products, product components, and product related lifecycle processes either singly or in combination as appropriate.

2. Solution Architecture

Solution architecture is a practice to provide ground for software development projects by tailoring IT solutions to specific business needs and defining their functional requirements and stages of implementation. It is comprised of many subprocesses that draw guidance from various enterprise architecture viewpoints.

3.Delivery Feasibility by [date]

4.High-Level Delivery Plan

A high-level project plan is a plan that considers the resources, time and goals required to complete a project and monitors them over a certain period of time. This type of plan specifically focuses on the milestones a team should reach at different stages of a project. High-level project plans can also track a project’s progress and provide insight into how a team can adjust their efforts to meet goals if necessary.

5. Team Structure

A typical software development team structure includes a business analyst, a product owner, a project manager, a product designer, a software architect, software developers, software testing engineers, including test automation engineers, as well as a DevOps engineer

6. Proposed Team CVs

Ask for pen profiles

7.Professional Capabilities & Experience: Comparable Solutions

Check for evidence of what they have done before

8.Professional Capabilities & Experience: Function / Sector

MS Gold or other skills required?

9.Auditing, Security & Quality Assurance Standards

10. Cultural Fit

This is very important as sometimes panels prefer different teams who come alive when pitching during the supplier presentation rather than what’s said on paper

System Demo- scenarios

get access to a sandbox or ask for a demo using a user journey

Check out the MoSCoW method or other IT related pages