northernscope process
northernSCOPE™ is a proven method for managing contracted software development between customers and suppliers. The method originally was developed in Australia (southernSCOPE). Later it was improved and formalized by the Finnish Software Measurement Association (FiSMA) and named northernSCOPE™..
northernSCOPE™ combines contracting unit pricing (cost per function point) with an active control of scope in terms of requirements, budget and timelines.
northernSCOPE™ projects show a cost per function point
of 35% compared to traditional projects. Large software
development projects using northernSCOPE™ show an
even better performance of a cost per functionpoint of
22% compared to traditional projects. Software development projects that use the northern-
SCOPE™ method have shown a decrease in ICT project
cost and schedule overrun to an astounding average of
around 3%.
(source: southernSCOPE and northernSCOPE™ research
using ISBSG database 2005-2007)
northernSCOPE is based on unit pricing of software and embraces the following twelve concepts:
- Customer driven requirements lead to hiring Certified SCOPE Manager
- SCOPE Manager organizes and subdivides "program of work" into standard "projects"
- Early functional size estimate of component software projects (as appropriate)
- SCOPE manager and customer analyze quality requirements
- Customer issues RFP for software and systems development
- Customer selects supplier based on agreed upon unit cost per software function point
- Requirements specification developed with customer and supplier
- SCOPE manager baselines Functional Size of software components and product development commences
- Change management done based on unit cost / FP as agreed
- SCOPE manager quantifies and reports project progress
- Project completed, customer pays based on FP delivered and agreed
- Final project experience data collected and stored
Projects using the northerSCOPE process enjoy many benefits, such as:
- No more Lose-Lose fixed price contracts
- Flexibility for customers to enable needed changes
- Supplier pays for work done controlled by the customer
- Both customer and supplier satisfaction increases dramatically with improved communication
- The software development process becomes fair for both parties
- Project is baselined at completion of requirements, at points of change and again at project end
- Lessons-learned are collected in knowledge database
