"We are an award-winning product design and development firm called CodeJunkie. We partner with startups and enterprises to help them build scalable digital products faster and cheaper. Our team members have the exposure of working with Fortune 500 companies and startups valued at above $100M. We are a solution-oriented team expert in modern tools and technologies but agnostic in our approach to using them for different project requirements. Let's grab a coffee together to discuss how we can help you.
"

"WORK ORGANIZATION

Work organization within the project is based on Scrum. Scrum is a framework that consists of iterative and incremental attitudes towards troubleshooting complex issues. It allows delivering a product of the highest possible value in a productive and creative way.
Within this framework, the process of delivering a product is separated into smaller iterations called sprints, which facilitate rapid and suitable reactions to the changes that accompany the development of the product.
Such a solution helps to build a highly-developed model of information transfer that includes solid control of the whole process upheld by three pillars: transparency, inspection, and adaptation.
We created a backlog of the Product, which has a sequence number, and assign subtasks if needed. It facilitates and simplifies tasks identification.

KICK-OFF

The kick-off meeting is a meeting consisting of two parts
1) Introduction of the team and presentation of the cooperation manual, tools, and reporting practices.
a) Identification of the communication channels we'll use.
b) Clarification of each team member's roles and responsibilities
c) Meetings scheduling (demo/retrospective/planning session)
2) Completing the Backlog along with general acceptance criteria and estimation of the backlog with initial assumptions of velocity.
a) Aligning the team on milestones, scope, and purpose
b) Writing down all the tasks/epics we need to complete in order to deliver on our project's goals
c) Prioritization of work D. It’s also time for technical questions and discussions

REGULAR MEETING

The heart of the Scrum framework is a Sprint, which consists of all the other Events. There are three statute meetings where the presence of the Client (for sure the presence of a person who takes responsibility for the Product Owner role) is required:

Sprint Planning
This meeting is about planning the work amount for the next Sprint. It’s based on Product Backlog, which includes a list of items that completed will make a Sprint Goal.

Sprint Review (Demo)
That's the key to a project’s success. The opportunity to inspect the Increment at the end of the Sprint and adapt the Product Backlog (if needed) can solve or even prevent potential misunderstandings.

Sprint Retrospective
It is an opportunity for the Scrum Team to inspect their workflow. It’s meant to increase team productivity and focus on how efficiently they work. It’s a great time to share new communication ideas, work improvements, or even fears of potential blockers in the future.

EVERY DAY COMMUNICATION

Daily Scrum
The whole Development Team takes part in a Daily Scrum, where the presence of the Client is not required. It is every day, 15-minute time-boxed meeting which serves planning the work for the next 24 hours.

Channels
For everyday communication, we use the following: -
Email - for sharing important information and agreements,
Slack - for discussing current issues and problems.

QUALITY ASSURANCE

Quality Assurance is a systematic process of determining whether a product or service meets specified requirements. Developers work according to Agile methodology, constantly improving the quality of their services sprint by sprint, aiming to achieve full client satisfaction.
"

Agile Software Development, Crystal Methods, Dynamic Systems Development Model (DSDM) , Feature Driven Development (FDD), Lean Development (LD), Rapid Application Development (RAD), Scrum