IT Project Planner I

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting: It includes description of School of Medicine (intro), then "Be You. Position Overview ..." then "Be Bold. Position Description ..." then "Choose Duke." then "Anticipated Pay Range ..." then benefits description, then duplicate pay range, then EEO, etc. We need to extract substantive content: Overview, Responsibilities (position description), Requirements (minimum requirements), Preferred Qualifications (maybe none), Skills? Not explicit. Benefits: described in Choose Duke section (competitive benefits package). Pay: Anticipated Pay Range given. Schedule: not mentioned. So we include sections: About the role? Could be overview. Could use "About the role" heading for position overview. Responsibilities: from Position Description. Requirements: Minimum Requirements. Qualifications: maybe Preferred Qualifications (but it says "Preferred Qualifications OR AN EQUIVALENT COMBINATION OF RELEVANT EXPERIENCE AND/OR EDUCATION. N/A." That's basically no content; we should not include Qualifications if it's just placeholder. Skills: not explicit. Benefits: from Choose Duke. Pay: Anticipated Pay Range. Schedule: none, omit. We must not include sections with filler like "commensurate with experience". So we will include only those with real content. We need to use

• for any list of duties/requirements/benefits. So we need to turn responsibilities into list items. Requirements into list maybe. Benefits into list. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific systems (EQAPOL, IQA, VQA, SPICA, SLIMS, AMP, Protein Inventory). Also mention tasks: develop system requirements, functional specs, test plans, collaborate with technical staff, manage budgets, liaison to vendors, etc. Also mention tasks like design/maintain DHVI Intranet website, oversee software evaluations, provide ongoing application support, support audits, develop SOPs, lead annual review of DHVI IT Policies, manage vendor contracts, organize software validation strategies for 21 CFR Part 11 compliance, draft critical IT-related documents for federal contracts, serve as primary DHVI Liaison to OASIS and DHTS groups, assist with DHVI server node acquisition, management, replacement. We need to keep all that. We also need to include the introductory paragraph about School of Medicine? That is background but not part of job description? It might be considered "About the role" or maybe we can include as a brief intro paragraph before sections. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having a paragraph before headings. We can include a

  with the School of Medicine overview as background. But we must not repeat job title. The job title is "IT Project Planner I". Not to repeat as heading. We need to output only HTML fragment, no /, no markdown fences. Thus final output: maybe:

  School of Medicine Established in 1930, Duke University School of Medicine is the youngest of the nation's top medical schools. Ranked sixth among medical schools in the nation, the School takes pride in being an inclusive community of outstanding learners, investigators, clinicians, and staff where interdisciplinary collaboration is embraced and great ideas accelerate translation of fundamental scientific discoveries to improve human health locally and around the globe. Composed of more than 2,600 faculty physicians and researchers, nearly 2,000 students, and more than 6,200 staff, the Duke University School of Medicine along with the Duke University School of Nursing, and Duke University Health System comprise Duke Health, a world-class academic medical center. The Health System encompasses Duke University Hospital, Duke Regional Hospital, Duke Raleigh Hospital, Duke Health Integrated Practice, Duke Primary Care, Duke Home Care and Hospice, Duke Health and Wellness, and multiple affiliations.

  About the role

  The IT Project Planner I will manage multiple Duke Human Vaccine Institute (DHVI) Application/Database computer system projects including development of system requirements, functional specifications, system software, test plans, and collaborate with technical staff for the implementation of system hardware and software, user implementation training, and management of system life cycle process. In addition, they will own management of the IT project-specific budgets and serve as the liaison to vendors for software invoicing, acquisition and vetting. This role will report to the Director of Scientific Program Management in the DHVI Program Management Office.

  Responsibilities

  • Create documentation for various initiatives including test plans, test cases, software implementation plans, and process improvements.
  • Work directly with DHVI stakeholders to understand project concepts, deliverables, objectives and approach of projects.
  • Communicate closely with the project stakeholders and managers on project statuses, risks, and mitigation plans.
  • Work with the team to define scope and objectives of all levels of testing. This includes establishing the purpose and deliverables of the test effort, developing and implementing test plans/cases.
  • Participate in all aspects of testing: unit, integration, functional, regression, load/performance, automation and system testing.
  • Manage standard project management processes, tools, and methodology.
  • Define and develop multiple project goals, schedules; monitor and evaluate project effectiveness using qualitative and quantitative tools, recommend and help implement modifications to improve effectiveness and meet project milestones.
  • Make decisions that have a significant impact on the successful achievement of project objectives related to Federal, State, and other organization contracts and grants awarded to DHVI.
  • Manage and create yearly IT application- and/or project-specific budgets for the DHVI Program Management Office (PMO).
  • Initiate, establish, and maintain business relationships with all key stakeholders of a project whether internal or external to DHVI.
  • Work with Finance to establish purchase orders, receive and review invoices before submitting to Finance for payment.
  • Establish, lead, and facilitate numerous cross-functional project teams with faculty, staff, and vendors.
  • Develop system requirements, detailed task lists, work effort assessments, and resource allocation plans based on input from all key players and team members.
  • Proactively analyze risks and issues that may compromise project results and develop plans to remove or mitigate them.
  • Manage project management plans, documentation and schedules to ensure successful projected delivery for the application portfolio.
  • Collaborate with project stakeholders and application managers to provide training to project teams and application users prior to application implementation.
  • Provide training to contract and grant program managers in the transition of application management responsibilities from the development and implementation process to the operational environment.
  • Establish and maintain liaison with other School of Medicine (SoM) and Duke Health Technology Solutions (DHTS) IT programs, offices and departments to coordinate projects to accomplish program objectives; manage associated vendor’s efforts to ensure positive progress, and milestones met within resource allocations.
  • Design and maintain the DHVI Intranet website with input from the various DHVI department stakeholders, as well as the Chief Administrative Officer and Director of Scientific Program Management.
  • Oversee software evaluations for new software acquisitions by DHVI departments.
  • Provide on-going application support for applicable applications to include; EQAPOL, IQA, VQA, SPICA, SLIMS, AMP, and Protein Inventory systems.
  • Support Audits by providing IT documentation and resource information as needed for federal, sponsor, or certification audit requirements.
  • Develop Standard Operating Procedures for process improvements and applications as needed.
  • In addition, lead the annual review of the DHVI IT Policies.
  • Manage application vender contracts and establish statements of work for project initiatives.
  • Organize and implement software validation strategies to achieve 21 CFR Part 11 compliance.
  • Support federal contracts through the drafting of critical IT-related documents.
  • Serve as primary DHVI Liaison to the OASIS and DHTS groups within Duke.
  • Assist with DHVI server node acquisition, management, and replacement.

  Requirements

  • Education: Bachelor’s degree.
  • Additional training in Project Management or related training is desired.
  • Experience: Two years of experience in project management, with increasing scope and independence.

  Benefits

  • Competitive benefits package including health insurance plans, generous paid time off, retirement programs with employer contributions, tuition assistance for employees and their children, and more.
  • Comprehensive and competitive medical and dental care programs.
  • Generous retirement benefits.
  • Wide array of family-friendly and cultural programs.

  Pay

  Anticipated Pay Range: Duke University provides an annual base salary range for this position as USD $62,932.00 to USD $102,490.00. Duke University considers factors such as (but not limited to) scope and responsibilities of the position; candidate's work experience, education/training, and key skills; internal peer equity; as well as market and organizational considerations when extending an offer.

  We should not duplicate the pay range paragraph twice. Also we should not include the EEO boilerplate. Also we should not include "Choose Duke." heading as it's not a standard heading; we already captured benefits in Benefits section. The "Choose Duke." paragraph includes benefits description; we used that. We need to ensure we didn't miss any substantive info: The intro about School of Medicine we kept as a paragraph. The "Be You." and "Be Bold." are just stylized headings; we incorporated content. We must not include "Preferred Qualifications OR AN EQUIVALENT COMBINATION OF RELEVANT EXPERIENCE AND/OR EDUCATION. N/A." That's placeholder; we skip Qualifications section. We must not include "Schedule" section as none. Check for any leftover boilerplate: "Equal Opportunity Employer..." etc removed. "Essential Physical Job Functions" removed. Also "Learn more at https://hr.duke.edu/benefits/" we might keep as part of benefits? It's a link; we could include as a link in benefits. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive? It's a reference for more info. Could include as a link in benefits. But we already have benefits list; we could add a

  with link. However the instruction says use

  for prose. So we could add a

  Learn more at Duke Benefits.

  within Benefits section or after. But we must not create new sections unnecessarily. We can add a

  inside Benefits section after the list. However the instruction: Use

  • for any list of duties/requirements/benefits, and

    for prose. So benefits list is a list; we can also have a prose paragraph after the list. That's fine. Similarly for Pay we have a paragraph. We also might want to include the link to benefits in the Benefits section. Let's adjust Benefits section:

    • ...
    then

    Learn more at Duke Benefits