Sally Vlamis Email & Phone Number

Liberty, Mo

• Edit web content, training materials, and business proposals for grammar, style, and consistency.• Edited preliminary draft of Data Visualization book.• Created help file for business analyzer software product.

Kasnas City

• Interviewed stakeholders and subject matter experts to gather business requirements.• Wrote functional requirements and created screen mockups for software development lifecycle tools.• As part of Agile development team, coordinated with stakeholders and software engineers to determine project resources and timelines for developing new functionality.• Ensured tracing of functional requirements to test steps and assisted with testing as needed.• Created and maintained documentation for software development lifecycle tools (wiki help pages, newsletter articles, release notes, and policy and procedure documents).• Piloted use of IBM Rational Requirements Composer (RRC) for creating and managing software requirements; migrated in-flight designs from the wiki to RRC.

• Created and maintained online help for team's suite of software development lifecycle tools.• Created and published release notes (what's new, FAQs) for monthly software releases.• Developed content for and published quarterly team newsletter.• Created flow diagrams of development pipelines to supplement online help content.• Wrote demo scripts for and created videos about new software features.• Migrated original WinHelp files to WebHelp files and then to wiki pages.• Converted content for end users (articles, white papers, support information) from SharePoint to wiki.• Created and maintained controlled documents (policies, procedures, and work instructions) for team.• Migrated controlled documents from Microsoft Word to wiki pages with an online approval process.• Led organization’s internal reward/recognition program.

Documentation Process Lead (1997-2000)• Created network for technical writers to coordinate efforts and ensure adherence to standards. • Chaired monthly meetings to discuss documentation-related initiatives and concerns.• Served as technical resource and chief troubleshooter in dealing with help file issues.• Led migration from paper-based documentation to online help using RoboHELP.• Interviewed technical writer candidates and made recommendations to hiring managers.• Created training materials and taught classes for new technical writers.• Helped create and maintain the Technical Writer’s Handbook and the Cerner Style Guide.Editor (1993-1997)• Edited documentation by writers to ensure quality and conformance to department standards.• Created and updated user reference guides, quick reference cards, and product support guides.• Interviewed new writer candidates and led new writer training classes.• Facilitated migration of documentation set from MASS-11 (VAX-based word processing software) to Interleaf (PC desktop publishing software).Technical Writer (1992-1993)• Wrote and updated user reference guides for VAX-based health care software including pharmacy; workload reporting; commercial requisition processing; and remote report distributions.• Documented Cerner Command Language, a programming language patterned after SQL.• Proofread manuals created by other writers prior to publication.

• Wrote user’s guides for IBM PC and Macintosh versions of a budget system.• Edited and wrote Pension Accounting System documentation set (included user and technical manuals).• Wrote informative and how-to articles for quarterly departmental newsletter.• Contributed to development of departmental style guide for technical writing.

Boston, Ma

• Edited laboratory procedure manuals to meet College of American Pathologists (CAP) standards.• Developed data entry system for laboratory survey data using Lotus 1-2-3 and wrote documentation.• Wrote user’s guides for labor cost and workload statistics database systems.

• Proofread and edited articles and calendar section for Brown University publication.