Contact Us

Contact Us

Requirements Understanding & Project Definition

Objectives

Objectives are to understand customer business processes, customer needs, requirements, and constraints. So that, the scope of the project, customer objectives, constraints, and assumptions can be defined.

Process Entry/Exit Criteria

Entry Criteria Exit Criteria
  • A query or call or RFP is received from the customer
  • A person is assigned for customer follow-up.
  • Project scope, objectives, constraints, and assumptions are defined.

Process Inputs/Outputs

Inputs Outputs
  • RFP or customer email or tender notice
  • Timesheet System
  • Project Proposal / SOW

Tasks

  1. Technosoft Higher management either receives a query, call, tender notice or request for proposal (RFP) from a prospective customer, or makes an introductory call or approach to a prospective customer.
  2. Higher management assigns a PM or a Contact Person to follow up the customer request.
  3. DevMgr/PM/Contact Person develops an understanding of customer problems, needs, requirements, constraints, and objectives.
  4. DevMgr/PM/Contact Person defines the scope of work on the basis of understanding of customer requirements and available information in Proposal/SOW and (or) in Functional Specifications.
  5. DevMgr/PM/Contact Person defines constraints and assumptions related to budget, staff, and schedule in the Timesheet system.
Guidelines for Requirement Understanding and Project Definition
  1. This is a very high-level process of customer interaction, a customer can be approached in many different ways depending upon the customer type, business relations, and customer geographical location.
  2. DevMgr or a PM is assigned to follow-up customers and preparing proposal/SOW.
  3. Usually, the Project definition information that includes Scope of work, Customer Objectives are defined in Project Proposal and then in Functional Specifications.

Constraints and Assumptions related to budget, staff, and schedule are documented in the Proposal/SOW and Timesheet system whereas system, requirements, and design related constraints and assumptions are documented in Functional Specifications.