In a couple of previous posts, I wrote about preparing specs and mockups for your product (Part I) and hiring designers and developers (Part II). Once you have your product spec, design and team ready you can start the development process. This step is equally complicated as any of the
I read a fantastic book by Vasco Duarte called NoEstimates: How To Measure Project Progress Without Estimating. Estimating time & cost is always one of the main problems in software development, and I’d like to share some ideas I’ve learned from the book. If you like it, I
The only way to create software that has fewer bugs is to cut off the functionality and implement an absolute minimum and then spend an enormous amount of time testing and perfecting it. That’s rarely the case for a project that aims for commercial success. New releases of every
Speed and quality are two conflicting factors of a software development project. The proper development process includes analysis, design, solid implementation and rigorous testing. Because of tight deadlines management is often willing to speed up or skip steps that are deemed less necessary entirely and trade delivering the best overall
One of the toughest subjects for every software project is when it’s going to be finished. With traditional waterfall approach plenty of time is spent on analysis and estimation, and still, most of the projects are not completed by the deadline. Estimations that were too off contribute to this
Agile practices are often thought of as silver bullets for wrong estimates, bugs, tasks overdue, global warming and other kinds of problems in software development. It is often compared to waterfall methodology, which is a more linear approach to developing software. Let’s get into the detail of these concepts