TECHNICAL SKILLS:

Operating Systems: Windows 7, Windows XP, Linux, Mac OS

Software: IBM Lotus Notes, MS Office Suite 1997 - 2013, MS Visio, MS Project, Doc-To-Help 7.0, Cascading Style Sheets (CSS), XHMTL, SharePoint 2010, SnagIt, RoboHelp, Adobe Dreamweaver, Adobe Captivate

PROFESSIONAL EXPERIENCE:

Confidential, New Carrollton, MD

Technical Writer

Responsibilities:

• Provide updates to the project’s agile documentation, i.e., Computer Operator’s Handbook, SDSR, ICDs, and ensuring all documents are 508 compliant.
• Create/update and maintain the documentation repository from SharePoint to DocIT.
• Ensure that all signed/finalized documents are stored on the project’s documentation repository.
• Meet weekly with the PMs to review progress on daily standup sessions.

Confidential, New Carrollton, MD

Technical Writer

Responsibilities:

• Provided quality assurance to documentation created/updated by technical writers to ensure they meet the guidelines established by the IRS Enterprise Lifecycle (ELC) guidance
• Met with the quality assurance staff on a weekly basis to review any new and/or updated guidance documentation
• Reported to the technical writers on compliance guidelines
• Maintained an updated version of the team’s style guide so that it is consistent with what is delivered to the customer
• Created, developed, updated and maintained any software manuals, publications, specific to ACA application design, operational documentation
• Delivered updated manuals and publications or change pages to the updated manuals and publications to ACA Systems as changes are made to AIR hardware and software
• Provided all documentation and manuals required for the maintenance and operation of any ACA hardware and/or software application that is modified or acquired after contract award for the period of this Work Request
• Obtained documentation and software manuals required to meet the requirements of the contract
• Maintained all existing documentation and software manuals to meet the requirements of this contract. Appropriate change pages to all existing documentation shall be provided to the IRS whenever a software change is made throughout the period of this Work Request.
• Provided all documentation for all software that is modified, newly developed, or acquired after contract award, in the format described for which the IRS may assume maintenance and modification responsibilities
• Maintained, updated, and delivered printed and electronic copies of all screen displays in file formats
• Scribed and recorded meeting notes for ad hoc and/or recurring meetings assigned

Confidential, Washington, DC

Technical Writer

Responsibilities:

• Create MS Visio template to be used by divisions within Confidential so that all Visio process diagrams maintained by QA and stored on SharePoint are consistent. Provide guidance to SMEs on how to use the MS Visio template.
• Create MS Word template to be used by divisions within Confidential so that all MS Word documents maintained by QA and stored on SharePoint are consistent. Provide guidance to SMEs on how to use the MS Word template.
• Create, update and maintain the Quality Assurance documentation style guide to be used by all writers, business analyst and QA staff.
• Collaborate with the Washington Metropolitan Area Transit Authority’s ( Confidential ) on documenting Information Systems Security policies and procedures for the various divisions within the Metro transit system.
• Create and maintain a list of current/future process documentation, diagrams, user documentation and other artifacts produced by various divisions.
• Identify outdated processes and provide guidance on updating the information to the current state.
• Provide guidance on the creation of user documentation for a task management system designed for in - house use.
• Organize existing policies in preparation for implementation of new standard operating procedures.
• Conduct brainstorming sessions on policy categories, types, roles and responsibilities, and identify divisions.
• Research industry standards to suggest to management as best fit solutions to as-is documentation.
• Work with developers on creating a tracking system that will assign unique identifiers to existing process documents, Visio diagrams and user documentation as they pertain to various work areas within divisions.

Confidential, Suitland, MD

Business Analyst/Project Coordinator

Responsibilities:

• Create High-level and Detailed Design documents by working with engineers and developers.
• Create style guides and standards for consistency that included illustrations, screen shots and other images.
• Create SOPs and Work/Task procedures as required. I've created documentation templates, organizational charts and checklists for the various documents all in compliance with CMMI.
• In order to create a workable SOP, I've interviewed and worked with a team of engineers and SAs to finalize an SOP.
• Create real scenarios based on the current stage of the project teams SDLC stage of their project.
• Create and provide supporting documentation to assist with student manuals and case studies to aide in the training.
• Interact with project managers to identify the project team’s need and assist with coaching on how to move through the SDLC whether through the Waterfall method or Agile. Aided in the transition from the Waterfall method to Agile/SCRUM development. During this time, I participated in 7-10 daily Scrum meetings.
• Interview programmers, engineers and developers and SMEs to formulate and complete technical documents this may include creating process flow diagrams using Visio or taking screen shots using SnagIt to insert into the file.
• Research existing documentation and other developer’s and/or engineering notes, source code to create documents or update existing documents.
• Work closely with management to identify the types of training needed within the directorate.
• Provide industry standard process training to the Economic Directorate on Design (both high-level and detailed), Code, Software Configuration Management, Test Plans and Test Cases, Release to Production, Walkthroughs and Inspections, and System Testing (regression, performance, and integration). The various training material were written that described how each document is formulated, who should author the documents within the particular phase of the project.
• Perform quality assurance to project teams to ensure the deliverable was consistent with established standards of quality.
• Create an MS Project schedule for the group within the directorate that includes attainable milestones.
• Write, edit and format presentations, instructor guides, student manuals in preparation for training Census ESMPD, FTD, and GOVS personnel on processes and procedures as mandated. After the completion, received a plaque of appreciation from management.
• Create and update the company’s Computer Based Training (CBTs) for end-users.
• Create process documents such as Project Management plans that contain diagrams, images and workflows.
• Conduct and participate in weekly staff meetings with management.
• Act as point of contact in planning for Directorate-wide event (ESPI Day), i.e., secure logistics, setup breakdown classrooms, and consolidate feedback from meetings or training sessions.
• Provide training to new personnel on document management, training profiles, training plans, file structure, logistics, copy services, and all other ESPI related duties
• Manage the Branch’s Intranet website using CSS for consistency throughout and XHTML with links to and from areas within the directorate. Also working as the lead in designing, maintaining, and updating the new ESPI Section of this website for compatibility with common browsers, i.e., Safari, Mozilla Firefox, IE+, etc. All graphics and layout is mocked up using Adobe PhotoShop and then presented to upper management for approval.
• Work with other members to facilitate roles and responsibilities when requesting information to add, remove to and from the newly designed website.
• Lead Implementation Manager for the ESPI Website as far as design, changes, updates and content.
• Conduct and lead Change Control Board meetings whenever changes, fixes, or modifications suggested by directorate personnel.

