Nortec’s project methodology is built from the Microsoft Solutions Framework. Nortec has developed a five-phase solution delivery model that covers all aspects of an engagement. Each phase is mapped to a schedule of milestone-based deliverables, charting progress against the overall solution scope.

This methodology improves the structure and integrity of Nortec solutions, while providing all parties involved with a standard reporting and status mechanism.

Envision

Current State Assessment - documentation of an accurate description of the environment and its corresponding variables in which the solution will reside. This is a living document to be constantly updated and used for reference

Vision and Scope Document - The Vision/Scope document represents the ideas and decisions developed during the envisioning phase. The goal of the phase, represented by the content of the documentation, is to achieve team and customer agreement on the desired solution and overall project direction

Project Scope Document - defines the approach the team will take in organizing and managing the project. It is the strategic representation of initial decisions made regarding goals, work scope, team requirements, team processes, and risk.

Plan

Master Project Plan - Master Project Plan is the document into which all subsidiary plan are synchronized and presented together as a single plan. This document f acilitates an understanding of the overall approach to the project, facilitates reviews and approvals and helps identify gaps and inconsistencies

Subsidiary Plans – Communication Plan, Backup & Recovery Plan, Budget Plan, Deployment plan, Support Plan, Training Plan, Pilot Plan, et al. These plans break up the project into manageable functional aspects.

Develop

Testing Report - This document will be used multiple times at frequent intervals during the development, testing, and stabilization phases. For example, during a six-week build phase, the test team might submit this report weekly, or six times during the build phase; however, the team might submit the report bi-weekly during the stabilization phase.

Traceability Audit - Documents the processes of 1) comparing specifications to what was actually developed and plans to actual events, 2) identifying if and where change control process broke down, and 3) determining the cause of all variations and deviations. The comparison process focuses on Functional Specification and the Master Project Plan and looks at what occurred in the development phase and how that was different than planned

Stabilize

Test Specification – The technical outline for conducting the testing process. It defines the input, output, environment, and procedural guidelines at the solution level as well as for each test case. The Test Specification is developed using the framework of the Test Plan (created during the Planning Phase) and the contents of the functional specifications.

Validation - records the results of the process that validates that what is delivered during the pilot meets specifications and business requirements. Provides valuable insight into the solution’s value. If the development and testing activities rigorously followed the specifications and design, the pilot should go smoothly.

Deploy

Project Close-Out Report - the project’s epilogue. It records the comparison between the initial intent of the project and what the project actually delivered. It also records the closing of all remaining open issues, documents any significant changes that occurred in the project during the development and solution deployment, and provides information on the vision for future projects. This is not an evaluation document – the final project analysis is recorded in the Post Project Analysis document.

Post-Project Analysis - document records the results of conducting a depth and breadth assessment of the project from its inception (envisioning phase) to completion (deployment phase). This assessment captures successes, challenges and failures, and identifies what should have been done differently on this project and what could be done differently for the next project.