Code & Pepper FAQs

You will stay on the same page with your team thanks to sharing the tasks and their status in a dedicated Jira board. As an option, we can switch to your own progress tracking tool if necessary. You’ll be able to observe how team velocity translates into project progress thanks to constant access to the team timesheet updated on a daily basis. (more)

It’s our priority to build and maintain an orderly, fully legible and reliable code repository you can look into whenever you need. To assure mutual access to the code, we recommend sharing your own (client’s) repository with the project team. In selected cases, we work on Code & Pepper’s repository and grant you full access to it. (more)

The exact approach to requirements management will be settled after the preparation phase. At that point, we analyse how we can optimally share the scope of responsibilities, competences and skills between you and the team at Code & Pepper. (more)

Our software development and communication toolkit include Jira, Confluence, GitHub, GitLab, and Slack. Our designers use Adobe Creative Cloud software, Sketch, Zeplin, and Marvel, among others. We are also open to using other tools of your choice.
(more)

The fundamental element of our approach to product development is to follow the Continuous Delivery practice. It means that the product is built and deployed to a proper environment feature by feature (user story by user story). The developers should deploy new features as often as possible, even several times a day. Building, testing and deployment happens automatically using proper CI/CD tools. Code quality involves several types of automated tests to cover as many product areas as possible.
(more)

Scrum is our go-to methodology for design and development projects as it offers a perfect set of tools to manage projects transparently and effectively. The team will use Scrum’s flagship measurement techniques (i.e. story points and burndown charts per sprint) to determine team velocity and plan reliably. In order to clarify functional and technical requirements in an efficient way, we organise so-called product discovery workshops, which take at least one day at the beginning of cooperation. (more)

Any person on your end can take part in any team meeting, especially the ones within the Scrum flow (daily standup, demo, review, retrospective). Daily real-time messaging takes place on Slack, where everyone can communicate without intermediaries. This way, you and the team can get to know each other better. (more)