services that compliment our products



"Know what your customers want more and what your company does best. Focus on where those two meet." – Kevin Stirtz



The Bay Project Management Methodology





In the delivery of projects Bay Technologies applies its proven project delivery methodology. This methodology, based on the PMBOK (Project Management Body of Knowledge), forms part of the ISO9001 accredited Quality Management System that Bay operates within.

The Bay Project Methodology defines a clear definition of the project life-cycle phases and outcomes required from each. At a high level Bay defines the project life-cycle phases as:

  1. Envision
  2. Design
  3. Development
  4. Implementation, Handover and Closure




There is specific focus on complete project life cycle management at lower activity levels; from analysis and planning through to post implementation reviews and project closure. Bay has placed special emphasis on risk and issue management and mitigation strategies, these have been incorporated into the Bay project methodology.


The application of this methodology and all coordination of the project will be via Bay’s Project Office. The project office retains primary responsibility for communication, coordination and delivery, on-time and on-budget.


The project team, led by a Bay Project Manager, will consist of a multi-disciplinary team responsible for inception through to hand-over to Bay’s product support group.

During the envisaging phase the project management team will work closely with the customer to formalise the Project Management Plan by refining the areas of solution scoping, activity decomposition and risk. This will be through a number of workshops, meetings and other information gathering techniques to help Bay complete the picture of the customers’ culture, values and drivers for the project. Bay sees this activity as key to the success of the project.


Moving through into the Design phase, a senior business analyst will be assigned for the duration, conducting necessary workshop engagements, resulting in the production of the detailed configuration and customisation specification. At the beginning of this phase, the base Bay product will be implemented. This is part of our agile processes and is used to educate business representatives on the application. Our experiences have shown this helps facilitate and accelerate the refinement of requirements and product specifications.

The Design phase documents and agrees all processes and interfaces to a complete state, even when a phased delivery method is being used. A Bay User Acceptance Test (UAT) plan will be updated upon finalisation of the specification document.


The outcomes of the Design phase are passed to the Bay Engineering Team to execute the development phase. This phase covers the development of any product customisations and Bay’s own quality certification testing. During this phase, rigorous project management ensures the solution is delivered on time, on budget. Bay’s development approach is focused on supporting the chosen delivery model. The key outcome of each development cycle is to ensure each release supplies a production quality system.

Bay’s Implementation phase covers both the Product Release and Training components, handover to Bay Support as well as project closure. Change management resources are assigned to structure and deliver training supported by user and administration documentation. The Bay Release Management Team is responsible for product packaging, release and installation to the Customer. Handover to Bay Support provides the closure to product support and results in an internal briefing to tier 1 and 2 support regarding specific Customer changes.


Bay has applied this Project Management Methodology to deliver projects on time and on budget to many Federal, State and Local Government bodies throughout Australia.