This step is key. Here you should do everything you can to help make the decision.
Our process of developing digital products
Our goal is to leverage collective knowledge and skills and foster a healthy democratic system with independent associates, working in a network of other small companies, to engage in larger client projects.
We create an umbrella cooperative for local small digital service providers to join forces in order to achieve larger goals and work in cooperation for client projects.
1. Analysis, Research & Preparation
2. Sketching & Wireframing
Now that you know where you’re going, it’s time to think about how this digital product should look. If you’re working with an agency, they can bring in experts to develop this for you.
3. Design
How should this product look and feel? If it’s an app, how will the screens look on an old Android tablet or brand new iPhone X?
4. Prototyping
Before actually starting development on the first version of your product, you can ask to have a scaled down version or “prototype” developed.
5. Agile Implementation
Using an Agile project management methodology significantly increases development productivity, gives you more control and results in an end product that provides real value to your users.
6. Launch
It’s time to roll out your marketing and communication plan, which you should have already started planning in the preparation phase.
7. Maintenance & Support
Often overlooked, the maintenance and support are not the most exciting part of digital product development. But if your product is successful, this will be the longest stage.
Our approaches
Design Thinking
Design thinking is the set of cognitive, strategic and practical processes by which design concepts (proposals for products, buildings, machines, communications, etc.) are developed. Many of the key concepts and aspects of design thinking have been identified through studies, across different design domains, of design cognition and design activity in both laboratory and natural contexts.
Our approaches
Lean
Lean startup is a methodology for developing businesses and products that aims to shorten product development cycles and rapidly discover if a proposed business model is viable; this is achieved by adopting a combination of business-hypothesis-driven experimentation, iterative product releases, and validated learning. Lean startup emphasizes customer feedback over intuition and flexibility over planning. This methodology enables recovery from failures more often than traditional ways of product development.
Central to the lean startup methodology is the assumption that when startup companies invest their time into iteratively building products or services to meet the needs of early customers, the company can reduce market risks and sidestep the need for large amounts of initial project funding and expensive product launches and financial failures.
Our approaches
Scrum
Scrum is a framework utilizing an agile mindset for developing, delivering, and sustaining complex products, with an initial emphasis on software development, although it has been used in other fields including research, sales, marketing and advanced technologies. It is designed for teams of ten or fewer members, who break their work into goals that can be completed within time-boxed iterations, called sprints, no longer than one month and most commonly two weeks. The Scrum Team assess progress in time-boxed daily meetings of 15 minutes or less, called daily scrums. At the end of the sprint, the team holds two further meetings: the sprint review which demonstrates the work done to stakeholders to elicit feedback, and sprint retrospective which enables the team to reflect and improve.
Our approaches
Behaviour Driven Development
In software engineering, behavior-driven development (BDD) is an Agile software development process that encourages collaboration among developers, QA and non-technical or business participants in a software project. It encourages teams to use conversation and concrete examples to formalize a shared understanding of how the application should behave. It emerged from test-driven development (TDD). Behavior-driven development combines the general techniques and principles of TDD with ideas from domain-driven design and object-oriented analysis and design to provide software development and management teams with shared tools and a shared process to collaborate on software development.
Our approaches
Domain Driven Development
Domain-driven design (DDD) is the concept that the structure and language of software code (class names, class methods, class variables) should match the business domain. DDD connects the implementation to an evolving model.
Domain-driven design is predicated on the following goals:
- placing the project’s primary focus on the core domain and domain logic;
- basing complex designs on a model of the domain;
- initiating a creative collaboration between technical and domain experts to iteratively refine a conceptual model that addresses particular domain problems.
The term was coined by Eric Evans in his book of the same title.
Still have questions?
Contact Us
If you’d like to get contact with our team, please complete the contact form.
Partners
