Project initiation

// setting the project goals and understanding its core idea
1

Interview

Step one is arranging an interview call. This is when we discuss things like project goals, scope, target audience, monetization, key dates, and deadlines. At this stage, we're focused on establishing an understanding of the client's needs and expectations.
Step one is arranging an interview call. 
                    This is when we discuss things like project goals, scope, target audience, monetization, key dates, and deadlines. 
                    At this stage, we're focused on establishing an understanding of the client's needs and expectations.
2

Use cases

We draft a list of use cases based on our interview notes and get confirmation from the client. This isn't the final version of the list, but it's a starting point.
We draft a list of use cases based on our interview notes and get confirmation from the client. 
                    This isn't the final version of the list, but it's a starting point.
3

MVP scoping

In order to define the correct release scope and dates, we have a discussion with the client about the MVP in terms of use cases, strategy, and technical approaches. The MVP doesn't necessarily need to be the first public release version, but it may serve as a foundation for future development.
In order to define the correct release scope and dates, we have a discussion with the client about the MVP in terms of use cases, strategy, and technical approaches. 
                    The MVP doesn't necessarily need to be the first public release version, but it may serve as a foundation for future development.
4

Estimation

We work on a T&M (Time and Material) basis. We only estimate approximate development costs so that we can get an idea of the cost of the final product.
We work on a T&M (Time and Material) basis. 
                    We only estimate approximate development costs so that we can get an idea of the cost of the final product.
5

Milestones

It's also important to pay attention to project dates. With that in mind, we set several milestones with dates and deliverables, while scope can be more flexible if needed.
It's also important to pay attention to project dates. 
                    With that in mind, we set several milestones with dates and deliverables, while scope can be more flexible if needed.

Project in progress

// we deliver working and valuable software at each iteration

Workflow

Design sprints
  • Plan
  • Sketching
  • Approval
  • Design
  • Approval
  • Plan
  • Sketching
  • Approval
  • Design
  • Approval
  • Plan
  • Sketching
  • Approval
  • Design
  • Approval
  • Plan
  • Sketching
  • Approval
  • Design
  • Approval
  • Plan
  • Sketching
  • Approval
  • Design
  • Approval
  • Plan
  • Sketching
  • Approval
  • Design
  • Approval
Development sprints
  • Plan
  • Development
  • Testing
  • Demo
  • Plan
  • Development
  • Testing
  • Demo
  • Plan
  • Development
  • Testing
  • Demo
  • Plan
  • Development
  • Testing
  • Demo
  • Plan
  • Development
  • Testing
  • Demo
Product analysis sprints
  • Hypothesis
  • Analysis
  • Insight
  • Hypothesis
  • Analysis
  • Insight
  • Hypothesis
  • Analysis
  • Insight

Project management

We believe in lean processes and agile software development. OOur process is completely transparent to clients. In order to guarantee this transparency, we provide clients with full access to our management software.
For each iteration, we provide a sprint plan (example) before we start and a sprint report (example) at the end. We prefer fixed release dates, but the scope can be flexible if needed.
Targetprocess logo
TargetProcess sprint view screenshot
Screenshot from the project management software

UX/UI design

We always make sure that we're asking the right questions before getting started. Our first goal should be to gain a deep understanding of the problem we're trying to solve.
Only after we have achieved this do we proceed with the design stages, from user stories to user journeys, sketches, screen maps, and prototypes.
Sketch
Sketch example
UX
UX example
UI
UI example
UI
UI example

Development and quality assurance

We truly dislike bad coding and poorly designed architecture. We use unit and integration tests to automatically double-check our code and release it quickly.
Our manual testing is documented and well-organized. We use test cases and test plans, and we also record test runs.
Test run example screenshot
An example of a typical test run