Our Development and Project Management Processes
Canvas Intelligence's Development Process
At Canvas, we prioritise governance in our development process, ensuring responsible data management that complies with regulatory standards.
Version control is key, providing an audit trail for every stage of the development process (from requirements gathering to deployment) ensuring transparency, traceability and accountability. We integrate DevOps practices with GitHub to track changes, collaborate effectively, and maintain a history of all modifications, reducing the risk of errors or conflicts.
Our DevOps governance ensures standardised processes, automation, and reliability in all our projects. Our clients achieve greater agility, faster time-to-value, and improved quality in their BI solutions.
Our robust and scalable enterprise architecture provides our clients with a solution that will last decades, and can evolve and adapt to changing business requirements without major disruptions.
1. Requirements Gathering
Our development process initiates by collaborating with our client to gather detailed requirements, including any constraints.
2. Design
Developers create the user stories, start coding within the DevOps framework based off pre-developed solutions, and regularly commit code changes to the GitHub repository.
3. Development & Testing
Once the code is reviewed and approved, it is deployed to production. SQL databases are updated, ensuring that each run of the process utilises the latest code, delivering updated features to clients. Data Factory plays a central role, orchestrating pipelines to facilitate the smooth flow of data and processes.
4. Deployment
Developers iteratively modify, test, and align their code with the specified requirements, utilising continuous integration (CI) for seamless updates.
5. Review
Continuous review ensures smooth operation and that issues can be swifty rectified, should they arise. Our entire development framework is structured on the Medallion Architecture, ensuring effective change management and the long-term stability of our product.
Canvas Intelligence's Development Process
At Canvas, we prioritise governance in our development process, ensuring responsible data management that complies with regulatory standards.
Version control is key, providing an audit trail for every stage of the development process (from requirements gathering to deployment) ensuring transparency, traceability and accountability. We integrate DevOps practices with GitHub to track changes, collaborate effectively, and maintain a history of all modifications, reducing the risk of errors or conflicts.
Our DevOps governance ensures standardised processes, automation, and reliability in all our projects. Our clients achieve greater agility, faster time-to-value, and improved quality in their BI solutions.
Our robust and scalable enterprise architecture provides our clients with a solution that will last decades, and can evolve and adapt to changing business requirements without major disruptions.
1. Requirements Gathering
Our development process initiates by collaborating with our client to gather detailed requirements, including any constraints.
2. Design
Developers create the user stories, start coding within the DevOps framework based off pre-developed solutions, and regularly commit code changes to the GitHub repository.
3. Development & Testing
Once the code is reviewed and approved, it is deployed to production. SQL databases are updated, ensuring that each run of the process utilises the latest code, delivering updated features to clients. Data Factory plays a central role, orchestrating pipelines to facilitate the smooth flow of data and processes.
4. Deployment
Developers iteratively modify, test, and align their code with the specified requirements, utilising continuous integration (CI) for seamless updates.
5. Review
Continuous review ensures smooth operation and that issues can be swifty rectified, should they arise. Our entire development framework is structured on the Medallion Architecture, ensuring effective change management and the long-term stability of our product.
Canvas Intelligence's Project Management Process
What is critical to Canvas is our speed to market, our accuracy, and the quality of our work.
Given that, we have chosen to utilise the Agile Methodology which is best described as an iterative approach to project management and development that helps teams deliver value faster.
Instead of betting everything on a “big bang” launch, an agile team delivers work in small, but consumable, increments. Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly.
Canvas Intelligence's Project Management Process
What is critical to Canvas is our speed to market, our accuracy, and the quality of our work.
Given that, we have chosen to utilise the Agile Methodology which is best described as an iterative approach to project management and development that helps teams deliver value faster.
Instead of betting everything on a “big bang” launch, an agile team delivers work in small, but consumable, increments. Requirements, plans, and results are evaluated continuously so teams have a natural mechanism for responding to change quickly.
Scrum
As a key element of the Agile Methodology, we deploy through an agile project management framework called Scrum. This framework helps teams structure and manage their work through a set of values, principles, and practices. Scrum encourages teams to:
- Learn through experiences
- Self-organise while working on a problem
- Reflect on their wins and losses
- Continuously improve
Sprints
Using the Scrum framework, a product is built in a series of iterations called Sprints, that break down big, complex projects into bite-sized pieces. In other words, a short, time-boxed period when a Scrum team works to complete a set amount of work.
Sprints are at the very heart of scrum and agile methodologies, and getting sprints right will help your agile team ship better software with fewer problems.
Sprint Planning
Before commencement, we set up the sprint. We determine how long the time box is going to be, the sprint goal, and where we will start. The sprint planning session kicks off the sprint by setting the agenda and focus and essentially addresses the following elements:
How it Works
Each month will represent a sprint to deliver on the agreed-upon goals.
Capacity will be assigned to the planned work and brought into the sprint.
Each Sprint will start and end with a Ceremony with the following outlined agenda:
Scoping, Planning and Delivery
Planning is done on Microsoft Azure DevOps. All work is planned in Epics, Features and User Stories. Tasks are created in executing the work.
Development
The execution of the planned work by the developers as per the User Stories. Tasks are used to indicate what is being worked on. DevOps Github integration is used to keep a repository of all code in the system.
Support
Support is allocated to attend to bugs and errors picked up after testing and delivery.