Projects have different sizes depending on hours needed, people involved, budget etc.
In the smallest projects, where we have a standard plug and play installation, the number of processes and activities is slimmed. From contract signing and given hardware availability, you could have solution in production within a few working days. Even if the project processes are limited and with short lead time, you will go through the classic project steps:
- Contract
- Installation
- Test
- Production
- Hand over to support
For larger projects that require customization of the application, set and dedicated project organization, customer specific integration the project process will require more time.
Analyze and Planning Phase
In order to start the development or installation, the requirements need to be defined.
For larger projects with specific Customer demands, KSD writes a Solution Design when the Business Requirement Specifications analysis has been finalized and agreed.
The project organization and steering groups are established, the Work Breakdown Structure (WBS) is set, critical elements during software development/customization are discussed, communication plan and reporting structure are defined etc.
Develop Build Phase
KSD has two different development/customization teams:
- One team is responsible of the configuration/customization layer. This is the team that is the expert on the customer business and implementing the business need to KSD CWW in the Configuration Layer. (By Configuration Layer we mean that part that may be changed without influenced by a release of a new software version meaning having an optimal Version Release Control (VRC).)
- The second team is the development team. The development team handles changes in the core of the application, which sometimes is required to fulfill the customer’s business need. This team mainly uses Rational Unified Processes.
Both teams adopt the extreme programming basics to secure best possible quality. Each module is tested separately before moving forward with the next. At the end of critical line is the UNIT test where we also secure that all modules are working properly and fulfill the set of requirements.
Deliver/Go-Live
In general the project team is 100% dedicated after go-live for up to one month to give best possible support and secure that all documentation is updated accordingly. During this time period the support organization is trained to be able to give required support according to the agreed SLA.
Closure
In general all larger projects ends with a closure meeting between all parties involved in the projects. The lessons learned are discussed and documented. From now the project is in support mode.