Sybu development methodology utilizes some aspects of Agile development and some traditional but best summarized by the following:

• URS.  User requirement specification is required for development.
• WBS. The work breakdown structure is determined
• Software work units is created and assigned to resources.  On larger projects this may be preceded by a Business analysis phase.
• Simulators.  For engineering related projects, software simulators is created where possible. Although this creates an extra development item, it helps in reducing costs in reducing off-site development/integration time, travel and subsistence.
• UAT. User acceptance testing documentation is generated, and utilized for sign-off
• Bug tracking, Issue, Ticketing system.  This system is used to track all software work units, and reported issues.
• Timesheet.  On some projects time is tracked for billing purposes.
• Version Control   All software, documentation, installers, help files  is under version control
• Backups. Onsite and to online servers
• Naming conventions.  All files, software source, documentation follows specific naming convention.
• Software release versioning.  Releases are versioned. Versions are under version control.
• Release notes.   Software releases are accompanied  by release notes with reference back to Issue numbers tracked.
• Milestone/ functional releases.  Software is broken down into functional milestones which are released. This allows quick client feedback for integration back into development.  It engages the end-user/client  at earliest possible time.
• Testing. is performed in house, followed by testing at partner's lab (where applicable) and UAT.