In web and software development we all know what it’s like to finish a project and have it leave a bad taste with either your team or your stakeholders. Often left with thoughts of “if we’d just had time to slip that last feature in”, “I wish we’d understood that requirement earlier. or even worse “I wish we’d given that more testing time”. The problem is that as humans we’re incredibly good at this kind of thinking, but by using Agile processes to change this thinking both your development team and stakeholders alike will be a much happier bunch.

You’re close to shipping and you receive a shopping list of bugs and changes. Some are tiny and un-eventful, some are show stoppers, some let the bad guys in, and some are simply scope creep trying to sneak through the door. It’s hard to know where to start without reclassifying them because the majority of them are all labelled Critical. It’s time to sit down with whoever documented your bugs and do some talking…

Writing quality software for clients is difficult at the best of times. Planning a timeline, planning resources and making sure you have the skills to complete the job, along with a myriad of other things to worry about – If your company is a solution provider, not an integrator (a digital agency) you also have to factor in the end result, and expected return that the client will even get out of the project (the end game) before you even start. So the question is, with so many things that require careful planning, why do software development timelines always appear to carry less weight with management than projects in other mediums?