Tools
All of our projects are managed using Clarizen - the leading cloud based project management solution. Details about each project and team are managed and maintained in one centralized, online location reflecting the true status and driving progress in real time. Project status and related data are shared securely between the assigned Titanium Fire Project Team and the respective Client.
- All aspects of a project which are historically maintained in separate applications such as budgets, time, resources and issue tracking are all unified into one platform, empowering teams to work smarter and more efficiently.
- Project related correspondence via email is done through Clarizen ensuring that project status, plans, related documents, notes and discussions are always available.
- Collaborative capabilities allow users to provide feedback regarding risk, issues and recommendations ensuring important knowledge and information is shared with the team.
Methodologies
Waterfall and Agile are two different project management methodologies. Both have their advantages, and can be used independently or in combination based on the needs of the project.
The Waterfall model is a sequential process. Completion of one phase leads to another, with each one having clearly defined deliverables. Key characteristics are the division of the project into tight compartments (phases), comprehensive requirements gathering at the early stages, and robust documentation allowing the movement of individuals on and off the project as required.
Our life cycle template is incorporated into our Hammerhead methodology and supports this approach using the key phases depicted in the diagram below.
This method ensures predictability through greater project and deadline control and is best used:
- In global/multi-site roll-outs with multiple workstreams.
- When priorities and dependencies are rigid.
- Where there are heavy resource constraints.
Agile methodology bases itself on an iterative and incremental approach. Technical teams work on small modules, and respond to users' changing requirements rather than follow a specific or predetermined plan of action. The basic design is simple, and changes are made as work progresses.
This method encapsulates adaptability giving priority to collaboration over design and is best used when:
- Heavy SFDC customisation requirements are identified.
- Force.com application development is needed.
- Clients are able to allocate resources on a full-time basis.
