Sri lanka web server - 340 Part V: Closing Your Software Project contributed
340 Part V: Closing Your Software Project contributed to the document. Although you may like to believe that those two lists were identical, some people have the gift of writing and organization, and some don t. You may discover that pulling coherent, usable documentation from some team members is next to impossible. Some members are a part of the team because their skill and expertise is needed in an area other than documentation. As much as you may not want to, you ll have to accept the fact that the writing is not something they are good at. Of course, accepting this fact may be a whole lot easier if the team members are crack coders! Documenting the project s successes Success is sweet. It feels good to accomplish something and know that you pulled off a task that was very difficult. It makes you feel all warm inside and beam with pride. But you know this already, right? Many people tend to downplay success and pass it off with, Ah, shucks, it was nothing, or, Just got lucky. Inside we may know that we did the impossible, but are afraid that saying so out loud will sound like bravado. After all, no one likes a braggart. Regardless of how you feel inside, you cannot be afraid to commit the successes to paper as part of your lessons learned documentation. Be honest about what was accomplished and don t be afraid to toot your own horn if necessary. The success came because you figured out what worked and directed your team to get the job done, and that is something that someone else can benefit from on their next project. Commit it to paper, be honest about it, and feel good about it! Documenting the project s failures Along the path, you experienced failures as well as successes. You went in one direction believing that it was the best path to follow, then were blind- sided by an issue that you never gave much forethought to. This is natural with almost every project. These are the unknown unknowns that whack you in the head and wreck your project. That experience of failure needs to be a part of your lessons learned documentation. You document your failures so that future projects will not run the risk of being similarly blindsided and so that readers can see what worked for
If you are in need for chaep and reliable webhost to host your website, our recommendation is http web server services.