Google Analytics

HOW WE WORK

In the beginning we would like to get to know you and your idea. We’ll arrange a call or meeting in person if possible so we can meet face-to-face and get more details. Ask us as many questions as you like – we’ll answer them all.

If you decide to work with us we’ll put together the best team of our people chosen specifically to suit your needs. You’ll also get the best tools and technologies for your product.

Next step is to set the right plan of action. Together we’ll prepare appropriate steps so the whole process of creating product runs smoothly. Once we have the right plan of action the time has come to implement it. We’re Agile supporters and we usually work in two-week sprints. Here’s how it looks:

Information Icon

Product backlog

It is a list of all things that need to be done within the project. The owner of the Product Backlog is the Product Owner. Product backlog is never complete – it evolves with the product itself and can be changed freely anytime during the development process when time & materials approach is taken.
Information Icon

Sprint Planning

Next features that need to be done are selected by you. Then, in the meeting, team has to answer the following question: “What can be delivered in the upcoming sprint?” and move predicted task into the Sprint Backlog.
Information Icon

Sprint Backlog

The Sprint Backlog is a list of Product Backlog tasks identified by the team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects number of product backlog items and identifies the tasks necessary to meet the Sprint Goal.
Information Icon

Sprint Retrospective

In the Sprint Retrospective meeting the team focuses not on the software, but on improving the development process itself. This way it is always in line with changing conditions and different stages of a software life cycle.
Information Icon

Scrum Team

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. It’s self-organized in its own way to succesfully accomplish work instead of being directed from the outside. Scrum Team has all competencies needed to accomplish the work without depending on external resources. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
Information Icon

Daily Scrum

Short 15-minutes team meeting to synchronize activities and create a plan for the next 24 hours. Each team member answers the following three questions: What did you do yesterday? What will you do today? Are there any impediments in your way?
Information Icon

Sprint Review / Demo

Sprint Review is held at the end of each sprint. During this meeting, team shows an actual increment developed during the sprint. Typically this takes the form of a demonstration of the new features implemented.
Information Icon

Increment

The Increment is the sum of all the items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be in useable condition and be potentially releasable. The increment is a step toward a vision or goal.
Agile workflow
Information Icon

Product backlog

It is a list of all things that need to be done within the project. The owner of the Product Backlog is the Product Owner. Product backlog is never complete – it evolves with the product itself and can be changed freely anytime during the development process when time & materials approach is taken.
Information Icon

Sprint Planning

Next features that need to be done are selected by you. Then, in the meeting, team has to answer the following question: “What can be delivered in the upcoming sprint?” and move predicted task into the Sprint Backlog.
Information Icon

Sprint Backlog

The Sprint Backlog is a list of Product Backlog tasks identified by the team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects number of product backlog items and identifies the tasks necessary to meet the Sprint Goal.
Information Icon

Sprint Retrospective

In the Sprint Retrospective meeting the team focuses not on the software, but on improving the development process itself. This way it is always in line with changing conditions and different stages of a software life cycle.
Information Icon

Scrum Team

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. It’s self-organized in its own way to succesfully accomplish work instead of being directed from the outside. Scrum Team has all competencies needed to accomplish the work without depending on external resources. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
Information Icon

Daily Scrum

Short 15-minutes team meeting to synchronize activities and create a plan for the next 24 hours. Each team member answers the following three questions: What did you do yesterday? What will you do today? Are there any impediments in your way?
Information Icon

Sprint Review / Demo

Sprint Review is held at the end of each sprint. During this meeting, team shows an actual increment developed during the sprint. Typically this takes the form of a demonstration of the new features implemented.
Information Icon

Increment

The Increment is the sum of all the items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be in useable condition and be potentially releasable. The increment is a step toward a vision or goal.

For project management we use Atlassian JIRA to which you’ll receive access and be able to observe work in progress 24/7. You can communicate directly with the team as often as you wish – they’ll respond as soon as possible.

Project board Jira 1
Project board Jira 2

What else you should know?

  • We can take over projects started by other companies
  • We also work with undocumented and low quality legacy code – we can understand, document, refactor and update it to the current industry standards
  • We work with NDA – we always keep our cooperation confidential

PRICING CONTRACT

“If you think good design is expensive, you should look at the cost of bad design.” Ralf Speth

Selecting the right pricing contract is a vital step when outsourcing software development. In Code Poets we offer you a choice – you can choose between time & materials and fixed price. Let’s have a look at the advantages and disadvantages of each model.

TIME & MATERIALS

You will be charged for the number of hours spent on a specific project, plus costs of materials. Total cost of a project depends on the actual effort made towards the development. Main advantage is flexibility and opportunity to adjust requirements, shift directions and replace features. You will be given full transparency of work done in a sprint via reviews, sprint boards and regular releases.

  • Long-term projects
  • Developing a startup
  • Projects that require flexibility and have unclear scope
  • Projects in which you’re not sure about final functionalities
  • Working with legacy code
FIXED-PRICE

A fixed-price contract is based on an estimate of the amount of work that needs to be done. This model ensures that the project will be delivered within a specific timeframe and budget. It can be a good choice in cases when you know exactly what you want to create and know all the requirements and specifications. You have to be able to share your clear vision of the product.

  • Projects with very clear requirements
  • Small projects with limited functionality
  • MVP developing
  • Projects with strictly determined deadlines and budget
TIME AND MATERIAL
FIXED PRICE
+
You're able to adjust the project's requirements to constantly changing business circumstances. Do you need some new functionalities or remove an existing one? No problem, let's do it!
High flexibility
Predictability
With clear requirements and set deadlines, there are almost no suprises. It's easy to predict if the work will be completed on time.
+
+
In most cases it is better to make decisions in the process, evolving a strategy and building custom software simultaneously.
Dynamic work scope
Precise final cost
You will know exactly how much time and money the project development requires before the works starts.
+
+
We don't need a highly detailed project description. All we need to know at the beginning is only some basic features. New features will be added during the next sprints.
Instant start
Precise final cost
You will know exactly how much time and money the project development requires before the works starts.
+
+
You pay for the number of hours actually work on, based on their hourly rate. This model allows you to monitor progress and know exactly where the team is at any point.
Cost transparency
Little client involvement
You will know exactly how much time and money the project development requires before the works starts.
+
+
Product is well-tested and brought to its best thanks to multiple iterations which result in a highly-quality product.
High product quality
Less control
You won't be able to control the development process and easily follow the progress made in your project.
Minus icon
Minus icon
The overall cost can go far beyond the expected budget.
Low budget control
Less flexibility
Any change during the development requires additional planning and renegotiation. In consequence, it will take more time and increase the overall cost.
Minus icon
Minus icon
This contract type requires a great deal of your attention.
Low budget control
Long and meticulous planning
Product is well-tested and brought to its best thanks to multiple iterations which result in a high-quality product.
Minus icon