Apollo's Pad Community Site

Agile Project Management

Strong project management is key to the success of Heavenly Media. We recognise that at the start of a Ruby on Rails project, your requirements are not necessary 'baked' and can be subject to change, depending on your changing business needs or the needs of your client. We also recognise that you want the status and progress of your project to be visible at all times.

To accommodate these needs, our project management tools are designed to provide a high degree of visibility and flexibility.

We work incrementally and deliver fully working and tested software every 15 working days, a process known as timeboxing. This gives you the opportunity to go live early if you choose, and gives you direct feedback about the status of your project.

At the start of each iteration we agree with you which features should be present in that increment. You can prioritise features, meaning that you get the most valuable features first.

At the end of each increment, every 15 working days, we will deliver feature complete, tested, bugfixed and fully working software.

From here you have several options. You can choose to perform another iteration, adding more functionality. You can go live early with the features that you have, or you can decide that you already have enough functionality and end the project early, saving you money and increasing your ROI. At every stage you have the choice and you are never locked in.

Frequent, Effective and Honest Reporting

As features are completed, we mark them off. Each feature has a time estimate and we subtract this from the total, showing us how much work is being accomplished each day and if the project is on schedule. We graph this information into a 'burndown chart'. The speed at which the line moves towards 'zero hours remaining' lets us gauge the velocity of the project. If we can see that we're on target to finish early we can add more features to the iteration at no extra cost.

At Heavenly we work to the maxim 'done is done'. This means that a feature is not marked as complete until it is fully built, tested and running on the server. We call this 'pessimistic reporting'. This keeps us honest and allows you to have full confidence in our status reports.