Measuring the success of a development project is tricky. It can be easy to put too much emphasis on arbitrary metrics, but success is largely not defined by metrics. If you take a step back and look at the bigger picture, success is not as clear cut as "a velocity of 10 points per week". Let’s look at the ways we can measure if your software development project is successful.
Attempting to identify the ‘Best Practices of Project Management’ is no small feat. Often, role & responsibilities change from place to place, project to project, and differ people to people. That said, I do have some anecdotal information regarding what I believe to be a better approach to Project Management.
We’ve all heard the horror stories about using outside software development shops. Project overruns, bugs, poor performance and quality, and an impossible to maintain codebase are some of the most common. As with any service, the quality is completely dependent on the individuals providing that service to you. For custom software development, it’s even more challenging, as writing software is both engineering and art, and the best developers harness a bit of both.
You're wasting time on design and you don't even know it yet. Check out how you can speed up your process and unify your team with modular design.
As a consulting company, we review a lot of potential projects. How do we find those that are a good match for our expertise, culture, and that we can successfully sign a contract? The short answer is: it takes a lot of work. One step in the evaluating process is to estimate how much it would cost a potential client for us to build their project, and how long it would take. This post is the final of three that provide an in-depth walkthrough of how this happens at Quick Left!