Development & Integration
This phase is involves the development and QA team working together with the Product Owner.
Keeping your project on track
We employ simple yet effective agile project management. The basis of any project is a process called Scrum, a lightweight, iterative and incremental framework for managing complex work. Scrum meetings are held regularly, issues are identified rapidly and changes are communicated timely to the team.
Your project requires a realistic development plan and schedule. Based on industry’s best practices, we will:
- tackle most important tasks first, as they tend to surface risk which can be addressed early in the project
- work in sprints, with frequent deliverables
- track the progress weekly to ensure project’s schedule, team’s velocity
We believe communication is the key in delivering excellence, this is why we will propose to update you on a weekly basis, either via a show and tell session or via our weekly documentation.
This phase is split into multiple sprints, each usually taking about 1-2 weeks. At the end of each the team will produce a release of the code which will be distributed to everyone involved. The code is then tested by QA team to ensure quality and released to Staging environment for client review. The Product Owner is notified when a new release and
What is integration
Your project will most likely consist of various components linked together. Software (or System) integration is the process of bringing together various types of software sub-systems so that they create a unified single system.
Integration usually starts early in the project, in order to allow developers to build working releases. If a sub-system takes longer to build, the developers may create a mock service, that mimics the behaviour of real service in controlled ways. This is especially useful when testing needs to be done early.
Why Quality Assurance is important
Quality assurance (QA) is one of the most important processes during software development, preventing mistakes and defects in software products and avoiding problems when delivering products or services to customers.
QA planning starts early, usually during the discovery phase, where testing requirements, a testing plan and testing solutions are outlined. The QA analysts will take these further, working closely with the developers and ensuring features are tested on timely basis. Any detected issues will be logged in the system and fixed early.
Will I get involved?
Yes, it is very likely that you will need get involved in the development phase. Or you could choose to assign all duties to someone in your team as a Product Owner (PO). The PO is seen as the client’s official representative.
We will need input and direction from the PO, specifically with regards to:
- Managing Product Backlog, or a prioritised list of requirements for future iterations (sprints)
- Any changes in prioritisation of tasks, or decision with regards to scope creep
- Being available to the development and QA teams at all times to answer any questions with regards to customer needs and customer vision on how to implement product features
- Decisions whether to go live
What about infrastructure
Infrastructure comprises all the components required to operate and manage IT environments. These components include hardware, software, networking components, and data storage, all of which are used to deliver IT services and solutions.
Infrastructure requirements are defined during the discovery phase. Depending on these requirements, the infrastructure can be managed by the customer, or can be setup and managed by Atomate. We will discuss your requirements and advise the best course of action early in the project.
How will the product be managed further?
Once the project is stable and product is ready to be shipped, we can provide further maintenance, monitoring and support, as required.