We plan and execute our projects based on outcomes, not tasks, so that your project starts delivering early in the process. We use both Agile (Scrum) and Waterfall (Prince2) methodologies as appropriate for the type of project. Agile works well for a new system used by end customers, Waterfall is often best for bigger projects where the project delivers a step change.
We like to be hands on throughout the project lifecycle and often directly carry out requirements capture and test management as well as taking responsibility for the day to day running of the project.
For most of our projects, we manage the clients staff and suppliers as project resource. In some cases we can also provide subcontracted staff to cover any gaps in skills.
We use a number of tried and tested project management tools/techniques to give your project the best shot at success.
- Product based planning – we reckon we can plan any activity using this technique.
- Requirements catalogues – without requirements defined and agreed things will get out of hand. We prefer defining these as user stories.
- Process flows – If you are changing the way you work or do business, these are invaluable to ensure the “to be” does not miss out something critical from the “as is”.
- Sprints & Scrum boards – we used to like Gant charts (some of us still do) but these are clearer and better for team working.
- Test management systems – is it wrong to love a test management system? We have had a long term relationship with TestLink.
- Effort based planning – we use Microsoft Project to build plans that provide the three key ingredients of any project plan Time, Cost and Effort.
- RAID logs – We keep logs of risks, action, issues and decisions but we like to get the closed down as soon as possible.
- JIRA – we spend more than the recommended number of hours per day on this issue tracking system. We like it so much we even bought our own copy!