Documentation Project presentation
- 1. Documentation Project Presentation RANKINGS DETERMINATION, TENNIS AND GOLF
- 2. Overview The documentation project features the source document “Rankings Determination” by Robert J. Lake. The document describes the various point systems used by international tennis and golf to rank men’s and women’s respective sports. Two deliverables were produced to modify and improve the document: A PDF document featuring rankings tables. A slide show for less-experienced users and better visuals.
- 3. Product Features: PDF The PDF deliverable was created to assist the expert users (such as sports historians) in the readability of the original document. The source document was incredibly wordy, with many numbers and explanations of rankings remaining unclear. The PDF features rankings tables for both men’s and women’s golf and tennis. The tables explain how world rankings depend on how the athlete participates in certain events. Some of the information was removed or modified in order for the document to reduce length and vagueness. Cross-references were added for quick usage.
- 4. Product Features: Slide Show The slide show was created for novice users (such as casual sports fans) that require some history and background but not at length. Visuals and simple manipulation of the product allow the user to remain easily engaged more so than a written document. Information is broken down into specific slides with less emphasis on historical information and more on explaining the ranking systems.
- 5. Technical Challenges The first challenge was to find an original source that would meet my expertise in order for me to create two different deliverables. After attempting to revise older Microsoft software, it became evident my time would be spent learning about the product rather than redeveloping it into new formats. My top two dependencies were technical experience and product stability. My inexperience with CMS’s lessened the chance to diversify the formats with which to produce the two deliverables. The change in scope of my project and the new topic made product stability a dependency. Also, finding prototypes for the rankings tables proved difficult.
- 6. Lessons Learned I learned how to fully plan a project, from the analysis of scope, to scheduling, to assessing risks. I also understand how important and time consuming the planning phase should be. What I struggled with the most and had to eventually learn was how to identify user groups. From these user groups one can judge usability and test different formats and styles based on feedback. Writing the Progress Report was very useful in comprehending the full status of the project and how schedules and risks can fluctuate.