Introduction

You don’t become one of Canada’s most experienced and trusted provider of exceptional custom software solutions without learning a few valuable lessons along the way.

Fortunately for you, we’ve fine-tuned our process into a step-by-step playbook that efficiently and effectively guides the design, development, and ongoing support of every software solution we create.

Here’s the Agency Atlas Playbook.

Phase 1 - Design

Whether we’re developing new applications or building new features for an existing application, we begin with a robust design and prototyping process:
Design Discovery

1

Design Discovery

2

Design Discovery

3

Design Discovery

4

Design Discovery

5

Step 1 - Design Discovery

Our design phase begins with an in-depth discovery process where we work closely with you to  understand your goals and ensure we are on the same page regarding the full scope of your project.

While the work we do is technical, everything we do in business relies on clear and concise communication. We embrace the opportunity to remain transparent throughout, so you know the why and when behind everything we do for you. 

The discovery process involves an in-depth kickoff meeting with our design team and your key stakeholders where we clarify the history and future for your project. We recognize that clients come to us at different stages of their development process so it’s important to evaluate progress to-date before planning the roadmap to completion. 

Once that roadmap is understood, we create a series of user personas to clarify the unique types of potential users, what motivates them, and what their user experience preferences may be. 

Step 2 - Technical Discovery

Many of our projects start with a multi-part technical discovery engagement to either understand and document your existing software stack or research and recommend the right technologies and architecture for your project.

This technical discovery can include conducting an in-depth code review on your existing application, researching technology options for your specific use case, reviewing documentation for third-party integrations, creating a DevOps strategy, and more.

Step 3 - User Experience Design

Our UX design process ensures that we are solving user's needs efficiently, and creating an application that is easy to use and understand.

Feature Map

To start, we create a feature map - a high level view of the features of your application. It serves as a starting point for closer examination of how the views will interact, and is maintained and updated throughout the life of the project.

User Flow

Next, we'll build User Flows to demonstrate the steps users will take to achieve specific goals. User Flows become especially important when dealing with complex conditional workflows. It allows clients, designers, and developers to share a mutual understanding of how features will work and what feature outcomes will be.

Wireframes

As a final step, we'll create wireframes of the primary views of the application. Wireframing allows us to create the general layout of the screen without having to decide on the exact text and imagery that will be used in the final designs. It's useful for:

Rapid Prototyping

Rapid Prototyping

Rapid Prototyping

Rapid Prototyping

Rapid Prototyping

Step 4 - User Interface Design

Once Discovery and UX Design are complete, we move to visual design, first by iterating on and selecting a style concept, then turning the selected concept into a style guide, and as a final step, creating high fidelity mockups of each view of the application.

Phase 2: Develop

Our development playbook outlines our proven methodical approach to building iOS, Android, and web apps, ensuring you know what to expect along the way.

Pre-Development Planning

1

Pre- Planning

2

Launch

3

Step 1 - Pre-Development Planning

Pre-development planning ensures an effective and efficient development process. This involves assigning the best-fit development team, completing the step-by-step design to development handoff, establishing next stage milestones, creating stories, and planning sprints.

Assigning the Team

Our development teams include six professionals: two full-time senior developers, one part-time project manager, one part-time quality assurance professional, one part-time designer, and a product owner.

Our wealth of experience allows us to choose a team that is well-versed in your project’s area of need, and we take pride in choosing the right-fit for your project.

oval

Slavcho Karbashewski

CEO

oval

Slavcho Karbashewski

CEO

oval

Slavcho Karbashewski

CEO

oval

Slavcho Karbashewski

CEO

oval

Slavcho Karbashewski

CEO

oval

Slavcho Karbashewski

CEO

Design to Development Handoff

Our development teams include six professionals: two full-time senior developers, one part-time project manager, one part-time quality assurance professional, one part-time designer, and a product owner.

Our wealth of experience allows us to choose a team that is well-versed in your project’s area of need, and we take pride in choosing the right-fit for your project.

Assigning

Our development teams include six professionals: two full-time senior developers.

Our wealth of experience allows us to choose a team that is well-versed in your project’s area of need, and we take pride in choosing the right-fit for your project.

Create Stories

Our development teams include six professionals: two full-time senior developers.

Our wealth of experience allows us to choose a team that is well-versed in your project’s area of need, and we take pride in choosing the right-fit for your project.

Stories

Our development teams include six professionals: two full-time senior developers.

Our wealth of experience allows us to choose a team that is well-versed in your project’s area of need, and we take pride in choosing the right-fit for your project.

Step 2 - Active Development

Once the pre-development planning is completed, active development begins.

This stage includes completing two-week sprints, conducting retrospectives at the end of each sprint, and launching version releases based on project milestones.

Sprint Execution Begins

Developers are assigned a number of stories for each two-week sprint, complete with an estimated number of hours to complete. Each story includes a detailed description of what to build, as well as links to required assets, and acceptance criteria.

Sprint Execution Begins

Developers are assigned a number of stories for each two-week sprint, complete with an estimated number of hours to complete. Each story includes a detailed description of what to build, as well as links to required assets, and acceptance criteria.

Sprint Execution Begins

Developers are assigned a number of stories for each two-week sprint, complete with an estimated number of hours to complete. Each story includes a detailed description of what to build, as well as links to required assets, and acceptance criteria.

Step 3 - Launch

Once all version releases are completed and accepted by the client, the app is ready for beta testing, and eventually, a public (or internal) release.

After the public release, the app moves to either maintenance mode or continued development.

Phase 3: Maintain

Once the application goes live our support team provides ongoing service via a maintenance agreement and/or ongoing active development agreements.

Maintenance Agreements

For applications with limited development plans for the future, a maintenance agreement is all that's required to keep the app running well. Our maintenance agreements cover the following:

Error Monitoring & Bug Reporting

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Error

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Bug Reporting

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Error Monitoring

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Maintenance

For applications with limited development plans for the future, a maintenance agreement is all that's required to keep the app running well. Our maintenance agreements cover the following:

Error

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Bug Reporting

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Error Monitoring

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Agreements

For applications with limited development plans for the future, a maintenance agreement is all that's required to keep the app running well. Our maintenance agreements cover the following:

Error Monitoring & Bug Reporting

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Error

We use several third-party tools for error monitoring and bug reporting, including CodeClimate, Eslint, Sentry, and bugsnag. These tools alert us when something goes wrong, and help optimize performance.

Your Search is Over - Let’s Start Developing

Lorem ipsum dolor sit amet, consectetur adipiscing elit. In efficitur ultricies accumsan. Morbi et congue lacus. In hac habitasse platea dictumst.