What is the Pur­po­se of Preli­mi­na­ry Pro­ject Assessment

The preli­mi­na­ry pro­ject assess­ment (PPA) is the pro­cess that is aimed at eva­lua­ting the tech­ni­cal requi­re­ments and appro­xi­ma­ting the cost of a given pro­ject. Bes­i­des the­se esti­ma­ti­ons, PPA’s goal is to ans­wer some of the key busi­ness ques­ti­ons that ari­se befo­re the deve­lo­p­ment even starts:

  • How can we ensu­re the time­ly deli­very of an application?
  • What poten­ti­al road­blocks can we encoun­ter mid-development?
  • Can the pro­ject be sca­led to meet incre­a­sing con­su­mer demands?
  • What are some major steps towards deli­vering a high-qua­li­ty product?
  • How can we ensu­re that our pro­duct has a com­pe­ti­ti­ve edge?

Why PPA is Important?

First of all, the preli­mi­na­ry assess­ment allows you as a busi­ness owner to esti­ma­te the poten­ti­al ROI (returns on invest­ments) and it gives you a clear under­stan­ding of what can be done as well as at what cost.

Second, it pro­vi­des trans­pa­ren­cy bet­ween a soft­ware deve­lo­p­ment com­pa­ny and its cli­ent. Having a trans­pa­rent pro­cess is cru­cial, for a varie­ty of rea­sons, both stra­te­gic and in terms of publi­ci­ty. It allows IT com­pa­nies to spend less time on rese­arch, gives a clear cus­to­mer focus and invol­ves the cus­to­mer in the deve­lo­p­ment process.

The PPA also gives a soft­ware deve­lo­per com­pa­ny the chan­ce to com­mu­ni­ca­te requi­re­ments rela­ted to addi­tio­nal deli­ver­a­bles and leverage the expe­ri­ence gai­ned from simi­lar projects.

How is PPA Structured

In most cases the PPA can be bro­ken down into several sta­ges, let’s move through each step by step, shall we.

  1. Initi­al con­ta­ct. It is a star­ting point for prac­ti­cal­ly any pro­ject. You approach a IT firm with a request to assess a project.Probably, you’ll be asked to fill in an app­li­ca­ti­on form with very typi­cal and strai­ght­for­ward ques­ti­ons. This is whe­re your input ends, and a soft­ware deve­lo­p­ment com­pa­ny takes over.
  2. The first thing that a com­pa­ny will do is deci­de on the tech­no­lo­gy stack for your pro­ject. Or in simp­ler terms, what kind of tools, ope­ra­ting sys­tem, and rela­ted sup­port pro­grams are necessa­ry to deli­ver this par­ti­cu­lar project.
  3. Then it’s time to draw a com­po­nent dia­gram that will logi­cal­ly map out all tech­no­lo­gy parts.
  4. After the map is com­ple­ted the cost of each com­po­nent can be esti­ma­ted, which is usual­ly hap­pens during an expert mee­ting of seni­or staff.

The next step is not is not always the same, becau­se it assu­mes that eit­her the­re are still some blanks in developer’s under­stan­ding and addi­tio­nal infor­ma­ti­on from the cli­ent is requi­red or if a cus­to­mer asks for a more accu­ra­te estimation.

  1. In both cases, the com­pa­ny pres­ents its esti­ma­ti­ons to you and arran­ges a fol­low-up ques­ti­ons mee­ting, whe­re two par­ties go back and for­ward try­ing to eli­mi­na­te any remai­ning uncertainties.
  2. Final­ly, the detail­ed cost break­down can be delivered.

Fol­lowing Up on Pro­ject Assessment

Very rare­ly, the preli­mi­na­ry assess­ment stands on its own. Typi­cal­ly, in the indus­try of IT, it is fol­lo­wed by a detail­ed eva­lua­ti­on. The PPA gives cli­ent under­stan­ding of how the pro­ject will be deli­ve­r­ed, while the second assess­ment usual­ly ela­bo­ra­tes on it and takes a look at ent­i­re endea­vor in hig­her reso­lu­ti­on, so to speak.

The nice thing about preli­mi­na­ry assess­ment is that it is doesn’t real­ly requi­re a gre­at resour­ce input and can be given wit­hin a real­ly short timeframe.

If your com­pa­ny is inte­res­ted in a pro­ject assess­ment, then you can con­ta­ct us at Intech­core. We offer a com­ple­te­ly free preli­mi­na­ry pro­ject assess­ment for your IT project.