Methodology
A survey of 60 MIS directors revealed that the biggest cause of failures on software projects was the choice of methodology
Why KCS
What We Do
Products
Latest Update
Methodology
Every project has its unique set of requirements and nuances. The project in question may be a new development, existing project migration, technical administration, offshore / onsite development etc. Each and many such situations will demand that we look at it uniquely. Though a typical scenario in offshore development is something like -
- Initiation
- Scope / Project signoff
- Team identification
- Communication setup
- Knowledge acquisition
- Environment replication
- Project plan and scheduling
- Project plan signoff
- Offsite project execution
- Constant project review and milestone acceptance
- Implementation
- Technical support
Risk management approach
Wherever possible we apply our standard fixed price / fixed time model which lets us do the risk sharing with our clients. We stand by our budget and time commitments.
- Clear communication protocol setup
- Due approvals at all stages
- Effective issue management
- Breaking of entire project into smallest possible work units (tasks and sub-tasks). Managing, tracking them for constant review and action
- Continuous project review with onsite team for complete synchronization and mitigate any surprise element
General project practices
- Version control
- Backup of source code and document repository on a daily basis
- Well-defined issue management approach
- Documentation for easy project knowledge transfer, implementation, deployment, usage
- Adherence to general and project specific quality guidelines
- Testing against planned and documented test cases and scenarios
