Business Analysis is a profession of its own:
Clear, concise, unambiguous and understandable deliverables consistent with user needs cannot be improvised. Whether with requirements or backlog items, true business analysis expertise is essential.
Technical and functional knowledge about information systems alone is not enough to reliably manage projects.
Well-rounded expertise is necessary as it allows for:
- Industrialization of design phases
- Project scoping up until completion
- Adaptability of our Scrum Master and Product Owner consultants to any project environment, whether V-model or Agile
- Compliance with CMMi best practices
→ 80% of project success depends on the analysis and design phases.
According to the Standish Group’s « CHAOS » report (2015):
- 19 % of IT Projects are dropped ;
- 52 % of IT Projects drift away from their objectives.
Concerning the source of errors :
- 56 % occur as soon as needs are expressed ;
- 27 % occur in design.
Furthermore, 82% of a project’s extra cost comes from errors in deliverables defining requirements.
We systematically establish metrics to quantifiably steer all project phases. This helps ease project scoping, meet deadlines and provide objective performance indicators for measuring progress and self-improvement. We apply our expertise to the following services:
- Opportunity studies, functional requirement specifications, general and detailed functional specifications, software packages, acceptance tests
- Project managers, project directors, PMOs at every phase of the project life cycle
- Methodology, urbanism, business processes, masterplans
- V-model or Agile projects
Because upstream phases contribute to more than 80% of a project’s success, we significantly strengthen them by producing high quality deliverables through an industrial approach to requirement engineering. As such, we contribute to securing key processes: development, test, steering, etc.
The effort ROI arising from problem resolution is higher in upstream phases (needs study, requirement specification, detailed functional specifications) than in downstream phases (testing, user testing and maintenance). However, the latter of these is the most industrialized, whereas the qualitative effort made during upstream phases is somewhat insignificant. That said, the later a mistake is detected, the costlier the correction.
Therefore, provided applications only respond to user needs after lengthy revision phases, and only give partial satisfaction to users and project sponsors (O1 DSI and Standish Group):
- 70% of projects are significantly delayed
- One of every two projects overrun their budget by more than 50%
- Only 16% of projects end in success
Since its creation, Telys continually works towards improvement. That’s why we use our consultants’ knowledges and skills, as IT developers, computational linguistics or modern literature PhD’s to manage R&D (Research and Development) activities on lines such as readability, documents consistency and semantics.
More than half of our consultants work in an Agile environment (Scrum, XP, Kanban, etc.). This experience is the reason we are regularly consulted to optimize Agile practices and avoid the recurring pitfalls of implementation:
- High rework rate: Many Agile projects face high rework rates. This is because a significant part of the work achieved during a Sprint is undone or considerably modified during the next iteration, unlike with a classic V–cycle project. Needless to say, the delay is not highly damaging but persists, resulting in extra system costs and missed deadlines.
- A gradual drop in performance over time: Another common problem is reduced team performance over time. First, velocity declines and fewer complexity points or story points are achieved. When this occurs, the analysis effort required must increase to reach the end of the sprint. This is because there is no consolidated documentation on the system in its current state (user stories and the backlog only mention differences or increments between each iteration; the effects of new versions are more loosely controlled).
- Poor visibility: We also observed several Agile projects without any visibility of the final target, both in terms of delay and cost. For example, in the case of an agile project managed over a year and a half–long period, the chief executive had no visibility whatsoever and requested an audit. The inspection showed that only 10% of the final system had been built after nearly 5,000 man-days.
For each of these major issues, we have identified causes, namely counter-productive practices in the Agile environment. This allows us to offer significant value by securing project futures.