Finding a good domain name for a startup or new product can be a huge pain. Every good .com that you can think of is already taken -oftentimes by opportunistic squatters looking to make a quick thousand bucks; all of the keywords and combinations/permutations of them that aptly describe

When should you use Scrum and when should you use Kanban? There’s no answer that’s right 100% of the time for this question but there are some general rules of thumb that you can use to decide between Scrum and Kanban. The main factors to consider are: * Is

Some patterns pop up again and again. On many, actually most, of the products that I’ve managed, I’ve had to spend huge amounts of time doing manual testing, finding what’s broken, filing issues, tracking issues, chasing down engineers, apologizing to stakeholders and clients, and then following-up and

Given how sophisticated and configurable JIRA is, you’d think that handling dependent design and development tasks would be a piece of cake. It’s not. Usually, the Product -> Design -> Frontend Dev work that goes into creating a new feature/functionality has to happen in order;