RJB Project Scoping

An RJB Project Scoping is a service offering designed to articulate high level requirements, schedule, cost, and a recommended architecture for implementation of a software system. The process usually takes several weeks, and involves onsite data collection and offsite preparation of findings and recommendations. The results are presented to company management as a clear road map on how to proceed with the project. The report includes recommendations for areas that require custom coding, and/or those that might utilize Off-the-Shelf (OTS) software. The Project Scoping is the first step in our comprehensive Agile Software Development Life Cycle (SDLC). A Project Scoping can be delivered as a standalone service, or as part of our Application Delivery service.

Our Background

RJB has performed numerous Project Scopings that have enabled our customers to gain a precise road map for a system implementation. It is an important step that identifies and reduces risk, and sets the stage for a successful project. Make sure you have all the facts on hand to make reliable decisions, and don't hesitate to get in touch for your Project Scoping.

RJB Project Scoping FAQ

What is a Project Scoping?

Project Scoping is a discovery process which will:

  • Articulate the high level requirements for a project
  • Identify key issues, risks and benefits
  • Recommend an architecture approach
  • Recommend development tools and products
  • Propose the project team composition for implementation
  • Provide a project implementation schedule and cost

Why Do I Need a Project Scoping?

Project Scoping will help you:

  • Determine the RISKS that may be encountered during the project
  • Estimate the EFFORT required to deliver the project
  • Define the BENEFITS you will achieve by delivering
  • Assess the overall FEASIBILITY of the delivery approach

After a Project Scoping exercise you will be able to:

  • Understand the nature of the problem and required solution
  • Evaluate the impact to the organization of adopting the recommended approach
  • Take advantage of expertise in sizing the resource requirements
  • Demystify any market hype of with the technology

This is your first step towards a successful project.

When would I use a Project Scoping?

A Project Scoping is useful when:

  • Functional or operational problems exist with an application
  • Concerns exist over the effect of proposed application changes
  • Validation of an architecture for use in follow-on applications is desired
  • There is uncertainty about how best to complete an application implementation

Who Performs the Project Scoping?

The following people perform a Project Scoping:

  • Project Management (part-time)
  • Team Leader (full-time)
  • Architect (part-time)
  • Technical Specialists (as required)

How is the Project Scoping Performed?

There are three phases to a Project Scoping. Onsite phases may be performed by a combination of meetings at the customer site, and/or video conferencing.

Phase I Information Collection

  • Planning meeting to discuss project requirements and client objectives.
  • Delivery of existing project documents (to RJB), including some or all of:
    • User Requirements
    • Functional Specifications
    • Systems Analysis
    • Architecture Description
    • Application Design
    • Database Descriptions
  • On-site or video conference interviews with key personnel responsible for defining the nature of the system, which may include some or all of:
    • Business Analysts
    • System Architect
    • Design Team
    • Users
    • Project Manager
    • Senior Management

Phase II Information Analysis

  • Off-site analysis of all information collected.
  • Follow-up meetings or conference calls, as required, to verify information and assumptions.
  • Preparation of Presentation of Findings documentation.

Phase III Presentation of Results

  • Present findings, including:
    • High Level Requirements and Objectives
    • Proposed Approach
    • Recommended Tools
    • Deliverables
    • Key Issues, Risks and Benefits
    • Suggest Project Team Organization
    • Project Team Roles & Responsibilities
  • Review findings and solicit client feedback
  • Confirm that client objectives have been met.