Software Project Manager

Department: Software & Development  Reports to: Head of Development  Location: Bristol  Salary: c. £35,000 Role Purpose The Software Project Manager is responsible for coordinating the development work required for Newpark's projects. Working closely with the Head of Development and teams across the business, the role makes sure Development knows what's coming, requirements are clear, work is properly scheduled and everyone knows what's happening. You aren't responsible for managing developers or deciding how something should technically be built. You're responsible for making sure the work doesn't get lost, forgotten or discovered two days before somebody needs it. Key Responsibilities Development Projects Coordinate development requirements from initial handover through to completion. This includes:

• Understanding and documenting what Development needs to deliver.
• Identifying deadlines, dependencies and information required.
• Working with the Head of Development to get work scheduled.
• Tracking progress and following up outstanding actions.
• Coordinating development requirements for new sites, site additions and other projects.
• Keeping the wider project team updated.
• Identifying anything that could affect delivery and raising it early.
• Making sure completed work is communicated to the people who need to know. The Software Project Manager owns the coordination of the work, not the technical solution. Project Meetings & Communication Attend relevant project meetings and provide a clear view of Development's position. That means knowing:
• What's required.
• What's been scheduled.
• What's in progress.
• What's complete.
• What's outstanding.
• What could affect the project date. Where you don't know the answer, find the right person, get the answer and come back with it. Work closely with Project Management, Client Operations, Technical Support, Sales, R&D, Production and Development to make sure information moves between teams properly. This might include supporting the Sales Team on a client demonstration, or joining the Operations Team in a client meeting. Sending someone an email isn't the same as getting something done. Following things through is a key part of this role. Planning & Priorities Work with the Head of Development to make sure project requirements, deadlines and dependencies are visible when the Development team's workload is being planned. The Head of Development decides development priorities and how technical work is delivered. The Software Project Manager makes sure they have the information needed to make those decisions. Where priorities conflict or a deadline is at risk, raise it early rather than allowing it to quietly slip. Working With the Head of Development The Software Project Manager reports to the Head of Development and supports them in organising and coordinating the Development team's project workload. The distinction is straightforward: Head of Development: manages the Development team, technical delivery and development priorities. Software Project Manager: manages the coordination, deadlines, dependencies and communication around development projects. The Software Project Manager does not line manage developers. Working With the Project Manager Newpark's Project Manager remains responsible for delivery of the overall client project. The Software Project Manager coordinates the development workstream within it. The two roles work together to make sure Development knows what it needs to deliver, has the information it needs and understands when the work is required. Working With R&D The R&D Director has overall responsibility for the longer-term direction of Newpark's software and products The Software Project Manager doesn't set that direction, but will help coordinate development work that comes from it. Decision Making & Accountability The Software Project Manager is expected to take ownership of keeping development projects organised and moving. You should be comfortable chasing actions, asking questions and challenging dates or requirements that don't look realistic. Technical decisions and changes to Development priorities remain with the Head of Development. What Success Looks Like
• Development knows what's coming.
• Requirements and deadlines are clear.
• Work is properly scheduled and tracked.
• Other departments know what's happening.
• Problems are raised before they become delays.
• The Head of Development has a clear view of project commitments.
• Development work is completed when the wider project needs it.
• Projects don't get held up because somebody forgot Development needed to do something. The Person We're looking for someone organised, persistent and comfortable working across different teams. You don't need to be a developer, but you do need enough technical understanding to have sensible conversations with developers and explain what's happening to people who aren't technical. You'll need to be comfortable asking questions, chasing actions and keeping track of several projects at once. Most importantly, you'll take ownership. If something needs Development input, you don't just send an email and consider the job done. You follow it through.