Difference between revisions of "PostProject Phase"

From EUDP
Jump to: navigation, search
m (Klaus moved page PostProjectPhase to PostProject Phase over redirect)
Line 1: Line 1:
 
== What ==
 
== What ==
  
<imagemap>
+
<imagemap>Image:PostProjectPhase.png|
 
+
rect 264 136 326 176 [[Product Accept|]]
Image:Postproject_img.gif
+
rect 454 134 526 180 [[Product Evaluation|]]
 
+
rect 638 134 710 172 [[Project Evaluation|]]
poly 497 118 539 118 539 136 497 136 497 118 [[Project Evaluation]]
+
#<!-- Created by Online Image Map Editor (http://www.maschek.hu/imagemap/index) -->
poly 486 136 551 136 551 154 486 154 486 136 [[Project Evaluation]]
+
desc none
poly 350 117 398 117 398 135 350 135 350 117 [[Product Evaluation]]
+
poly 341 135 406 135 406 153 341 153 341 135 [[Product Evaluation]]
+
poly 201 117 249 117 249 135 201 135 201 117 [[Product Accept]]
+
poly 205 135 246 135 246 153 205 153 205 135 [[Product Accept]]
+
 
+
 
+
 
+
 
</imagemap>
 
</imagemap>
  

Revision as of 12:28, 11 November 2014

What

PostProjectPhase.png

How

The dish

Postproject

Ingredients

  • The realised system - the former system-to-be
  • The customer
  • The developer

Process

The final stages of the project should be carried out with great enthusiasm and at the same level of engagement as shown during the development. This is important in order to conclude the project with a satisfied customer and developer as well a satisfactory product.

In the Product Accept phase, arrange a formal meeting with the customer where the product is officially handed over to the customer. Conduct the Product Accept as the last formal task as described in the Product Accept Specification, which is based on the requirements agreed upon with the customer in the "Launch phase".

After the formal product accept, it is time to evaluate the delivered product as well as the entire project. This evaluation is more informal and gives the customer a possibility to declare how satisfied he or she has been cooperating with the developer. It is particularly worth spending some time on possible improvements that can be introduced in a possible next project.

Finally, the developer conducts an internal project evaluation in order to highlight any possible process improvements in the development phases.

Why

Just as important as the developer's first meeting at the customer's site is done in a professional and effective way, so should the exit also be in order to keep the door open for the next project. The customer should leave the developer with a positive experience in mind having received the expected product within the expected timeframe and to the agreed price. Therefore, a formal Product Accept should be signed by both parties and an informal Product and Project Evaluation should be conducted in order to clear out any misunderstandings and to improve the development process. This will leave the customer with an impression of an even more professional performance in relation to future projects.

Continue to Product Accept.