To increase the speed and quality of software development, Global Brainforce encourages to use proven test and deployment automation and an agile process that assures clear requirements.
Software Development Process Best Practices
Core Activities of Software Development Process
- Specifications/Requirements – The team and other project stakeholders specify the core functionalities of the software they aim to construct, as well as the limits they want to impose on the process.
- Design and Implementation – The team creates and implements software projects based on a set of pre-defined specifications.
- Verification and Validation – This is the process by which the team ensures that the software being developed meets the specification and the customer needs defined in the business requirements.
- Maintenance and scaling – the team is responsible for maintaining, modifying, and scaling the software to suit the changing needs of consumers and markets.
GBF Software Development Best Practice
- Having a source code control system (in most cases we are using the customer’s system)
- Doing code reviews before checking in code
- Doing unit tests
– automated test framework and write repeatable unit tests
- Test-driven development (write a test before the program)
- Acceptance test driven development (Apply the acceptance tests once code is checked in)
Agile - Iterative Development Process
- At the start, the customer explains the expected functionality to the team. The business prioritizes business value and urgency. The team estimates the effort and cost.
- The team discusses the tasks to implement the functionality, details the estimation and team members select their tasks.
- During the iterations, the team holds short meetings to discuss current task achievements and issues.
- At the end of the iteration, the team demonstrates to the customer the increment of (the potential shippable) functionality.
Benefits of the Iterative Development Process
- Produce working software more quickly
- More flexible. Functionality can be added at the next iteration
- Efficiency – Less costly for changing requirements
- Collaboration – End users can give their feedback quickly
- Find errors and bugs early