Chat with us, powered by LiveChat

Development Process

Our main development framework is Scrum. We organize our work in sprints (two weeks usually), maintain a backlog, and do daily Scrum meetings. We anticipate that the Product Owner will take the lead on backlog creation while Scrum Master helps him to do it properly. Typically, we use Concourse continuous integration server to deliver software.

Our Product Development Cycle looks like:

image description

The Scrum Roles

Within the Scrum Framework, the main three roles are defined:

Scrum Master

It is a person who is responsible for facilitating the Development Team and the Product Owner to work on the day to day development activities.

Product Owner

It’s a person with the project vision who breaks down the project into tasks and then prioritizes them, so everything meets the objectives and goals of the customer, market, and organization.

Scrum Team

These are the people who execute the project. They are autonomous, self-directed, and each has a unique set of skills that address the needs and the project and will work together with the whole team.

Our Role

We can take over from our customers’ tasks or project part or even the whole project.

There are 3 types of team we can gather for your project:

The Scrum Team

  • We provide with a team consists of:

    A Scrum Team consisting of 3-7 self-organizing and cross-functional developers.

  • We ensure:

    Assisting with an initial backlog creating;

    Taking responsibility for tasking and providing the estimates;

    Implementing effective QA management;

    Delivering a potentially releasable increment of “Done” product at the end of each Sprint.

  • We expect that you will:

    Manage the backlog;

    Reach product goals;

    Check and accept the sprint results;

    Facilitating Scrum events;

    Manage the process.

The Scrum Team + Scrum Master

  • We provide with a team consists of:

    A Scrum Team consisting of 3-7 self-organizing and cross-functional developers;

    A Scrum Master.

  • We ensure:

    Assisting with an initial backlog creating;

    Taking responsibility for tasking and providing the estimates;

    Implementing effective QA management;

    Delivering a potentially releasable increment of “Done” product at the end of each Sprint.

    Managing the process;

    Defencing the team from useless interactions to maximize the business value created by the Scrum Team;

    Facilitating Scrum events whenever requested.

  • We expect that you will:

    Manage the backlog;

    Reach product goals;

    Check and accept the sprint results.

The Scrum Team + Scrum Master + Product Owner

  • We provide with a team consists of:

    A Scrum Team consisting of 3-7 self-organizing and cross-functional developers;

    A Scrum Master;

    A Product Owner.

  • We ensure:

    Effectively collaborates with the Stakeholders and the Scrum Team;

    Managing product backlog;

    Reaching product goals;

    Check and accept the sprint results;

    Assisting with an initial backlog creating;

    Taking responsibility for tasking and providing the estimates;

    Implementing effective QA management;

    Delivering a potentially releasable increment of “Done” product at the end of each Sprint.

    Managing the process;

    Defencing the team from useless interactions to maximize the business value created by the Scrum Team;

    Facilitating Scrum events whenever requested.

  • We expect that you will:

    Be glad about the product we deliver.

The Procedure of Product Release

AnvilEight uses CI/CD pipeline to deliver bug-free code at high velocity. A CI/CD pipeline helps us to automate steps in the software delivery process, such as initiating code builds, running automated tests, and deploying to a staging or production environment. Automated pipelines remove manual errors, provide standardized development feedback loops, and enable fast product iterations.

Continuous Integration (CI) is a DevOps software development practice which lets developers merge code changes into a central repository, after which automated builds and tests are run.

Continuous Integration brings benefits, such as:

  • Fewer gaps between integrations;
  • Increase visibility enabling greater communication;
  • Catch issues early and fix them before they grow;
  • Spend less time debugging and more time adding features;
  • Stop waiting to find out if your code's going to work;
  • Reduce integration problems allowing you to deliver software more rapidly.

Continuous Delivery (CD) is the natural extension of Continuous Integration. It's an approach in which teams ensure that every change to the system is releasable and can be released by pushing a button. It gives the ability to get quick feedback on what users care about.

There are benefits of using Continuous Delivery:

  • Releases become smaller and easier to understand;
  • No needs to drop work to make a deployment because everything is automated;
  • The feedback loop with customers is faster: new features go straight to production when they're ready.