Agile Requirements Engineering
“As agile team, I want the team to have enough expertise about requirements engineering, so that requirements are given the attention they deserve.” Through its holistic approach, Texelia takes care of requirements quality.
Traditional or agile approach ?
In traditional approaches of Project Management, requirements engineering – collect, understand and manage requirements – is presented as a first phase, before proper development. In more recent methods of software development, it is assumed that requirements engineering will be applied throughout the lifecycle of a system.
The typology of a specific system under development must guide which specific method is to be used. An automatic flight control system will probably not be developed with an Agile approach as opposed to a dynamic website. For the website, we still are not aware of all public targets needs and some operational or functional increments should be reformulated throughout the project life cycle to regularly get customer’s feedback.
Graphic inspired by Gartner (April 2015)
Whatever the development method adopted, it is generally observed that a lot of projects do not achieve their objectives, mainly because of poorly defined business requirements. Whether the approach is Waterfall, V or Agile, defining quality business requirements and managing them is a key factor of success of any project or initiative.
Within the framework of the triple helix method that our experts use, Texelia offers a global approach of requirements analysis based on Accuracy, Relevance and Agility.
- Processes: during each iteration, our business analysts will ensure that a specific set of activities, techniques and tools are implemented to discover, define and manage requirements. We describe business processes “As is” (workflow, business rules, etc.), then we model them “To be” under the perspective of the expected technological or functional change.
- Data: during each iteration, we act as client proxy to ensure the quality of those data that are in input and output of processes impacted by the solution or service. Quality is guaranteed by effective testing that use relevant datasets. As business analysts totally integrated in the project team, we highlight the relevance of the company’s Master Data to assist in the prioritization of requirements’ repository (backlog).
- Tempo: we make sure to provide and communicate just in time, in the appropriate iterations, those requirements and functional specifications (Roles, Authentication, Logic, Business rules, External interfaces, Legal Compliance, etc.) as well as operational specifications (Performance, Availability, Usability, Security), adapted to customer and company needs. At the end of the project life cycle, we also take care to provide the necessary stable and complete documentation.
Meeting business needs through good Requirements management practices is an essential component of the success of a project, regardless of the approach used. A requirement makes sense only if it meets a need, explicit or implicit:
Comparing development models