Development
Process

Our main development framework is Scrum . We organize our work in sprints, 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.

image description

Explanation

Scrum Roles

  • 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.

Choose your development process plan

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.
Scrum team
Master
Product owner
Scrum team
Master
Product owner
Scrum team
Master
Product owner
Team composition
3-7 self-organizing and cross-functional developers.
Scrum master
Product owner
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
Defencing the team from useless interactions to maximize the business value
Facilitating scrum events whenever requested
Reaching product goals
Check and accept the sprint results
Managing the process
Effectively collaborates with the stakeholders and the scrum team
Managing product backlog
Expect that you will
Manage the backlog
Reach product goals
Check and accept the sprint results
Facilitating Scrum events
Manage the process
Be glad about the product we deliver

Product Release

A CI/CD pipeline helps us to automate steps in the software delivery process. Automated pipelines remove manual errors, provide standardized development feedback loops, and enable fast product iterations.

AnvilEight uses CI/CD pipeline to deliver bug-free code at high velocity.
image description
Continuous Integration
CI

DevOps software development practice which lets merge code changes into a central repository, after which automated builds and tests are run

  • 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

Approach which ensure that system changes can be released by pushing a button. It gives the ability to get quick feedback on what users care about

  • 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