Delivering working features based on vague project specifications can be fraught with pitfalls. How do you ensure a shared understanding between stakeholders of wildly varying subject-matter expertise and technical skills? How do you stay on the critical path, delivering incremental value and properly prioritizing when faced with conflicting mandates? How do you demonstrate that you've satisfied the original requirements after all that?
We'll cover how to set up a project for success with:
Behaviour-Driven Development using Behat
Agile project management on GitLab
Project documentation in Hugo
I have presented at numerous Drupal-related conferences and events, including, Camps, Summits and DrupalCon Europe.