Konstantin puts it to you that one of the biggest problems in the software industry manifest from the gaps in shared understanding. This leads businesses to make technological choices with limited knowledge of technology impacts, or worse, technology delivery teams to make business choices without business guidance. Inevitably this leads to products being built badly, or the wrong products being built.
Agile, and BDD in particular, try to solve this problem through steady and deliberate discovery. What if you don't have time to be steady? What if you need to start bridging this gap very quickly with a new customer at the beginning of a new project, almost every week? Enter the project discovery - a way to get on the same page with many businesses in an agency-like environment.
This talk will present a collaborative process built on top of Agile and BDD practices aimed to replace requirements gathering and contract negotiation processes with Agile delivery planning.
Konstantin is an engineer who, through tools and methodologies, got deep into business analysis. He's currently a behaviour driven development (BDD) practice manager at Inviqa Ltd (UK). His job involves bringing agile projects to life through bridging communication gaps between business and delivery teams.
Before Inviqa, he spent almost 2 years in France working as a senior PHP developer in KnpLabs, delivering high-quality startups for clients across the world. During his engineering life, Konstantin created de-facto PHP BDD tools (Behat, PhpSpec2) and contributed to big open source projects like Symfony2, Doctrine2, Composer and others.
To buy tickets to see this fantastic talk, and many others like it head over to our ticket page.
Need help planning which sessions to attend? We've provided a breakdown of our various session types below.
A presentation and discussion of real-life (not theoretical) experiences of the application (or mis-application) of Agile and Lean practices. Case studies and experience reports include some discussion of lessons learned and an indication of how novel the work is.
Participants learn a new approach, tool or technology through using it to solve one or more practical exercises. Any software/hardware requirements are disclosed in the session description.
A session focused around some specific tool, technique or issue. Primarily led by the speaker, tutorials usually include some elements of interactivity or individual / group exercise.
An in-depth working session on a specific topic. May include paper presentations.