Deciding between time and materials vs fixed price contract can be tricky. So here’s a complete guide with pros and cons to help you choose the best for you
Product Development
Should you go for cheap, fast or good when developing products?
Is it possible to develop a good product cheap and fast? In short: no. But some sacrifices are bigger than others.
How we prioritize features: Taming the feature creep
When building a product, it’s easy to get carried away adding feature upon feature. So how to tame the feature creep and prioritize functionalities?
Minimum viable product, maximum benefits: How we’re building LiveRobe’s sustainable fashion app
Style doesn’t have to cost the earth. Find out how we built LiveRobe’s minimum viable product to validate the sustainable startup idea and what should come next.
Fair p(l)ay: Time and material pricing in software development
How and how much to charge when selling your expertise? At Digital Natives, we swear by time and material-based pricing. Here’s why.
The next big thing or the next big flop? How (not) to create products
Developing a viable product is not an easy ride, and we learned that the hard way in the past. See our blog post on the products we failed to bring to success and the lessons we learned from that.
A bugging question: who should pay for bug fixing?
In our last post we said that there is no such thing as “bugless” software. But in this case another question pops up: who to blame – and who to charge – when a software needs fixing?
Are all bugs equally important in a product?
Let’s face it: when you’re in the business of delivering digital solutions, bugs are all part of the process. They’re inevitable. But are all bugs created equally important?
Here’s why every agile project needs a Product Owner
Find out why every development project needs a client-side product owner – and what to do if there isn’t one.
