Absolute estimating of programming tasks proves to be challenging in (too) many cases. When development takes longer than foreseen, any or several of the following areas are impacted: quality, finances, resource planning and client satisfaction. Studies reveal that 2 out of 3 software development projects are unsuccessful because they are over budget, late, missing function or a combination – in short: estimating fails frequently enough.
Agile Estimating is a methodology for project managers to better plan their projects in advance and to keep their planning up-to-date and accurate throughout the development process. Estimates of tasks are done on a relative basis using an independent unit instead of hours or days. As the team progresses on its tasks, indicators such as the actual business situation, the constitution of the team, the learning progress of the team members and the feedback of the client are tracked. These indicators are fed back into an updated planning allowing for more accurate forecasts and giving a better basis for decision making.
As the TYPO3 community is transitioning into greater possibilities and chances to establish itself increasingly in the enterprise CMS sector (keyword: TYPO3 Phoenix), new technical complexities will have to be faced and overcome. New business requirements and better interoperability with other systems is going to put high demands on project teams. Strong project management capabilities need to be acquired alongside the technological advancements within the community and with the different services providers to sustain the reputation of TYPO3 services as enterprise solutions.