## 2 Current Market Approach
### Agile Development  
Agile development roots can be traced back to the development of methods like Scrum, Kanban, FDD (feature-driven development) and other iterative solutions for software design and fast delivery like Extreme Programming (XP) or Crystal. These methods comprise various practices, which have their benefits and can be combined. All are based on the Agile Manifesto and included in the so-called \"agile methods\" to share fundamental commonalities.  
The methods are incrementally helping the product development in short iterations, delivering regular product releases to their stakeholders or the end customer, with emphasis on small teams [3; 4; 13]. The scrum process is portrayed in Figure 2, which shows the iterative character with the circles. The big loop or sprint reflects the short periods in which the product is developed incrementally in small parts and after passing through a reviewed process to check the ready status to be released to the customer or user. The daily meetings, small loop, are kept ensuring the information flow within the team, to update them, and discuss the project progress or current issues [23].  
The agile development adds in the circle of iterations the customer with regular cadence and is proactive in the process to ask the return that is considered during devel  
Figure 1: Lean Manufacturing principles.  
Figure 2: Scrum development cycle—part of Agile methodologies.  
-opment steps. Iteration based development and the acceptance of a lot of changes are considered highly reactive and the perfect match for the product prone to frequent changes. The waterfall model is usually inflexible due to the high level of details in the planning phase; it requires much effort and time to react to any required changes. The standard development process is not involving the customer being inside the circle of the decision nor when the requirements are created for the desired product [24].  
Within Agile the Feature Driven Development is a highly adaptive model that is focusing on quality during all development life-cycle and project phases. A feature is a valued function that the end-user wants in the software [25; 26], usually can be extended toward system goal as a value delivered, focused mainly on design and delivery phases. Frequent outputs are the expected and testable results that provide progress and status information for the project; the process is shown in Figure 3.  
The main targets of FDD for value-added development are its high adaptive development model that is focused on designing and modelling aspects during the early phases of the project for each planned release. Focus on quality is emphasized by the team throughout the development phases [25], feedback can be expected within four weeks by full iteration, which is helping to get fast feedback about the developed product from the customer or end-user.  
Integration, software, and feature deliveries are the most important activities that validate the expected results; high flexibility is the key for headlights development and the agile methods are providing the corresponding methodology. Lean and Agile are linked with each other like a balance: on one hand, agile is focused on value-added deliveries, and, on the other hand, lean is focused on waiting until the last critical moment for a decision.