330 Part V: Closing Your Software (Web site builder) Project
330 Part V: Closing Your Software Project Issue identification Issue resolution Testing documentation You and the Testy McTesty representatives agree to a fixed-price contract with an incentive for completing by a predetermined date. This is important to you because you need to have time to perform other activities after the software is completely tested and you don t want to take a chance on getting behind schedule. You ve documented all of the details in your procurement management plan and contract management plan and included constraints, assumptions, deadlines, performance reporting requirements, evaluation criteria, payment methods, and change control. You understand from your client, Barbwire Helmets, Inc., what is expected of you as the vendor; Testy McTesty, your vendor, understands what is expected of you, their client. All is right with the world. Being the exceptional software project manager that you are and working with your brilliant hand-selected project team, you complete the Web-based tutorials on time and within budget. Testy McTesty completes its portion of the project but have a few testing issues from the integrated software testing phase. These issues are still unresolved. You don t worry too much about it, though, because these issues are deemed a low priority. At project closure, your client, Barbwire Helmets, Inc., performs the following actions: Quality audits Scope verification Close vendor contracts Receive your invoices Performance review on your work as the project manager You and your client sign the scope verification documents and all project closure documents and you perform the following actions: Document performance reviews on your team members Provide surveys to your project team members to solicit their input on your performance as a project manager
In case you need quality webspace to host and run your web applications, try our personal web hosting services.