Web development approaches

Our neatly organized web development process allows us to deliver topnotch, well-documented products faster

Django Stars
Processes

processes-img processes-img
Initial Phase
Preparation
This phase is mostly about communication and includes calls, personal meetings, and first estimations. While preparing we get information from the client about project goals and software requirement specification. Steps of Preparations.
Intro call with a client
Intro call with a client
Signing NDA and getting<br> project information
Signing NDA and getting
project information
Documents review and Q&A
Documents review and Q&A
Dev proposal and rough<br> estimates
Dev proposal and rough
estimates
A call to discuss proposal<br> and estimates
A call to discuss proposal
and estimates
Signing a contract
Signing a contract
Build a dedicated team and<br> start the development<br> process
Build a dedicated team and
start the development
process
Inputs
Project documentation provided by Client: specifications, wireframes, hypothesis, design, etc. (if there is nothing to provide, we also can conduct a pre-project stage for you)
Duration
Up to 5-10 days
Tools
Confluence, Jira, Miro
Outputs
Software development proposal and signed contract
Initial Phase
Discovery
We need to be on the same page with our client when we plan the web service development steps. That’s why we conduct a Discovery phase. We make it in person, so the team leaders can meet the client, get the information needed and clarify details.
This period is divided into 5 main stages:
Initiation
Discovery agreement sign-off.
Discovery agreement sign-off.
Agenda presentation, tools set up, detailed scheduling of activities and deliverables list polishing.
Execution
Workshops, Q&A sessions, discussions and deep subject area analysis that allow to create comprehensive pre-agreed documents including costs, timelines, and project roadmap.
Control
Discovery report preparation and presentation, meetings with CxO.
Development
Negotiating and setting up our future development approach.
The client gets access to our communication and tracking tools. Starting from the Discovery phase, he becomes an important and active part of the development team.
After creating precise estimations we start composing the developing team, provide it with a precise scope of work and plan a few nearest sprints.
discovery-after-img
Team
Project Manager, Business Analyst, Solution Architect , UX/UI Engineer, Quality Assurance Engineer
Inputs
Rough estimate, project artifacts
Duration
Up to 2-4 weeks
Tools
Jira, Confluence, drow.io, Nimbus, Gantter, Figma
Outputs
JIRA backlog, Roadmap (Gantt or PERT chart) and Work Breakdown structure, Precise estimations
Design Phase
UX/UI Engineering
We understand business needs. We understand user needs. Our UX/UI engineering is about creating an interface bridge between them, both efficient and satisfying. We organize it in the following way.
Build User Flow diagram
Build User Flow diagram
Sketching and Low-Fi<br> prototyping
Sketching and Low-Fi
prototyping
Creating wireframes to<br> approve the structure
Creating wireframes to
approve the structure
Creating a clickable<br> prototype to validate UI<br> solutions
Creating a clickable
prototype to validate UI
solutions
Creating a design from the<br> prototype
Creating a design from the
prototype
Design quality assurance
Design quality assurance
Creating specifications for<br> design implementation
Creating specifications for
design implementation
Inputs
User research, primary and secondary scenarios, competitor analysis
Duration
Up to 3-6 weeks
Tools
Figma, Adobe XD, Adobe Photoshop, Adobe Illustrator, Axure, Principle
Outputs
Product design ready for implementation
Development process phase
Software Development
We follow Agile methodologies of web development flow including Kanban and Scrum. For most projects, we use Scrum and can cover not only Developing Team and Scrum Master, but also a Product Owner role. Our Scrum team consists of a Project Manager/Scrum Master and Development Team.
10-daysSprint

Product backlog

~1-2d

  • Is a list of the new features,
  • changes to existing features,
  • bug fixes,
  • infrastructure changes or other activities

Grooming

Planning

Commitment

Sprint planning

  • Meeting at every Sprint start
  • All accepted items are recorded into the Sprint Backlog

Spring

  • Iterations within 10 days
  • All tasks are due at the end of the sprint
  • All committed code at the end of a sprint is shippable

Daily stand-ups

Sprint review

  • Tasks done and undone analysis
  • Backlog discussion
  • Resources review

Delivery (demo)

Retrospective

Release

Development process phase
DevOps

We follow DevOps as a set of development and cultural practices to get the most from working and communication processes.

DevOps is well-complemented with Agile since it expands and complements the processes of continuous integration and product release, ensuring the code quality and value. The culture of DevOps helps us to optimize resources, speed up the delivery and solve the problems as a team to get the best results.

We use DevOps development practices to achieve four main goals:

  • Shorten development lifecycle
  • Ensure the highest product quality
  • Stick close to product business objectives
  • Carry out a constant application monitoring
Tools
Jira, Confluence, Slack, Github, Jenkins, CircleCi
  • Gathering requirements
  • Task management
  • Scheduling
  • Creating roadmap
  • Code development
  • Code review
  • Code merging
  • Source code management
  • Continuous integration
  • Version control
  • Manual testing
  • Continuous testing
  • Testing in production
  • Changes management
  • Release automation
  • Continuous delivery
  • Infrastructure installation
  • Configuration and management
  • Capacity planning
  • Log/backup management
Inputs
User research, primary and secondary scenarios, competitor analysis
Tools
Figma, Adobe XD, Adobe Photoshop, Adobe Illustrator, Axure, Principle
Duration
Up to 5-10 days
Outputs
Product design ready for implementation
Post-release Phase
Post-release support and growth
We follow Agile methodologies of web development flow including Kanban and Scrum. For most projects, we use Scrum and can cover not only Developing Team and Scrum Master, but also a Product Owner role. Our Scrum team consists of a Project Manager/Scrum Master and Development Team.
Support Process
On a support phase, we provide our clients with:
  • Errors monitoring
  • Analytics and metrics tracking
  • Technical and business consulting
  • Updates and changes Implementation
We establish the technical and organizational collaboration standard between our team and the client. If there is a technical team on the client’s side, we also practice the mutual code review to ensure the highest result quality.
release-img
Tools
Sentry, ELK, DataDog, Grafana, Google Analytics, Facebook Pixel
release-img
Tools
AWS, Kubernetes, Docker
Scaling Process
During the process of scaling, we provide our clients with:
  • Analytics
  • Technical and business consulting
  • Changes implementation
We follow the Twelve-Factor app methodology allowing to implement an automatical scaling system and based on Docker and cloud services.