Chapter 17: Documenting Your Software Project (Free web hosting with ftp) 337 product
Chapter 17: Documenting Your Software Project 337 product the lessons learned documentation is a great historical document that shows the cumulative results of their contributions. Look at the example of a lessons learned spreadsheet in Table 17-1 to inspire you about how to use this valuable tool in your own software projects. Remember, the column headings should vary depending on the particular type of software project that you re managing. You ll be amazed at how quickly this spreadsheet becomes a regularly expected part of your regularly scheduled project team meetings, and your team will take pride in making contributions to it. Table 17-1 Lessons Learned Spreadsheet for Future Documentation Topic Project Lesson Team Area Learned Owner Testing Workflow Prior to starting the testing Testing Testing phase, we need to set the Manager expectation that testers don t stop to resolve issues they just need to document each issue. Testing Workflow During workflow testing, Testing Testing we need to encourage Manager end users to perform their normal job functions. Training End-User During the planning phase, Client Training we need to set the expectation that 90% of end users must be trained in order to ensure successful system implementation. Reports End-User Start gathering information Client Reports on needed end-user reports at the beginning of the project to compensate for the learning curve for stored procedures. Print Testing Testing Ensure that all appropriate Project project team members Manager understand the complexities of testing the print capabilities of the project.
If you are looking for affordable and reliable webhost to host and run your business application visit our ftp web hosting services.