Methodology - a formula for success

We are flexible and can work with a customer’s in-house methodology or way of working, be it classic waterfall, DSDM, RUP, pure RAD or any hybrid or variation. We won't impose our way of working unless that's what you want, but there are certain levels of specification for baseline control that you will get as standard.

Where a customer hasn't mandated their own, we use one of our three custom in house methodologies to control how we deliver services. These are based on proven techniques and processes used by the Luminary team on many previous projects:

ProForma

Systems Integration (SI) waterfall/prototyping hybrid
Requirements Analysis, Design, Build, Test, Release
Workshops, flexibility for creativity, early stakeholder feedback, strong baseline control - No Surprises
Integrated design patterns, standards, libraries and templates
Appropriate for legacy/existing system integration or Green Field build

SystemCare

Support and maintenance methodology
Structures project initiation
Formalises SLAs and metrics

Project Management Methodology

Standard approach to planning, managing and controlling projects
Structures the project stages of set-up, delivery and closure
Regular and open customer reporting - No surprises

ProForma structures projects using a variety of techniques chosen as appropriate to each customer and project. These techniques provide for both the careful control and defined stages of the waterfall approach, and for more iterative approaches including time-boxing. Within each stage, prototyping and workshop techniques are used, together with use case analysis, object modelling and traditional entity and process design. Reusable testing outputs are also produced, not only to prove the system but also to highlight possible regressions as later phases are implemented.

For integration projects, a clear understanding of the impact on existing operational systems, both in terms of performance and functionality is factored in early. This ‘reverse engineered understanding’ of existing systems, supported by tools as well as process, is also an important factor in support and maintenance.

SystemCare is a support and maintenance methodology which has rigour and process in the traditionally risky area of defining Service Level Agreements (SLAs). There must be no misunderstandings nor surprises for any of the stakeholders.

The project initiation stage formalises the process whereby a clear understanding of the system to be supported is achieved so that appropriate SLAs and metrics can be defined. After the service has been defined, any agreed infrastructure can be implemented and knowledge transfer and service delivery can commence, with service being reviewed to an agreed schedule or milestones.

Project Management Methodology defines a standard approach to planning, managing and controlling projects, consisting of Project Set-up, Project Delivery and Project Closure.

During the Project Set-up stage, the Project Manager, in conjunction with the customer, creates the Project Initiation Document. This describes how the project will be run, and includes the project plan, a definition of the deliverables and milestones, the resource requirements for the project, and also defines the project control and reporting mechanisms.

During Project Delivery we Plan, Execute and Control the project, monitoring issues and risks and communicating progress back to the customer.

The Project Closure stage provides confirmation from the customer that the system has delivered on their business objectives, and ensures that we learn all the lessons we can from the project to feed back into the next one.

	About us
	Propositions
	Team
	Philosophy
	Past Projects
	Customers & Quotes
	Partners
	Press
	Methodology
	Technology
	Contact
	Links