Project Management

The Project Management team strives to do the following:

• Monitor the Digital Product Roadmap and watch for any impending delays, missed milestones, or required cross-team coordination. Pay close attention to metrics and team progress.

• Support each active project's on-going goals and the important strategic goals of those initiatives.

• Continue to revise, question, and amend our project management processes to ensure that we are working as efficiently as possible -- and that we are set-up to achieve the individual project goals.

• Ensure that cross-team coordination and collaboration is encouraged and supported by our team.

• Carefully and completely gather requirements and document business rules.

• Regularly review project milestones and ensure schedules are clearly communicated for all projects.

• Think and act proactively rather than reactively.

• Are communicative, responsive, and follow our outlined protocols.

• Ask hard questions and facilitate regular discussions.

We utilize Agile development practices and the SCRUM model to manage projects. Each team uses the various SCRUM ceremonies to coordinate work, communicate, coordinate, and manage timelines.

The Project Management team is responsible for any schedules, milestones, communication, and status updates -- with inputs from other teams and coordination with Product Managers.

The Project Managers (PMs):

• Help resolve impediments

• Establishes JIRA project with proper ticket workflows and AGILE boards

  • We should strive for a board that anyone could glance at and know exactly where a ticket is in the process both physically (server) and within the overall process.
  • Hand off between teams should be made clear and the ticket flow should reflect that.
  • All bugs in an active Sprint should go through the PO for prioritization. Any decision point on tickets should be made by the PO and documented in tickets by the PM. The PO determines which bugs to work on during the sprint and which bugs can wait and be moved into the backlog.

• Monitors progress on a day-to-day activities against the baseline Delivery Plan

• Facilitates the team focus on the on-time delivery of agreed products

• Manages deployment scheduling in coordination with PO, tech lead and DevOps

• The Project Management team acts as a bridge between stakeholders, designers, developers, DevOps team members and Quality Assurance.

• The Project Management team regularly provides:

  • weekly summaries to outline high-level view of progress towards overall project goals;

  • release notes for each deployment;

  • milestone schedules that translate the Sprint schedules into a timeline with specific dates outlined to show milestones toward overall project goals;

  • release planning checklists.

The team's goal is to ensure that we have clear implementation plans outlined before upcoming releases, that team members understand their role in release preparations, and that we are effectively managing release preparations.

The team facilitates coordination:

• The CRB meeting that allows for review of upcoming releases and coordination across products/projects
• Release Planning Meetings
• Incident responses Plans
• The team organizes each SharePoint space for project documentation.

The Business Analysts (BAs) on the Project Management team play a critical role in acting as a liaison and a translator. The BAs gather, analyze, and define requirements. The BAs adhere to the following process: https://wwnorton1.sharepoint.com/:w:/r/DP/PM/_layouts/15/Doc.aspx?sourcedoc=%7BB302F980-A281-4EC7-B10D-893F61788043%7D&file=BA_Process_Requirement%20Gathering%20and%20Business%20Analysis%20Process.docx&action=default&mobileredirect=true.