DB2 Limited
To help personalize content, tailor and measure ads, and provide a safer experience, we use cookies. By clicking or navigating the site, you agree to allow our collection of information on and off Facebook through cookies. Learn more, including about available controls: Cookie Policy.
bg-img

workflow

We are working according to the best standards what makes deliverables to our customers easy and understandable

  1. initiating

The initiating process determines the nature and scope of the project. This phase includes ascertaining the Stakeholder’s project requirements, and includes:

  • Project requirements (idea behind the project, overall goal, duration).
  • Roadmap (identify each different feature and module)
    1. analyze dependency between all the tasks
    2. classify each task
  • Allocate available resources.
  • Project schedule (milestones, important dates, deadlines).
  • Financial analysis of the costs and benefits, including a budget.
  1. planning
  • Select the project management methodology (scrum, agile, prince2 kanban).
  • Selecting the planning team.
  • Technical analysis (choosing the AWS/Heroku/DO/etc environments, microservices or monolith architecture, development languages and frameworks).
  • Estimating the development team resources and availability.
  • Estimating time and cost for activities.
  • Risk planning.
  • Creating a quality assurance plan.
  • Getting approval to begin work (Sign the contract).
  1. use cases

The goal of a user story is to deliver value to the client or internal team. Stories need to be written so it is apparent what needs to be addressed for the user story to be considered complete. This process includes writing a brief but clear description, and including links and/or screenshots to illustrate an issue, where appropriate.

For Jira tasks, we also include a list of acceptance criteria within the story, so the developer knows what is expected, and the person in charge of QA knows what to look for when reviewing it. Additionally, it's a good idea to include which team role the story pertains to. So, for example, the story could begin by stating, "As a customer..." so it's clear from the start who is expected to complete the task.

  • As a purchaser on the website,
  • I want the ability to pay with a credit card,
  • So that i may immediately confirm my purchase.
  • Acceptance criteria:
  • Accept Discover, Visa, MC
  • Validate CC# when entered
  • Validate expiration date and CVV
  • Validate billing address
  • Generate success and failure messages after processing
  • Definition of Done:
  • Passes all regression tests
  • Passes testing per acceptance criteria items
  • Approved by UI Team
  • Able to show feature in company demo

As you can see, the story description explains what needs to be done in a clear, concise manner, and then continues with a list of acceptance criteria that need to be met for the story to be considered complete. Again, it is useful to include a link to the referenced pages and/or a screenshot of the problem.

  1. ux

Creating low-fidelity prototypes is the crucial part of the development process. During this process, the UX designer creates a skeleton of the application with close attention to all the small features and possible exceptions.

  • Requirements analysis.
  • Research of similar systems.
  • What creating the UX includes: useful elements, usable elements, desirable modules, findable modules, accessible modules, credible module, a user journey simplification flow.
  • User journey simplification flow.
  1. ui

A useful and attractive UI is an essential elements of the product development process. Creating a visible UI for end users includes:

  • Market research and understanding the best UI practice.
  • Understanding of the design trends in the industry.
  • Choosing the UI style: composition, colors, fonts, module grids.
  • Using the correct marketing tricks.
  • Creating the style guides.
  • Preparing the documentation for the development team.
  1. development

Development is a core process in product creation. During the development process, tech leads start organizing the code styles and code reports. Project managers prepare the two-week sprints and arrange grooming and daily meetings. Developers start creating the code base, and QA specialists begin to test the system.

Grooming
  • analyze technical requirements
  • features estimation
  • design system architecture
  • establish priorities
  • create technical documentation
  • start two-week sprint
  • preparing the backlog
  • create requirements for the delivery process
coding
  • programming
  • debug
  • mentoring
  • code review
  • unit testing
Init Kubernetes
  • cluster on AWS or any other VPS provide
  • create configuration yaml file for each service in a project
  • setup DNS records on domain name provider
  • configure load balancing between available resources(services)
  • configure log stash, configure metrics for the cluster
  • configure metrics for the cluster
  • install kubernetes dashboard and grant restricted access level for the developers
  • configure CI steps to update Kubernetes deployments when new docker image is arrived
  • configure docker image registry, add support of semver (https://semver.org/)
Delivery to the dev environment for testing
qa testing
  • smoke testing
  • integration testing
  • regression testing
  • auto testing
  • forming bug reports
  • tests coverage
Delivery to the dev environment for testing
real content
  • adding real data to make sure the QA process covers all possible cases.
delivery to live environment
MAINTENANCE
  • bug fixing
  • support admin members
  • technical users support
Repeat process
  • repeat the process by creating a new sprint until the backlog is empty.
  1. project docs

Useful and beautiful UI one of the most important parts of the product development process. Creating visible UI to end users include:

  • Market research and understanding the best UI practice.

  • Understanding of the design trends in the industry.

  • Choosing the UI style: composition, colors, fonts, module grids.

  • Using the marketing tricks.

  • Creating the style guides.

  • Preparing the documentation for the development team.