Confidential, New Carrollton, MD

Business Analyst/Project Support

Responsibilities:

• Act as lead quality assurance and ensure that project-specific documents were accurate and contained the required data specified by various supporting divisions that monitor the Project's progress.
• As the QA lead my duties were to provide monthly status reports on the Project's activities, conduct and organize the Integrated Baseline Review with the Program office, Project office and contractor, organize and assist the QA Division with the project audit, and coordinate and facilitate kickoff meetings, milestone reviews, and stakeholders.
• Ensure contractor documentation conformed to the IRS' established Enterprise Life-Cycle (ELC) guidelines and all associated Data Item Descriptions (DIDs) and Directives as well as policies were followed. The IRS ELC documentation is their version of any product/software/system development process used in the IT environment.
• Work directly with the project manager to ensure the accuracy of the MS Project Plan.
• Format, group, create, update and manipulate tables and reports using Crystal Reports.
• Ensure that milestones were accurate, documented in the project plan.
• Attend joint application design (JAD) sessions to document requirements to include in the requirements documentation.
• Create and Review requirements documents based on the JAD sessions with developers and end users.
• Work with developers and other analysis to create a system specification document. If necessary review developer code/comments to determine the system flow.
• Create and maintain a high-level and detailed design document based on reviewing other available documentation and interviewing Subject Matter Experts as well as developers/programmers.
• Coordinate and lead in Contractor’s Lessons Learned sessions and provide documentation of the outcome.
• Interview contractors and provide evaluation of contractor performance using predetermined metrics.
• Write, edit, and update all Project-wide plans, which included the Quality Management Plan, Project Management Plan, Training Plan, Configuration Management Plan, Risk Plan, and Tailoring Plan.
• These contractor deliverables were reviewed for accuracy and content relevancy.
• Act as lead Training Coordinator to ensure the PMO had the required training relevant to their assigned tasks. The Training Plan was updated as needed as team training was received.

Confidential, Wash., DC

Technical writer

Responsibilities:

• Create, edit, and maintain documentation such as Detailed Designed document (using the high-level design as a base), Implementation Plan, Training material, system and unit test plans, and status reports. The requirements document was later updated due to system upgrades requested by the client.
• Attend weekly project status meetings.
• Produce meeting minutes from these weekly meetings.
• Document and track action items with engineers and analyst.
• Consolidate team status reports in preparation of upper management review.
• Interact with subject matter experts to ensure tasks are completed as assigned.

Confidential, Wash., DC

Technical writer

Responsibilities:

• As a writer, was responsible for writing a user manual for the Confidential Judge Advocate General's case management system.
• Procedures are written based on documented user requirements and gathering information from team leaders and subject matter experts.
• Documentation is updated based on any change reviews that are generated. Some responsibilities are to write standard operating procedures for the Legal Automation Army-Wide System (LAAWS) project.

Confidential, New Carrollton, MD

Configuration Rep/Technical writer

Responsibilities:

• I was assigned to follow CM procedures as required by the project. As a CM rep, my responsibilities consisted of managing, updating, and assigning Configuration items to various artifacts.
• Create and maintain the CM Worksheet that recorded Configuration Items.
• As a member of the process awareness team, I was responsible for creating/updating processes and procedures for the CASE Management project. The PAT was developed to better identify and document industry standards, traceability and development tools, as well as required training for the members of the IRS CASE Management project.

Confidential, Wash., DC

Technical writer/Desktop Support

Responsibilities:

• While working on the Help Desk, I have configured POP, SMTP Lotus Notes mail for multiple projects.
• Created Lotus Notes database on multiple occasions for divisions.
• Created help tickets in response to employee issues.
• Write and maintain the Standard Operating Procedures (SOP) for the Network Division of the U.S. Department of Justice Community Oriented Policing Service ( Confidential ) program.
• Desktop support duties included arranging for the repair of failed computer equipment, problem solving, and assisting users by telephone, email, and in-person with various computer-related issues.
• Responsible for administering and maintaining user accounts and profiles, monitoring email server accounts, maintaining secure access, and assisting end users as needed.
• Provided support and at times guidance with using new software and other office tools.

Confidential, College Park, MD

Technical writer

Responsibilities:

• Provided technical writing services on an as-needed basis.
• Created and updated the documents based on the growth of the current database application with the Confidential and Records Administration (NARA).
• Conducted system analysis with various vendors.
• Facilitated joint application design and rapid application design sessions and gathered requirements for the design of a new application system.
• Documents written while on this assignment included: user's manual, requirements document, system administrator's manual, database design document, functional design document, and a test plan.
• Utilized Oracle Designer as a repository for documenting the functions, entities, and attributes for the current system.