MODELS
Development Models
Project Life cycle development model descriptions should help in the selection of appropriate model for the project execution. Usually customer requirements are the basis for model selection. Project life cycle consist of stages. Stages should produce outputs which can be used as inputs for the next stage. At our company the following software development models are used: Waterfall and Incremental.
- Waterfall Model
Waterfall model is used for projects with well defined requirements. All functionality needed for project defined at the beginning of the project. Outputs from one stage are inputs for another stage. In general we have the line motion from the beginning to the end of the project.
Project Life Cycle for the Waterfall model usually should have the following stages:
- Requirement Development
- Designing• Development
- Verification• Deployment
- Maintenance
After the Start of the project at the Requirements Development stage customer requirements should be collected and formalized. So they should be a solid basis for the whole project. At the Designing stage design documentation based on requirements should be developed. At the Development stage project team members use design documentation to produce the build for the verification. At the Verification stage the build received from the Development Team should pass appropriate verification to be sure that requirements implemented correctly and product satisfy to customer requirements. Customer verification before Deployment stage is also required step. After the verification stage the project going to Deployment stage. At the Deployment stage product should be deployed for production usage. After Deployment stage project moving to the next stage – Maintenance. At the Maintenance stage issues received from production usage should be resolved and customer enhancements for the next project version should be collected. After Deployment stage project should be considered as Finish of the project.
- Incremental Model
Incremental model is the second model widely used across the company for Software Development projects. Incremental Life Cycle Model is used for projects with poor requirements or non completed requirements. Development is performed by iterations (2-4 week cycles).
At the Start of iteration customer provides only the requirements for the current iteration and general product vision. Iteration is planned according to scope of iteration requirements and each iteration includes design development/evolution and verification. Results of the first iterations are used to adjust the requirements of the next iterations. Iterations continue until the customer is satisfied with results and decides to move for Deployment. Deployment and Maintenance stages are the same as for Waterfall model.
Cost Models
Cost model is selected at the sales stage of the project. Decision depends of the customer requirements and other negotiations with the customer. Project proposal and later contract defines selected cost model conditions.
- Fixed Cost
Fixed cost model is used for projects with well defined requirements. Requirements can be provided from the customer or developed in house. Labor estimates are provided based on the requirements.
- Time&Material
Time&Material cost model is used for projects with ill requirements. Customer produces requirements during product development stage. The time period for next portion of the requirements should be negotiated with the customer – every month, quarter or other time period.Also customer can decide to have higher control to the development process and use this cost model. Next part of the requirements can be received after revision of the previous version of the product. This cost model is often used for pilot or prototype projects with the new customer. Customer can request preliminary estimates for defined portion of work before start of work.
- Time&Material with Cap
The Time&Material with Cap cost model is very similar to Time&Material cost model. The difference is that in the case of usage Time&Material with Cap cost model customer has own limitations in budget for the project. When budget for the project is over the customer should decide to continue with additional budget or finish the project.
- Fixed Team
Fixed Team cost model is variant of the Time&Material model when size of the team is fixed. This model is used for long term projects. Customer decides to pay for a predefined number of resources for a period of time. Customer provides requirements to the development team at a periodic basis.
Project Management Models
- Broncoway Management – Broncoway performs all processes according to Broncoway policy under Broncoway management.
- Customer direct management – Broncoway employees work in customer teams and all management up to tasks planning is responsibility of the customer
- Customer process implementation – Management (Project Management and Team Management) is performed by Broncoway but all basic processes (for example, Requirements Management, Verification) are implemented (or not implemented) according to customer requirements.
