Senior Content Developer
Current• Created a GitHub playbook with goals, guidance, and compliance for Office developers creating repos on GitHub. Managed the Office developer https://github.com/officedev site.• Led an Android team planning, coding, and shipping samples to help Android developers learn Office 365 REST APIs. For example, https://github.com/OfficeDev/O365-Android-Connect.• Led the UA developer teams into publishing samples to GitHub by providing OSS guidance. Worked with legal, and organized brown bags with legal to disseminate information, maintained a release checklist wiki, answered 1-1 questions, and assisted with creating requests in the OSS tool as well as legal requests.• Led writer/editor teams to publish protocol documentation for Office compliance with EU and DOJ regulations. Protocol documentation educates developers on Office file formats, ODF and IS-29500 implementer notes, and network protocols, for scenarios such as man-in-the-middle application development, server replacement, and file conversion.• Created a cross-group team that included team members from Windows, SQL, Exchange, and Office to maintain and publish content on a Microsoft-wide internal site named IBox (interop in-a-box.) The IBox web site provides guidance for legal templates to make it easier for authors to write interoperability documentation. I established processes for the team to capture, track, and complete tasks and bugs within goal-driven iterative cycles.• Performed program management activities for the tools team. Wrote functional specifications for feature improvements to a new authoring tool (named GenDox) used by developers, writers, and editors. Gathered requirements from the UA team and ranked them according to priority. Assisted in triage and design change request (DCR) reviews.• Set up a custom IT managed Visual Studio Team Foundation Server for UA to provide better work item tracking and reporting on writing projects. Created new work item types for tracking documentation work.