Sharepoint Software Development Project Manager Resume
2.00/5 (Submit Your Rating)
Washington, DC
SUMMARY:
- Team turnover and stale IT knowledge hinder project success.
- In today’s era of deep IT specialization, rapid - fire deadlines, and constant tool upgrades, team work and up-to-date know-how are more important than ever.
- The successful program manager must be able to juggle the team’s need for vertical and horizontal communication, work-life balance, and relevant targeted training.
- Experienced IT professional with broad skill spectrum, including federal IT project management, Agile process, software system security, change management, and technical training
- Effective horizontal and vertical communicator and documentation designer
- Consistent improver of policy process, strategy, and procedures
SOFTWARE:
- SharePoint 2016
- SharePoint Online
- O365
- Team Foundation Server (TFS)
- JIRA
- Microsoft Office Suite, including Word, Excel, PowerPoint, Project, Access, One Note
- Splunk
- REMEDY
WORK HISTORY:
Confidential, Washington, DC
SharePoint software development project manager
Responsibilities:
- Led transition from Waterfall to Agile methodology by actually managing projects using the new methodology and showing the team how well Agile works when used properly
- Managed project teams through the IT development process, juggling multiple concurrent projects as scrum master and suggesting approach alterations to improve outcomes
- Facilitated sprint planning meetings and daily standups; provided written reports to product owners upon sprint completions
- Introduced JIRA in tandem with Agile to track tasks, bugs, and issues
- During development, identified risks and issues that could lessen the effectiveness of SharePoint sites or hinder deployment; also developed mitigation approaches
- Helped develop and maintain SharePoint and Office 365 governance specifications; created an Confidential SharePoint governance portal
- Provided level-of-effort and rough order of magnitude estimates to product owners once preliminary requirements were defined
- Responsible for early release definition and scope negotiation for SharePoint applications within Confidential
- Maintained scheduling, tracking, and control of releases for SharePoint applications within Confidential
- Managed procurement of all third-party tools by obtaining multiple vendor quotes, evaluating benefits and return on investment, and ensuring compliance with the complex web of government protocols and federal procurement regulations
- Was direct supervisor of IT project staff, trainers, and technical writers; assigned tasks, reviewed performance, conducted lessons-learned sessions, and supported career progression
- Worked with direct-report trainers to develop a training portal through which Confidential personnel could request instructor-led individual or group training; the portal also provided access to self-paced training materials and video tutorials
- Outlined strategies and approaches for technical writers to deliver the required SLM documentation for the release of all SharePoint applications
- Created an “HR Deputies” program instituted widely in Confidential ; under this program, technical team leaders serve as liaisons between their team and management to better align business objectives with team capacity and to give individual team members a conduit for elevating personal issues
Security officer
Confidential
Responsibilities:
- Reviewed monthly Confidential Security Vulnerability Management (ISVM) reports for vulnerabilities applicable to SharePoint
- Informed engineers of any SharePoint vulnerabilities and tracked fixes for on-time completion
- Pulled security patches from the Microsoft release site and attached them to the ticket created in JIRA
- Ensured that all subsystem Privacy Threshold Analyses (PTAs) were current; helped system owners create PTAs for new subsystems or update PTAs at the time for renewal
- Requested outages to accommodate patching and attended Change Control Board meetings to get approval of outage schedules
- Helped test security controls
- Participated in annual table top exercises to ensure that the system disaster recovery plan was up to date
- Worked with the compliance team to ensure that Confidential SharePoint had all required patching, not just Microsoft patching; developed alternative approaches when required software in a given environment did not work with Microsoft or other servers in the environment
- Provided resource continuity as a constant, long-term security assistant; I supplied the corporate memory and deep knowledge of the environment to reduce the ill effects of several turnovers in the lead information system security officer
SharePoint software requirements analyst
Confidential
Responsibilities:
- Created a requirements service portal eventually adopted throughout the Chief Information Officer’s organization; portal provides a “one stop shop” to more than 28,000 users for the entire spectrum of IT support Was primary collaborator with the customer in defining business needs and effectively answering those needs with custom SharePoint applications
- Documented requirements using an SLM template and submitted them for gateway reviews and development approval
- Facilitated meetings with all stakeholders prior to deployment of SharePoint systems
Confidential, McLean, VA
Project configuration manager
Responsibilities:
- Coordinated with stakeholders of Restatement Change Management teams to standardize their CM process and procedures to align with Confidential CM policies
- Served as the primary interface between all related technical/ support groups needed for activation of various applications and environments
- Verified that all information in Remedy tickets had full traceability in Clear Case and Clear Quest
- Documented various methods to ensure that stakeholders had full traceability to all applications that were migrated during Restatement
- Set up active directories for all end user computing systems ( Confidential ) needing to be migrated
- Checked in the active directories in repository that was maintained in Clear Case Maintain version control for Confidential and Enterprise System and Operations (ESO) migrated via Clear Case and Clear Quest
- Performed deployments via automated CM tool and manual migrations for Confidential
- Ensured regular audits of the set of authorized users for any applications being managed
- Presented evidence of application/access controls in response to requests from internal audit teams and SOX compliance
- Served as first level escalation point for all non-standard and non-compliant requests
- Developed and updated documentation for team migration process and plans such as Configuration Management Plans, Service Level Agreements, Primary Guidelines, and other team role guidelines