Project Management Methodology

The Lead Up Software project manager has responsibility and accountability for delivering a successful business outcome for our clients. This includes, but is not limited to:

	Providing the client project manager with a single point of contact for all matters associated with the project
	Establishment of the Lead Up Software project team and development environment
	Development of project level documentation (e.g. project plan)
	Managing the project through all stages (e.g. requirements specification, design, development, system testing, user acceptance testing).
	Ensuring engineering quality processes are followed during the course of the project (e.g. documentation reviews, design reviews, code reviews, system testing requirements, release notes, configuration management, issue management, etc)
	Tracking and reporting on project status to the client through weekly team meetings
	Managing change requests from the client

Lead Up Software has a comprehensive project management methodology that it uses to manage all customer and internal software development projects. The project management methodology has been certified as conforming to the requirements of the ISO 9001 standard for software development. The Lead Up Software Project Management methodology is made up of the following modules:

	Project start up
	Project planning
	Project tracking and reporting
	Contract management
	Managent of customer communications
	Project team management
	Subcontractor and supplier management
	Project closure

In addition, Lead Up Software uses a standard project environment and project filing system for all projects. This includes the use of a standard set of basic tools including:

	Timesheet recording and reporting
	Defect and issue management, recording, and reporting
	Planning and scheduling
	Risk assessment models
	Project checklists and standard project document templates

Techniques used to control, monitor, and manage projects include:

	Regular project status reviews with the client project manager
	Organising the project team into areas of responsibility (sub-teams)
	Use of highly skilled team leads for the sub-teams
	Regular internal project reviews for identifying issues and actions and for tracking progress against the schedule
	Design reviews and code reviews
	Mandatory monthly project reporting to Lead Up Software management covering risks, progress against key milestones, resource usage, and financial status
	Agreed project functional specifications and acceptance tests

Testing Methodology

Lead Up Software's default testing methodology consists of three levels of testing as follows:

• Unit Testing - Provides verification against the Detailed Design

• Integration Testing - Provides verification against the High Level Design or System Architecture

• System and Acceptance Testing - Ensures that the project requirements have been met

At each testing level, a test plan is produced that:

	Outlines the overall testing approach,
	Describes how the approach will meet the project and QA goals,
	Gives the traceability matrix back to the appropriate specification document,
	Identifies the test cases to be used, and
	Describes the tools and techniques required to implement the test cases

The test cases themselves are also described in detail in the test case specification documents. Where possible, an automated testing approach using a set of baseline data is developed for each test case. When defects are found, they are entered into the Issue Management System where they can be tracked and resolved. For each test conducted, a test log is produced which outlines the test conditions, execution details, and test results.

Repeatability of testing is achieved through a combination of controlling test plans, system configuration, and baseline data used in testing and the configuration of the automated tests themselves. The test suites, test data, and test environment is subject to the same tight configuration management control as the software itself.